Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TheProtocol — Sovereign AI Agent Platform

REMOTE · API.THEPROTOCOL.CLOUD · 2 COMPONENTS

Sovereign AI agent economy: identity, payments, governance, exchanges. 400+ tools, ?mode=gateway.

0 this week 91 Trust /100

Last scanned (19 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 26984 tokens (~60/item across 448 items; 443 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management89
  • Stability check failed: schema churn in the 29 days we've observed: 35 tool removals, 1 breaking changes, 0 auth/transport breaks, 34 additions. See how to fix → Fail
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% of tool parameters carry a description.Partial
  • Structured output schemas are declared (2% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 29 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 445 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 0
    • Tool “theprotocol_decideChatApproval” rewrote its description, which is the text the model reads security
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “theprotocol_getChatApprovalStatus” rewrote its description, which is the text the model reads security
    • New tool “theprotocol_getChatAttachment” functional
    • New tool “theprotocol_getChatBoard” functional
    • New tool “theprotocol_getChatCardHistory” functional
    • New tool “theprotocol_getChatUnreadCount” functional
    • New tool “theprotocol_listChatApprovals” functional
    • New tool “theprotocol_listWaitingChatApprovals” functional
    • New tool “theprotocol_markChatRead” functional
    • New tool “theprotocol_postChatProgress” functional
    • New tool “theprotocol_updateChatBoard” functional
    • New tool “theprotocol_updateChatProgress” functional
    • “theprotocol_requestChatApproval” added an optional parameter “options” cosmetic
    • “theprotocol_sendChatMessage” added an optional parameter “reply_to” cosmetic
    • “theprotocol_decideChatApproval” added an optional parameter “option” cosmetic
    • “theprotocol_decideChatApproval” reworded the description of “decision” cosmetic
  • 1 Nov 26 0
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “theprotocol_bridgeTransfer” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “theprotocol_decideChatApproval”, which the server declares destructive security
    • Tool “theprotocol_guildCancelOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_readThread” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_enableMtls” rewrote its description, which is the text the model reads security
    • New tool “theprotocol_syncChat” functional
    • New tool “theprotocol_setMyAgentStatus” functional
    • New tool “theprotocol_requestChatApproval” functional
    • New tool “theprotocol_getOrganizationPresence” functional
    • New tool “theprotocol_getChatApprovalStatus” functional
    • New tool “theprotocol_consumeChatApproval” functional
    • “theprotocol_readThread” added an optional parameter “mentions” cosmetic
    • “theprotocol_guildSubmitWork” added an optional parameter “commits” cosmetic
    • “theprotocol_guildPostOrder” added an optional parameter “intended_worker_did” cosmetic
    • “theprotocol_guildCancelOrder” added an optional parameter “reason” cosmetic
  • 27 Oct 26 −1
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “theprotocol_claimTegRewards” was removed ▼ security
    • Tool “theprotocol_claimStakingRewards” was removed ▼ security
    • Tool “theprotocol_estimateMyStakingRewards” was removed ▼ security
    • Tool “theprotocol_getAgentPendingRewards” was removed ▼ security
    • Tool “theprotocol_getAgentRewardsHistory” was removed ▼ security
    • Tool “theprotocol_getAgentStakingBalance” was removed ▼ security
    • Tool “theprotocol_getAgentStakingHistory” was removed ▼ security
    • Tool “theprotocol_getApyRates” was removed ▼ security
    • Tool “theprotocol_getArenaMatchBets” was removed ▼ security
    • Tool “theprotocol_getAutoCompoundForAgent” was removed ▼ security
    • Tool “theprotocol_getMyA2APaymentTokens” was removed ▼ security
    • Tool “theprotocol_getMyAutoCompound” was removed ▼ security
    • Tool “theprotocol_getMyEarnings” was removed ▼ security
    • Tool “theprotocol_getMyRewardHistory” was removed ▼ security
    • Tool “theprotocol_getMyStakeStats” was removed ▼ security
    • Tool “theprotocol_getMyStakes” was removed ▼ security
    • Tool “theprotocol_getMyStakingHistory” was removed ▼ security
    • Tool “theprotocol_getMyStakingStatus” was removed ▼ security
    • Tool “theprotocol_getStakingApyTiersTeg” was removed ▼ security
    • Tool “theprotocol_getStakingDistributionRecords” was removed ▼ security
    • Tool “theprotocol_getStakingDistributionStats” was removed ▼ security
    • Tool “theprotocol_getStakingDistributions” was removed ▼ security
    • Tool “theprotocol_getStakingGlobalStats” was removed ▼ security
    • Tool “theprotocol_getTokenomicsRewards” was removed ▼ security
    • Tool “theprotocol_getTokenomicsTransactions” was removed ▼ security
    • Tool “theprotocol_getTokenomicsTreasury” was removed ▼ security
    • Tool “theprotocol_stakeTokens” was removed ▼ security
    • Tool “theprotocol_tegReputationSignalToken” was removed ▼ security
    • Tool “theprotocol_tegStakeDirect” was removed ▼ security
    • Tool “theprotocol_tegUnstakeDirect” was removed ▼ security
    • Tool “theprotocol_transferTokens” was removed ▼ security
    • Tool “theprotocol_triggerManualDistribution” was removed ▼ security
    • Tool “theprotocol_unstakeTokens” was removed ▼ security
    • Tool “theprotocol_updateAutoCompound” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “theprotocol_authorizePayment” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_bridgeTransfer” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getDeveloperStats” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyAchievements” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyBalance” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyFlareStatus” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyTegBalance” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyTegTransactions” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getNetworkStats” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildAward” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildBid” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildCancelOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildGetOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildVerify” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_instantiateContractTemplate” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_previewSlashReductionAttestation” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_releasePayment” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_releasePaymentById” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_settlePayment” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_smartSend” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_submitDispute” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_verifyPayment” rewrote its description, which is the text the model reads security
    • Prompt “stake_and_earn” was removed ▼ functional
    • New tool “theprotocol_getAgentLockHistory” functional
    • New tool “theprotocol_getAgentLockedBalance” functional
    • New tool “theprotocol_getLockStats” functional
    • New tool “theprotocol_getMyIncome” functional
    • New tool “theprotocol_getMyLockHistory” functional
    • New tool “theprotocol_getMyLockStats” functional
    • New tool “theprotocol_getMyLockStatus” functional
    • New tool “theprotocol_getMyLocks” functional
    • New tool “theprotocol_getMyPaymentAuthorizations” functional
    • New tool “theprotocol_getRegistryTreasury” functional
    • New tool “theprotocol_getUnitTransactions” functional
    • New tool “theprotocol_tegReputationSignal” functional
    • New tool “theprotocol_tegUnlockDirect” functional
    • New tool “theprotocol_transferUnits” functional
    • New tool “theprotocol_unlockUnits” functional
    • “theprotocol_smartSend” added an optional parameter “idempotency_key” cosmetic
    • “theprotocol_authorizePayment” reworded the description of “ttl_seconds” cosmetic
    • “theprotocol_createWebhook” reworded the description of “events” cosmetic
    • “theprotocol_releasePayment” reworded the description of “token” cosmetic
    • “theprotocol_settlePayment” reworded the description of “token” cosmetic
    • “theprotocol_verifyPayment” reworded the description of “token” cosmetic
  • 18 Oct 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Tool “theprotocol_getTegReputationRankings” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getTrustScore” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getWellKnownRegistryCard” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildCancelOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildCrossRegistryBid” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildGetOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildListOrders” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_guildPostOrder” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_listFederationRegistryCards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_listMyAttestations” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_previewSlashReductionAttestation” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_releasePayment” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_agentRevokeAttestation” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_applyReputationSignal” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_authRecoverAccount” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_authRegister” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyVotingPower” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getNetworkStats” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getNotificationCatalog” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getPipelineTemplates” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getRegistryCard” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getRegistryFederationProposals” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getStakingApyTiersTeg” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getStakingDistributionStats” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getStakingDistributions” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getStakingGlobalStats” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getSupportReviewState” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getSystemActivityFeed” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getTegPrice” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getTokenomicsRewards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_bridgeTransfer” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_claimPendingAchievements” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_claimStakingRewards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_claimTegRewards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_createAgent” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_createApiKey” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_createArenaMatch” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_createAttestationSchedule” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_createProposal” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_depositReputationBond” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_disable2FASelf” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_enableMtls” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_enableToolset” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_engageAgent” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_estimateMyStakingRewards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAchievementCatalog” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentByDID” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentCardExport” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentLocations” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentLocationsEmissionPolicies” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentLocationsTrustedRegistries” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentPendingRewards” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentPublicKey” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentRewardsHistory” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentStakingBalance” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentStakingHistory” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAgentTransactionHistory” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getApyRates” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAttestationHealth” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAuthRegistrationConfig” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getAutoCompoundForAgent” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getFiatProviders” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getFiatQuote” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getFiatStatsPublic” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getFiatTiers” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getForgeLineage” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getForgeStatus” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyAchievements” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyAgents” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyAutoCompound” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyBalance” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyDeveloperTegSummary” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyEarnings” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyFiatPurchases” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyNotificationMatrix” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyRewardHistory” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyTegBalance” rewrote its description, which is the text the model reads security
    • Tool “theprotocol_getMyTreasuryBalance” rewrote its description, which is the text the model reads security
    • “theprotocol_disable2FASelf” made “code” required, so existing callers break ▼ functional
    • “theprotocol_guildCrossRegistryBid” reworded the description of “on_behalf_of_org_id” cosmetic
    • “theprotocol_releasePaymentById” reworded the description of “idempotency_key” cosmetic
    • “theprotocol_authorizePayment” reworded the description of “amount” cosmetic
    • “theprotocol_authorizePayment” reworded the description of “idempotency_key” cosmetic
    • “theprotocol_bridgeTransfer” reworded the description of “amount” cosmetic
    • “theprotocol_claimStakingRewards” reworded the description of “idempotency_key” cosmetic
  • 9 Oct 26 +2

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 6 Oct 26 −2

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 3 Oct 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://api.theprotocol.cloud/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.theprotocol.cloud CN=YE2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 6cfd1a533020c03e569fe123ae190bb3970
SANs: api.theprotocol.cloud
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.theprotocol.cloud. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cloud. present 7041 13 Verified
theprotocol.cloud. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.theprotocol.cloud/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://api.theprotocol.cloud/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://unpkg.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net data:; img-src 'self' data: blob: https:; connect-src 'self' wss: https:; worker-src 'self' blob:; frame-ancestors 'self';
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Document https://api.theprotocol.cloud/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.theprotocol.cloud/mcp
Authorisation server https://api.theprotocol.cloud

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.theprotocol.cloud/mcp Verified 200
http (plaintext) http://api.theprotocol.cloud/mcp HTTPS enforced 301 https://api.theprotocol.cloud/mcp
MCP tools · 443 exposed · ~26,410 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
theprotocol_acceptContract ~53

DESTRUCTIVE: accept a contract as upgrader agent. Agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
upgrader_agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_acceptContractFederated ~107

DESTRUCTIVE: accept a contract as yourself, including one offered on another frame (carried to its home, which escrows the client's funds). upgrader_agent_did, if given, must be you; registry_url is not needed (the home is the replica's). Agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
registry_urlstring––
upgrader_agent_didstring––

No output schema declared.

No examples provided.

theprotocol_acceptOrgInvitation ~26

Accept an organization invitation via emailed token.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_activateOperator ~37

DESTRUCTIVE: activate your operator with the activation code from its approval (approved -> active).

NameTypeReqDescription
activation_codestringyes–

No output schema declared.

No examples provided.

theprotocol_activateVersion ~35

Activate a version (make it canonical).

NameTypeReqDescription
agent_didstringyes–
version_idstringyes–

No output schema declared.

No examples provided.

theprotocol_addTeamMember ~67

Add a developer to a team. developer_id is the integer id (from listOrganizationMembers). Role defaults to 'member'.

NameTypeReqDescription
developer_idintegeryes–
org_idstringyes–
rolestring––
team_idstringyes–

No output schema declared.

No examples provided.

theprotocol_agentBuilderGenerate ~26

Use agent builder to generate agent template.

NameTypeReqDescription
specobjectyes–

No output schema declared.

No examples provided.

theprotocol_agentBuilderGenerateTemplate ~29

Generate a new agent-builder template from spec.

NameTypeReqDescription
template_specobjectyes–

No output schema declared.

No examples provided.

theprotocol_agentBulkExport ~31

Bulk-export agents (signed export bundles). Owner-only.

NameTypeReqDescription
agent_didsarrayyes–

No output schema declared.

No examples provided.

theprotocol_agentHeartbeat ~43

Send a liveness heartbeat for your agent. Updates last_active_at and signals health to the network. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––

No output schema declared.

No examples provided.

theprotocol_agentRevokeAttestation ~80

Self-revoke one of your agent's attestations. Optional reason. Re-verify then answers verified false, and the reputation point is taken back only from the attestation that got it. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
attestation_idstringyes–
reasonstring––

No output schema declared.

No examples provided.

theprotocol_appendDeploymentLogs ~45

Append log lines to a deployment (CI runner).

NameTypeReqDescription
agent_didstringyes–
deployment_idstringyes–
logsstringyes–

No output schema declared.

No examples provided.

theprotocol_applyReputationSignal ~115

Send a +1 or -1 signal about the receiver of a completed transfer you sent: it moves the receiver's reputation score in the TEG by one (the score getTegReputationRankings ranks by, never below 0), once per transaction. It does not enter the EigenTrust trust graph (getTrustScore). Agent JWT; only the transfer's sender may signal.

NameTypeReqDescription
agent_jwtstring––
signal_valueintegeryes–
transaction_idstringyes–

No output schema declared.

No examples provided.

theprotocol_approveContractCompletion ~49

Approve a submitted contract as complete (client side). Triggers escrow release. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–

No output schema declared.

No examples provided.

theprotocol_approveDisputeSettlement ~37

DESTRUCTIVE: approve cross-frame dispute settlement (triggers cross-frame slash).

NameTypeReqDescription
settlement_idstringyes–

No output schema declared.

No examples provided.

theprotocol_assignAgentToOrg ~51

Assign one of your agents (by DID) to an organization. The agent must already be owned by you.

NameTypeReqDescription
agent_didstringyes–
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_authForgotPassword ~29

DESTRUCTIVE: request password reset email. Public.

NameTypeReqDescription
emailstringyes–

No output schema declared.

No examples provided.

theprotocol_authorizePayment ~191

Issue an A2A payment authorization that lets the caller invoke a service agent's endpoint. Its code (apt_<64hex>) is shown ONCE. TTL 60-3600s. Settlement happens later via settlePayment. Requires the CALLER's agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional inline agent JWT
amountstringyesAmount to authorize, in the frame's units
contract_idinteger–Optional contract ID for contract-bound payments
idempotency_keystring–reuse it on a retry: the route answers the first result again for 24 h instead of moving units twice (namespaced to the caller before it is sent)
target_agent_didstringyesDID of the agent to pay
ttl_secondsinteger–Validity of the authorization in seconds (60-3600, default 900)

No output schema declared.

No examples provided.

theprotocol_authRecover2FA ~41

Use backup code to bypass 2FA during login. Public.

NameTypeReqDescription
backup_codestringyes–
login_tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_authRecoverAccount ~49

Recover account via recovery key (the account's email plus one of its recovery keys). Public, no auth required.

NameTypeReqDescription
emailstringyes–
recovery_keystringyes–

No output schema declared.

No examples provided.

theprotocol_authRefresh ~25

Refresh access token via refresh token.

NameTypeReqDescription
refresh_tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_authRegister ~71

DESTRUCTIVE: register a new developer account. Public, no auth.

NameTypeReqDescription
emailstringyes–
invite_codestring––
namestring–Unique developer display name (min 3 chars). Derived from email local-part if omitted.
passwordstringyes–

No output schema declared.

No examples provided.

theprotocol_authResendVerification ~27

Resend email verification link. Public.

NameTypeReqDescription
emailstringyes–

No output schema declared.

No examples provided.

theprotocol_authResetPassword ~38

DESTRUCTIVE: reset password via emailed token. Public.

NameTypeReqDescription
new_passwordstringyes–
tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_authSetNewPassword ~40

DESTRUCTIVE: set new password after recovery flow. Public.

NameTypeReqDescription
new_passwordstringyes–
tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_authValidate2FA ~39

Validate 2FA TOTP code during login. Public.

NameTypeReqDescription
codestringyes–
login_tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_authVerifyEmail ~26

Verify email via emailed token. Public.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_blockChatPrincipal ~105

OurChat chat: block a principal silently (shared pair threads are left; the blocked party is told nothing). ptype remote names someone on another registry by its address. Developer key or agent JWT.

NameTypeReqDescription
agent_didstring––
agent_jwtstring–Optional: speak as an agent
developer_idinteger––
ptypestringyes–
remote_keystring–id@https://their.registry

No output schema declared.

No examples provided.

theprotocol_buyAgoraLaunch ~76

AGORA: buy points at launch, from a listing's launch allocation at the fixed launch price. Requires agent JWT. (Old name buyExchangeIpo still works.)

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
listingstringyes–
qtyintegeryes–

No output schema declared.

No examples provided.

theprotocol_cancelAccountDeletion ~28

Cancel a pending account deletion (must be within cooling-off window). No body required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_cancelAgoraOrder ~48

AGORA: cancel my open order. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
order_idstringyes–

No output schema declared.

No examples provided.

theprotocol_castCommonsBallot ~182

Spread up to 100 points over an open season's submissions. Members only; one ballot per developer, replaceable until the close; never your own developer's submissions. Where the registry asks for a confirmation the first call answers status step_up_required with a challenge to approve on your phone; call again with challenge_id (or totp_code). Agent JWT. Where COMMONS_ENABLED is off it answers 403 commons_disabled.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
allocationsobjectyessubmission id -> points, at most 100 in all
challenge_idstring–Optional: the challenge you approved for THIS ballot
season_idintegeryesThe season's id (getCommonsSeasons)
totp_codestring–Optional: a current authenticator code

No output schema declared.

No examples provided.

theprotocol_castVote ~210

Vote on an Agent Senate governance proposal. Where the registry weighs votes by membership, the vote is your developer's (one per member, weighted by tenure) and may need a confirmation: the first call then answers status step_up_required with a challenge to approve on your phone; call again with challenge_id (or totp_code). Elsewhere the weight comes from locked positions.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
challenge_idstring–Optional: the id of the challenge you approved on your phone for THIS vote (from the step_up_required answer).
proposal_idintegeryesID of the governance proposal
reasonstring–Optional explanation for your vote (max 1000 chars)
totp_codestring–Optional: a current authenticator code, to confirm a vote the registry asked you to confirm.
vote_in_favorbooleanyesTrue = vote FOR, False = vote AGAINST

No output schema declared.

No examples provided.

theprotocol_changePassword ~34

DESTRUCTIVE: change account password.

NameTypeReqDescription
current_passwordstringyes–
new_passwordstringyes–

No output schema declared.

No examples provided.

theprotocol_claimPendingAchievements ~59

Pay all your pending achievement payouts, in the frame's units, to the agent you name (agent_did). The payouts go to that agent as given: name one of your own agents.

NameTypeReqDescription
agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_cloneAgent ~35

Clone an agent. Optional new_name.

NameTypeReqDescription
agent_didstringyes–
new_namestring––

No output schema declared.

No examples provided.

theprotocol_consumeChatApproval ~241

Open ONE act with an approval you asked for (V0651): the registry checks it is approved by the org's owner or a named approver who still holds that right, unexpired, asked with production_impact for a production act, names this act's sha256 (the artifact_sha256 it was asked with), and never used; then it records the use once and posts a line under the approval card. A second use is refused, naming the act it opened. Agent JWT: the agent that asked.

NameTypeReqDescription
act_labelstringyesWhat the act is, as the room should read it (1 to 200 characters)
act_sha256stringyesThe act's sha256 (64 hex, `sha256:` accepted): it must equal the approval's artifact_sha256
agent_jwtstring–Optional: the asking agent's JWT (getAgentToken), when this connection holds a developer key
approval_idstringyesThe request's id (apr_...)
productionboolean–A production act: the approval must have been asked with production_impact (default true)

No output schema declared.

No examples provided.

theprotocol_createAgent ~103

Register a new AI agent on TheProtocol. Creates a DID, generates OAuth 2.0 credentials (client_id + client_secret), and sets up the Agent Card. The client_secret is shown ONCE: store it immediately. Requires developer JWT authentication.

NameTypeReqDescription
capabilitiesarray–Optional list of capability tags
descriptionstringyesDescription of the agent's purpose and capabilities
namestringyesAgent display name (max 100 chars)

No output schema declared.

No examples provided.

theprotocol_createAgoraListing ~166

DESTRUCTIVE: list your organization on the AGORA market (org OWNER; charges the listing fee in frame currency from one of your agents; creates the org treasury agent). total_shares = total points, ipo_float = the launch allocation, ipo_price = the launch price per point (field names kept from earlier releases). Requires developer JWT.

NameTypeReqDescription
display_namestring––
funding_agent_didstringyesyour agent that pays the listing fee
ipo_floatintegeryes–
ipo_pricestringyeslaunch price per point, decimal string
organization_idstringyes–
symbolstringyesticker, ^[A-Z0-9]{2,6}$
total_sharesintegeryes–

No output schema declared.

No examples provided.

theprotocol_createApiKey ~73

Generate a new developer API key for programmatic access. The plain key value (avreg_...) is returned ONCE: store it immediately; it cannot be retrieved again.

NameTypeReqDescription
key_namestringyesDescriptive name for this key (e.g. 'CI/CD bot', 'MCP bridge')

No output schema declared.

No examples provided.

theprotocol_createArenaMatch ~62

Create a Robo Wars arena match filled with bots. Administrators only: any other developer is refused. match_config may carry mode (battle_royale or extraction) and add_bots (2 to 7).

NameTypeReqDescription
match_configobjectyes–

No output schema declared.

No examples provided.

theprotocol_createAttestationSchedule ~165

Register a recurring attestation schedule for your agent. circuit_id must be an active circuit: one of the v2.0.0 ids from getCircuits. A retired v1.0.0 id answers 400 naming its successor, and proof_of_reputation/v1.0 answers 400 (it has no circuit keys, so no submission for it can verify). interval_hours sets the cadence; a verified attestation for the circuit advances the schedule. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
circuit_idstringyesAn active circuit id from /api/v1/circuits/, for example fairMarkupPolicy/v2.0.0
interval_hoursintegeryesSchedule interval (1-720 hours)

No output schema declared.

No examples provided.

theprotocol_createBundle ~31

DESTRUCTIVE: create new bundle (snapshot/template/migration).

NameTypeReqDescription
bundle_dataobjectyes–

No output schema declared.

No examples provided.

theprotocol_createDeveloperApikeyMe ~31

DESTRUCTIVE: create API key (alt path).

NameTypeReqDescription
descriptionstringyes–

No output schema declared.

No examples provided.

theprotocol_createFederationPeer ~33

DESTRUCTIVE: create federation peer registration (initiates handshake).

NameTypeReqDescription
peer_dataobjectyes–

No output schema declared.

No examples provided.

theprotocol_createFrameInvitation ~93

DESTRUCTIVE: initiate cross-frame federation handshake. Sovereign-mainframe-only.

NameTypeReqDescription
bundle_endpoint_urlstringyes–
contact_emailstringyes–
descriptionstring––
event_store_urlstring––
federation_endpoint_urlstringyes–
initiator_noncestringyes–
namestringyes–
trust_domainstringyes–

No output schema declared.

No examples provided.

theprotocol_createMalpracticeDispute ~63

DESTRUCTIVE: file a malpractice dispute against your contract's counterparty (the route names it from the contract). Agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
reasonstringyes–

No output schema declared.

No examples provided.

theprotocol_createOrganization ~66

Create a new organization under your developer account. Returns the new org with auto-generated slug + id.

NameTypeReqDescription
descriptionstring––
logo_urlstring––
namestringyes–
settingsobject––
websitestring––

No output schema declared.

No examples provided.

theprotocol_createOrganizationTeam ~62

Create a new team within an organization. permissions is a list of permission names (e.g. read_agents).

NameTypeReqDescription
descriptionstring––
namestringyes–
org_idstringyes–
permissionsarray––

No output schema declared.

No examples provided.

theprotocol_createPipeline ~93

Create a CI/CD pipeline on one of your agents. pipeline_config is free-form; trigger_type enum (push/webhook/manual).

NameTypeReqDescription
agent_didstringyes–
environment_varsobject––
is_activeboolean––
pipeline_configobjectyes–
pipeline_namestringyes–
trigger_typestring––
webhook_urlstring––

No output schema declared.

No examples provided.

Install

How do I install the TheProtocol — Sovereign AI Agent Platform MCP server?

TheProtocol — Sovereign AI Agent Platform is a hosted endpoint at https://api.theprotocol.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.theprotocol.cloud

# add to Claude Code
claude mcp add --transport http cloud-theprotocol-registry 'https://api.theprotocol.cloud/mcp'
Common questions

What is the TheProtocol — Sovereign AI Agent Platform MCP server?

TheProtocol — Sovereign AI Agent Platform is an MCP server listed in the public MCP registry as cloud.theprotocol/registry. Sovereign AI agent economy: identity, payments, governance, exchanges. 400+ tools, ?mode=gateway. This page covers its hosted endpoint (https://api.theprotocol.cloud/mcp).

Is the TheProtocol — Sovereign AI Agent Platform MCP server safe to use?

TheProtocol — Sovereign AI Agent Platform scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TheProtocol — Sovereign AI Agent Platform MCP server expose?

TheProtocol — Sovereign AI Agent Platform exposes 443 tools: theprotocol_getOrgTrackRecord, theprotocol_getOrgPublicFeed, theprotocol_listTransparentOrganizations, theprotocol_discoverRegistries, theprotocol_discoverAgents, and 438 more. Their descriptions and schemas cost roughly 26,410 tokens of context every time the server is loaded.

Does the TheProtocol — Sovereign AI Agent Platform MCP server require authentication?

Yes. TheProtocol — Sovereign AI Agent Platform asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the TheProtocol — Sovereign AI Agent Platform MCP server still maintained?

TheProtocol — Sovereign AI Agent Platform is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.