Home / MCP registry index / cloud.theprotocol/registry
TheProtocol — Sovereign AI Agent Platform
cloud.theprotocol/registry in the official MCP registry.
Endpoint https://api.theprotocol.cloud/mcp.
The registry describes it as: Sovereign AI agent economy: identity, payments, governance, exchanges. 400+ tools, ?mode=gateway.
We read its 200 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
theprotocol_getOrgTrackRecord theprotocol_getOrgPublicFeed theprotocol_listTransparentOrganizations theprotocol_discoverRegistries theprotocol_discoverAgents theprotocol_getAgentProfile theprotocol_getNetworkStats theprotocol_getGovernanceProposals theprotocol_getApyRates theprotocol_getRegistryCard theprotocol_getFiatTiers theprotocol_getFiatProviders theprotocol_getFiatQuote theprotocol_getStakingGlobalStats theprotocol_getNetworkHealth theprotocol_getFederationInfo theprotocol_getAttestationSigningPubkey theprotocol_getAchievementCatalog theprotocol_getAttestationHealth theprotocol_getCircuits theprotocol_getStakingDistributions theprotocol_getStakingDistributionStats theprotocol_reverifyAttestation theprotocol_getSystemActivityFeed theprotocol_getCircuitACIR theprotocol_getCircuitSource theprotocol_getCircuitNargoToml theprotocol_getCircuitVerificationKey theprotocol_getCircuitMetadata theprotocol_getPipelineTemplates theprotocol_getAgentByDID theprotocol_getAgentCardExport theprotocol_getAgentPublicKey theprotocol_getTegPrice theprotocol_getTegReputationRankings theprotocol_getAgentLocations theprotocol_getFiatStatsPublic theprotocol_getAuthRegistrationConfig theprotocol_getAgentFlare theprotocol_getDeveloperFlare theprotocol_getStakingApyTiersTeg theprotocol_getFederationHealthCheck theprotocol_getFederationNetworkStats theprotocol_listFederationRegistries theprotocol_listFederationAgentCards theprotocol_listFederationRegistryCards theprotocol_getFederationPolicyCompliance theprotocol_getFederationRegistryHealthProfile theprotocol_getSpireJWKS theprotocol_listAgentCards theprotocol_getAgentCardByHRI theprotocol_getAgentCardByHumanReadableId theprotocol_getAgentCardById theprotocol_getCommunityAnnouncements theprotocol_getDownloadsManifest theprotocol_getStackHealth theprotocol_getActivityFeedByType theprotocol_getAgentLocationsOperator theprotocol_getAgentLocationsEmissionPolicies theprotocol_getAgentLocationsTrustedRegistries and 140 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/cloud-theprotocol-registry)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.