// MCP SERVER RECORD

TempoGraph

Unverified
NPMtempograph
DRisk gradehigh blast radius
Catalogue entry updated 7 days ago
Auth postureNot probedno remote endpoint probed yet
Tools241 Execute · 2 Write · 21 Read
Worst categoryExecutegrade tracks the peak, not the average
Capability mix
Execute 1Write 2Read 21
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 24
run_kitExecuteHighindex_repoWriteHighunwatch_repoWriteMediumarchitectureReadLowblast_radiusReadLow
View all 24 tools
cochange_contextReadLowdead_codeReadLowdependenciesReadLowdiff_contextReadLowembed_repoReadLowfile_mapReadLowfocusReadLowget_patternsReadLowhotspotsReadLowlearn_recommendationReadLowlookupReadLowoverviewReadLowprepare_contextReadLowreport_feedbackReadLowsearch_semanticReadLowstatsReadLowsuggest_nextReadLowsymbolsReadLowwatch_repoReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
run_kitrequire approval
index_reporate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y tempograph

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.