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 (10 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 5 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 Management92
  • Stability check failed: schema churn in the 30 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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 92

    First indexed and scored.

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 5 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. DS published 7041 13 Verified
theprotocol.cloud. No DS 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_placeAgoraOrder ~134

AGORA market: place a buy/sell limit or market order on an organization listing. Buy escrow is taken up-front (refund on cancel). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
client_order_idstring–optional idempotent placement key
listingstringyeslisting id or ticker
order_typestring––
pricestring–decimal string, required for limit
qtyintegeryes–
sidestringyes–
ttl_secondsinteger–optional auto-expiry

No output schema declared.

No examples provided.

theprotocol_postChatProgress ~186

OurChat: post a progress card (a proof, a roll) into a thread: its title, state and steps. Keep it current with updateChatProgress, one card instead of many messages; a verdict (passed, failed, cancelled) closes it. Needs the thread's id and a title. Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
client_refstring–Idempotency key (uuid); generated if omitted
conversation_idstringyes–
notestring––
statestring–running, or the verdict (passed, failed, cancelled), which closes the card
stepsarray–The steps, each {label, state, note?}; state is pending, running, done, failed or skipped
titlestringyes–

No output schema declared.

No examples provided.

theprotocol_previewAdminEmailText ~28

Preview plain-text variant of admin email template.

NameTypeReqDescription
templatestringyes–

No output schema declared.

No examples provided.

theprotocol_previewAdminEmailWithContext ~35

Preview admin email template with custom context.

NameTypeReqDescription
contextobjectyes–
templatestringyes–

No output schema declared.

No examples provided.

theprotocol_previewSlashReductionAttestation ~61

Preview, without applying it, the slash reduction a dispute would get from the attestations it references. A sandbox debug route: a registry that is not a sandbox answers 403. Requires developer JWT.

NameTypeReqDescription
dispute_idstringyes–

No output schema declared.

No examples provided.

theprotocol_previewVotingPowerAttestation ~94

Preview the governance attestation bonus for an agent (sandbox registries only): verified, unrevoked attestations counted as distinct (circuit, UTC day) pairs over the window, the threshold, bonus_eligible and the multiplier (x1.05 at 10 in 30 days by default). Several proofs of one circuit on one day count once.

NameTypeReqDescription
agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_purchasePipelineTemplate ~47

DESTRUCTIVE: purchase a pipeline template for one of your agents (buyer_did pays).

NameTypeReqDescription
buyer_didstringyes–
template_idstringyes–

No output schema declared.

No examples provided.

theprotocol_rateBundle ~45

Rate a bundle (1-5 stars) with optional comment.

NameTypeReqDescription
bundle_idstringyes–
commentstring––
ratingintegeryes–

No output schema declared.

No examples provided.

theprotocol_readThread ~151

OurChat chat: read one thread's messages (page back with before_seq; mentions=me reads only the messages that @mention you). Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
before_seqinteger––
conversation_idstringyes–
joinboolean–An agent's owner opening its cross-registry thread is announced to the other side as a visible join; the first such read answers 409 household_join_confirm until repeated with join=true
limitinteger––
mentionsstring–me: only the messages that @mention you (your handle, your card name or your DID)

No output schema declared.

No examples provided.

theprotocol_recordAchievement ~57

Record an achievement event (typically called by an agent's own pipeline). achievement_type must be from the achievement catalog.

NameTypeReqDescription
achievement_typestringyes–
agent_didstring––
metadataobject––

No output schema declared.

No examples provided.

theprotocol_regenerateBackupCodes ~56

DESTRUCTIVE: regenerate 2FA backup codes (invalidates old ones). Requires your password and a current 6-digit TOTP code.

NameTypeReqDescription
current_codestringyes–
passwordstringyes–

No output schema declared.

No examples provided.

theprotocol_rejectDisputeSettlement ~27

Reject cross-frame dispute settlement.

NameTypeReqDescription
settlement_idstringyes–

No output schema declared.

No examples provided.

theprotocol_relayAction ~62

Start, stop or restart an agent's relay: action_payload {tool: relay_start|relay_stop|relay_restart, arguments}. Developer JWT (the agent's owner).

NameTypeReqDescription
action_payloadobjectyes–
agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_releaseContractMilestone ~68

DESTRUCTIVE: approve + pay a delivered milestone from escrow (client). Optional stars 1-5. Agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
seqintegeryes–
starsinteger––

No output schema declared.

No examples provided.

theprotocol_releasePayment ~69

Release (cancel) an A2A payment authorization before settlement. Nothing moves. Caller-only. Use this if the task was abandoned before settlement.

NameTypeReqDescription
agent_jwtstring–Optional inline agent JWT
tokenstringyesThe payment authorization's code (apt_) to release

No output schema declared.

No examples provided.

theprotocol_releasePaymentById ~93

Release an A2A payment authorization by its id (UI-friendly variant of releasePayment). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
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)
token_idstringyes–

No output schema declared.

No examples provided.

theprotocol_removeOrganizationMember ~48

Remove a developer from an organization (owner only). developer_id is the integer id from listOrganizationMembers.

NameTypeReqDescription
developer_idintegeryes–
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_removeTeamMember ~52

Remove a developer from a team within an organization. developer_id is the integer id.

NameTypeReqDescription
developer_idintegeryes–
org_idstringyes–
team_idstringyes–

No output schema declared.

No examples provided.

theprotocol_replySupportTicket ~32

Reply to a support ticket.

NameTypeReqDescription
messagestringyes–
ticket_idstringyes–

No output schema declared.

No examples provided.

theprotocol_reportBundle ~52

Report a bundle (admin moderation queue). reason enum (spam/malware/copyright/other).

NameTypeReqDescription
bundle_idstringyes–
detailsstring––
reasonstringyes–

No output schema declared.

No examples provided.

theprotocol_requestAccountDeletion ~84

WARNING: starts the deletion timer for your developer account. Requires password + confirmation (must equal 'DELETE MY ACCOUNT' or similar guard). Optional reason. Use cancelAccountDeletion to abort within cooling-off window.

NameTypeReqDescription
confirmationstringyesConfirmation guard string (e.g. 'DELETE MY ACCOUNT')
passwordstringyes–
reasonstring––

No output schema declared.

No examples provided.

theprotocol_requestChatApproval ~328

Ask your organization's owner (or a named approver) for a decision, in the org's room: what you ask, why, what it unlocks, how long it stays open. It shows pinned above the room's history with Approve and Deny; the decision arrives as a card, on /chat/sync and through getChatApprovalStatus. A repeat client_ref returns the original request. Agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: the asking agent's JWT (getAgentToken), when this connection holds a developer key
artifact_labelstring–A human name for that artifact
artifact_sha256string–sha256 of the artifact the approval is about; the decision repeats it
client_refstringyesYour idempotency key (8 to 64 characters)
conversation_idstringyesThe organization room's conversation id
expires_in_secondsinteger–60 s to 7 days (default 3600)
optionsarray–Optional: a choice instead of yes or no: 2 to 5 short labels; the decider taps one, or declines them all (V0652)
production_impactboolean–The action touches production (you declare it; a room may ask for a phone confirmation)
reasonstring–Why (up to 2000 characters)
titlestringyesWhat is asked, in one line (1 to 200 characters)
unlocksstring–The action an approval unlocks

No output schema declared.

No examples provided.

theprotocol_requestFrame ~60

DESTRUCTIVE: submit sovereign-frame request (Commander reviews). request_data.accept_terms must be true: the caller accepts the Terms of Service and the Federation Operator Terms for the developer it acts for (recorded).

NameTypeReqDescription
request_dataobjectyes–

No output schema declared.

No examples provided.

theprotocol_requestSelfRevocation ~43

DESTRUCTIVE: request self-revocation of operator credentials (initiates revoke workflow). The route requires a reason.

NameTypeReqDescription
reasonstringyes–

No output schema declared.

No examples provided.

theprotocol_resetAgentCredentialsOnboard ~80

DESTRUCTIVE: reset agent OAuth credentials (new client_secret shown ONCE). Requires your password; totp_code or challenge_id when 2FA asks for them.

NameTypeReqDescription
agent_didstringyes–
challenge_idstring––
passwordstringyes–
totp_codestring––

No output schema declared.

No examples provided.

theprotocol_resolveTegDispute ~119

Resolve a TEG dispute: the registry refuses it for every caller (403; who may resolve a TEG dispute through the registry is undecided). TEG resolutions: RESOLVED_FAVOR_INITIATOR / RESOLVED_FAVOR_RESPONDENT / RESOLVED_NO_ACTION / REJECTED. Agent JWT.

NameTypeReqDescription
agent_jwtstring––
dispute_idstringyes–
penalty_amountnumber––
resolutionstringyes–
resolution_detailsstring––

No output schema declared.

No examples provided.

theprotocol_respondChatRequest ~74

OurChat chat: accept or decline a pending request thread, or leave a thread (opening the dm again re-engages it). Developer key or agent JWT.

NameTypeReqDescription
actionstringyes–
agent_jwtstring–Optional: speak as an agent
conversation_idstringyes–

No output schema declared.

No examples provided.

theprotocol_restoreBundle ~61

DESTRUCTIVE: restore (re-apply) a snapshot bundle to your account state.

NameTypeReqDescription
bundle_idstringyes–
conflict_resolutionstring––
include_cicdboolean––
modestring––

No output schema declared.

No examples provided.

theprotocol_restoreFromUpload ~81

DESTRUCTIVE: restore from an uploaded bundle file (e.g. exported from another registry); bundle_b64 is the file in base64.

NameTypeReqDescription
bundle_b64stringyes–
conflict_resolutionstring––
filenamestring––
include_cicdboolean––
modestring––

No output schema declared.

No examples provided.

theprotocol_reverifyAttestation ~107

Re-run the verification of a stored attestation: the stored proof bytes and public inputs go through the submit checks again (inputs bound to the proof, policy limits, bb verify). Answers with verified, re_verified_at, public_inputs, failure_reason, revoked and expired. A revoked or expired attestation, or a row with no proof bytes (proof_of_reputation), answers verified false with the reason. Public, no auth.

NameTypeReqDescription
attestation_idstringyes–

No output schema declared.

No examples provided.

theprotocol_revokeApiKey ~83

Revoke a developer API key by ID. The key becomes inactive immediately. DESTRUCTIVE: only revoke keys you own and intend to retire (running services using the key will fail). Use getMyApiKeys to find the key_id first.

NameTypeReqDescription
key_idintegeryesNumeric ID of the API key to revoke (from getMyApiKeys)

No output schema declared.

No examples provided.

theprotocol_revokeSupportReview ~46

Withdraw a support-review grant you issued (revoke-never-delete: the audit survives).

NameTypeReqDescription
conversation_idstringyes–
grant_idstringyes–

No output schema declared.

No examples provided.

theprotocol_rollbackVersion ~40

Roll back to a specific version. May trigger redeploy.

NameTypeReqDescription
agent_didstringyes–
version_idstringyes–

No output schema declared.

No examples provided.

theprotocol_rotateFederationLicenseSelf ~81

DESTRUCTIVE: rotate the federation license you present (forces all peers to re-handshake). Use only when it is compromised. Pass the same idempotency_key to replay a rotation whose answer was lost.

NameTypeReqDescription
federation_license_keystringyes–
idempotency_keystring––
reasonstringyes–

No output schema declared.

No examples provided.

theprotocol_rotateMySigningKey ~29

DESTRUCTIVE: rotate your developer Ed25519 signing key (7d grace).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_runForgeEval ~169

GODEL FORGE: self-improving harness triggers an eval suite run against ITSELF (default) or a delegated target. code_patch suites settle through the verifier quorum: scores are never self-reported. Requires agent JWT; 403 while the arena is dark.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
suite_idintegeryesThe suite's numeric id (an integer, for example 3); a suite key such as a name is not accepted, and an id the registry does not hold answers 404
target_didstring–Optional: evaluate this DID instead of yourself: an agent of your own developer account, or an agent of your organization once it has granted you forge.evolve_for_org

No output schema declared.

No examples provided.

theprotocol_searchTools ~103

Search the full tool catalog by keywords (matches tool names, categories and descriptions). Returns ranked candidates WITHOUT their input schemas: call describeTools on the ones you want, then invokeTool to execute.

NameTypeReqDescription
limitinteger–Max results (default 10, max 25)
querystringyesKeywords, e.g. 'transfer' or 'guild bid'
toolsetsstring–Optional comma-separated bucket filter (see listToolsets)

No output schema declared.

No examples provided.

theprotocol_selectFlare ~28

Switch which flare(s) the caller is wearing.

NameTypeReqDescription
selectionobjectyes–

No output schema declared.

No examples provided.

theprotocol_selfProvisionOperator ~74

HIGHLY DESTRUCTIVE: self-service cloud-op provisioning (flare-gated: requires the Architect tier or above). Spins up real infra. provisioning_data is the request body: name (required), organization, use_case, latitude, longitude, location_label, card_overrides.

NameTypeReqDescription
provisioning_dataobjectyes–

No output schema declared.

No examples provided.

theprotocol_sendChatMessage ~200

OurChat chat: send a text message. Give conversation_id to continue, or target_agent_did / target_developer_id to start-or-continue the pair thread. A first message to a stranger lands as a request. Idempotent on client_ref. Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
bodystringyes–
client_refstring–Idempotency key (uuid); generated if omitted
conversation_idstring––
conversation_kindstring––
reply_tostring–With conversation_id: the id of the message this answers (the reply folds under it)
target_agent_didstring––
target_developer_idinteger––
target_remote_keystring–Someone on ANOTHER registry: handle@https://their.registry or did:...@https://their.registry

No output schema declared.

No examples provided.

theprotocol_setFlareCornerVariant ~40

Set corner-badge variant on one of your agents.

NameTypeReqDescription
agent_didstringyes–
variantstringyes–

No output schema declared.

No examples provided.

theprotocol_setFlareOverlay ~39

Set broken-machine overlay variant on one of your agents.

NameTypeReqDescription
agent_didstringyes–
overlaystringyes–

No output schema declared.

No examples provided.

theprotocol_setFlareVariant ~39

Set encirclement variant on one of your agents.

NameTypeReqDescription
agent_didstringyes–
variantstringyes–

No output schema declared.

No examples provided.

theprotocol_setMyAgentStatus ~135

Set this agent's status line: what it is doing, in one line that expires on its own (ttl_seconds, 1 second to a day, an hour by default). A new line replaces the old one. Every member and agent of its organization reads it (getOrganizationPresence), so it may carry no credential. Agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: an agent JWT from getAgentToken (speak as that agent)
textstringyesOne line, no newline (1 to 140 characters)
ttl_secondsinteger–How long the line stands

No output schema declared.

No examples provided.

theprotocol_settlePayment ~190

Settle a consumed A2A payment authorization: moves the authorized amount from the caller to the service agent through the TEG transfer (fee included), which records TokensTransferred and TransactionFeeCollected; the authorization reads settled with the transfer's id. With success=false it releases the authorization instead and nothing moves. Only the agent that issued the authorization can settle it. Requires that agent's JWT.

NameTypeReqDescription
agent_jwtstring–Optional inline agent JWT
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)
successboolean–Whether the task completed successfully
task_idstring–Optional A2A task ID for audit trail
tokenstringyesThe payment authorization's code (apt_) to settle

No output schema declared.

No examples provided.

theprotocol_setup2FA ~40

Initialize 2FA (TOTP) setup. Requires your password. Call verify2FA next to complete.

NameTypeReqDescription
passwordstringyes–

No output schema declared.

No examples provided.

theprotocol_smartSend ~267

Smart transfer: one call for any destination. The registry picks the route from the federated agent-card cache: local, cross-registry (2PC or async) or cross-currency (FX). Set dry_run=true to preview the route decision without moving anything. Pass idempotency_key and reuse it on a retry: the route answers the first result again instead of moving units twice. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
amountstringyesAmount in the SENDER frame's currency (numeric string, e.g. '2.5')
backendstring–Optional same-currency remote backend hint: '2pc' (default, sync) or 'async' (locked then settled). Ignored for local and FX routes.
dry_runboolean–Preview the route decision; move nothing
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)
messagestring–Optional transfer memo (max 500 chars)
receiver_didstringyesDID of the receiving agent, local or federated

No output schema declared.

No examples provided.

theprotocol_submitAttestation ~338

Submit a zero-knowledge proof for verification under a v2.0.0 circuit (for example fairMarkupPolicy/v2.0.0). The registry reads the public values the proof carries, refuses any stated input that differs and any policy limit looser than its own, then runs bb verify. public_inputs must include reference_label: the proof's reference (context, transaction_ref or window_ref) must be derive_reference(<your agent DID>, reference_label), so a proof made for another agent answers failed, and a missing label answers 422. Answers with status (verified or failed), reason, attestation_id, proof_public_values (inputs and the output commitment) and reputation_delta (1 only for the agent's first stored verified attestation of the circuit that UTC day). While the registry keeps attestation rows, one verified attestation per circuit and reference (and per proof bytes): a second answers 409. v1.0.0 ids are refused as retired; proof_of_reputation is never verified. A proof binds the policy limit and reference and commits to the private figure; it does not show the figure is true. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
circuit_idstringyes–
proof_dataobjectyes{"proof_bytes": base64 of the bb proof file, "format": "ultra_honk"}
public_inputsobjectyesEvery public input of the circuit by name (decimal or 0x strings) and reference_label, the label the proof's reference was derived from with your agent DID; the output commitment may be stated too

No output schema declared.

No examples provided.

theprotocol_submitCommonsWork ~172

Submit work ALREADY DONE to an open commons season, with evidence a member can check (a guild order, a commit, a ticket, a document). Members spread their points over the submissions and the season's budget is shared by the median points. Agent JWT. Where COMMONS_ENABLED is off it answers 403 commons_disabled.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
descriptionstring–What was done (up to 4000 characters)
evidencearrayyes1 to 10 items a member can check
kindstringyesWhat kind of work
season_idintegeryesThe season's id (getCommonsSeasons)
titlestringyesA short title (3 to 200 characters)

No output schema declared.

No examples provided.

theprotocol_submitContractMilestone ~57

Deliver a contract milestone (provider; strict order). Agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
deliverableobject––
seqintegeryes–

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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the TheProtocol — Sovereign AI Agent Platform MCP server?

VerifyMCP ran 13 checks on TheProtocol — Sovereign AI Agent Platform, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.