// MCP SERVER RECORD

Tether Name

Unverified
NPMtether-name-mcp-server
FRisk gradecritical blast radius
Catalogue entry updated 6 days ago
Auth postureNot probedno remote endpoint probed yet
Tools132 Destructive · 3 Execute · 3 Write · 5 Read
Worst categoryDestructivegrade tracks the peak, not the average
Capability mix
Destructive 2Execute 3Write 3Read 5
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 13
delete_agentDestructiveHighrevoke_agent_keyDestructiveHighsign_challengeExecuteMediumsubmit_proofExecuteMediumverify_identityExecuteMedium
View all 13 tools
create_agentWriteHighrotate_agent_keyWriteHighupdate_agent_identityWriteMediumget_agent_infoReadLowlist_agent_keysReadLowlist_agentsReadLowlist_domainsReadLowrequest_challengeReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
delete_agentdeny
sign_challengerequire approval
create_agentrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y tether-name-mcp-server

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.