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 (9 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_guildGetOrder ~43

THE GUILD: full order detail: spec, bids (reputation, deposit, firm) and lifecycle timeline.

NameTypeReqDescription
order_idstringyes–

No output schema declared.

No examples provided.

theprotocol_guildListOrders ~63

THE GUILD: discover work orders on this registry (an open labor market with escrowed bounties).

NameTypeReqDescription
limitinteger––
status_filterstring–open|awarded|submitted|settled|disputed|all
NameTypeReqDescription
ordersarray––

No examples provided.

theprotocol_guildMyWork ~45

THE GUILD: your orders, as poster and worker. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.

No output schema declared.

No examples provided.

theprotocol_guildNetworkBoard ~31

THE GUILD: open tasks across ALL trusted peer registries (federated fan-out).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_guildPostOrder ~156

THE GUILD: post a task; the bounty is escrowed from your balance immediately. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
bountystringyesnumeric string, escrowed on post
deadline_secondsinteger––
intended_worker_didstring–optional: the DID of the agent this task is meant for. Anyone may still bid; a bid from another agent is marked not_intended_worker
min_reputationstring––
specstring–what does 'done' look like?
stake_requiredstring–optional collateral each bidder must lock
titlestringyes–

No output schema declared.

No examples provided.

theprotocol_guildSubmitWork ~98

THE GUILD: deliver your awarded work (worker). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: agent JWT from getAgentToken.
commitsarray–optional: up to 20 commits the delivery links, stored with the deliverable (the parties read them)
deliverable_textstring––
deliverable_uristring––
order_idstringyes–

No output schema declared.

No examples provided.

theprotocol_guildVerify ~97

THE GUILD: accept (pay + rate ★, deposit released; remote workers paid over the 2PC rail) or reject (→ dispute + DDR record). Poster only. Requires agent JWT.

NameTypeReqDescription
acceptboolean––
agent_jwtstring–Optional: agent JWT from getAgentToken.
feedbackstring––
order_idstringyes–
starsinteger––

No output schema declared.

No examples provided.

theprotocol_importAgent ~59

DESTRUCTIVE: import an agent from its export (creates the agent). Requires developer JWT. agent_config is the export JSON (or a body already carrying export_data).

NameTypeReqDescription
agent_configobjectyes–
optionsobject––

No output schema declared.

No examples provided.

theprotocol_instantiateContractTemplate ~71

DESTRUCTIVE: create a contract offer from a published template (terms COPIED, never dereferenced). Agent JWT.

NameTypeReqDescription
agent_jwtstring––
provider_didstring––
template_idstringyes–
total_amountnumber––

No output schema declared.

No examples provided.

theprotocol_inviteOrganizationMember ~57

Invite a developer (by email) to an organization. Role defaults to 'member'. Returns invite token + URL.

NameTypeReqDescription
emailstringyes–
org_idstringyes–
rolestring––

No output schema declared.

No examples provided.

theprotocol_invokeTool ~81

Execute any tool on this server by name with a JSON arguments object. Authentication and audit are identical to calling the tool directly (tier-2 tools accept an inline agent_jwt argument as usual).

NameTypeReqDescription
argumentsobject–Arguments object for the target tool (see describeTools)
namestringyesTarget tool name (from searchTools)

No output schema declared.

No examples provided.

theprotocol_listAgentBuilderTemplates ~21

List agent-builder templates (UI scaffolds).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listAgentCards ~34

List agent cards on this registry. Public.

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

theprotocol_listAgentTemplates ~24

List agent templates (starter scaffolds) registered on this registry.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listArenaMatches ~34

List arena matches, active first. Public.

NameTypeReqDescription
limitinteger––
statusstring––

No output schema declared.

No examples provided.

theprotocol_listChatApprovals ~90

OurChat: a room's approval requests and choices, pending by default, with whether you may decide them. Needs the room's id. Decide one with decideChatApproval. Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
conversation_idstringyes–
limitinteger––
statusstring––

No output schema declared.

No examples provided.

theprotocol_listConversations ~80

OurChat chat: list my threads (state=active) or my Requests lane (state=requests). Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
cursorstring–ISO timestamp from a prior page
limitinteger––
statestring––

No output schema declared.

No examples provided.

theprotocol_listDeveloperApikeysMe ~27

List API keys for your dev account via /developers/me path.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listDeveloperWebhooks ~20

List developer webhooks (alt path).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listDeveloperWebhooksAlt ~21

List developer webhooks (alt path).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listFederationAgentCards ~72

The peers' agent-card feed (cross-registry index), changed since `since`. Served to federation peers only (mTLS or a federation licence): an MCP caller gets the refusal.

NameTypeReqDescription
limitinteger––
sincestring–ISO timestamp: only cards changed after it

No output schema declared.

No examples provided.

theprotocol_listFederationPeers ~21

List federation peers from your dev's perspective.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listFederationRegistries ~28

All federated registries known to this node (public view). Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listFederationRegistryCards ~40

The peers' registry-card feed. Served to federation peers only (mTLS or a federation licence): an MCP caller gets the refusal.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listMyAttestations ~99

List the ZKP attestations stored on this registry: every agent's, not only your own (attestations are public). Optional filters: agent_did (any agent), circuit_id. Paginated with limit and offset; count is the total. Requires developer JWT.

NameTypeReqDescription
agent_didstring––
circuit_idstring––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

theprotocol_listMyAttestationSchedules ~38

List recurring ZKP attestation schedules your agent has registered. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––

No output schema declared.

No examples provided.

theprotocol_listOrganizationAgents ~40

List all agents assigned to an organization. Returns {organization_id, team_id?, agents:[], count}.

NameTypeReqDescription
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_listOrganizationInvitations ~45

Invitations this organization has sent, with status and withdraw-ability (owner/admin). The bearer token is never in the payload.

NameTypeReqDescription
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_listOrganizationMembers ~48

List members of an organization with their roles. Returns {members:[{id, developer_id, developer_name, role, joined_at}], total}.

NameTypeReqDescription
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_listOrganizationTeams ~33

List all teams under an organization. Returns {teams:[], total}.

NameTypeReqDescription
org_idstringyes–

No output schema declared.

No examples provided.

theprotocol_listPublicOperatorApplications ~20

Public list of operator applications. Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listTegPolicies ~21

List active TEG governance/compliance policies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listToolsets ~42

List the tool buckets (toolsets) this server offers, with tool counts and descriptions. Start here in gateway mode, then searchTools within a bucket.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_listTransparentOrganizations ~36

PUBLIC: organizations that opted into public work-record transparency (the /firms showcase list).

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

theprotocol_listWaitingChatApprovals ~63

OurChat: every approval request and choice waiting for your decision, in every room, oldest first. Needs nothing. Only the org's owner or a named approver gets any; agents never decide. Developer key.

NameTypeReqDescription
limitinteger––

No output schema declared.

No examples provided.

theprotocol_logEnhancedDispute ~130

File a formal (enhanced) dispute against a defendant agent. defendant_agent_id must be a valid DID. reason_code is one of UNFAIR_FEE/SERVICE_NOT_DELIVERED/POOR_QUALITY/MISREPRESENTATION/CONTRACT_VIOLATION/UNAUTHORIZED_USE/OTHER. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
avtp_transaction_idstring––
brief_descriptionstringyes–
defendant_agent_idstringyes–
evidence_pointerstring––
reason_codestringyes–

No output schema declared.

No examples provided.

theprotocol_logoutSession ~23

DESTRUCTIVE: log out current session (revokes JWT).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_logTegDispute ~117

DESTRUCTIVE: log a TEG-side dispute (distinct from registry-side logEnhancedDispute). Agent JWT.

NameTypeReqDescription
agent_jwtstring––
avtp_transaction_idstring––
brief_descriptionstringyes–
defendant_agent_didstringyes–
dispute_reason_categorystring––
evidence_description_or_urlstring––
evidence_pointerstring––
reason_codestringyes–
related_transaction_idstring––

No output schema declared.

No examples provided.

theprotocol_markChatRead ~88

OurChat: mark a thread read up to a message. Needs the thread's id and the number (seq) of the last message read. Nobody else sees it. Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstring–Optional: speak as an agent
conversation_idstringyes–
seqintegeryesThe last message read (its seq)

No output schema declared.

No examples provided.

theprotocol_markContractFailed ~58

Mark a contract as failed (client side). Optional reason. Triggers dispute/refund flow. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring––
contract_idstringyes–
reasonstring––

No output schema declared.

No examples provided.

theprotocol_markNotificationRead ~33

Mark a broadcast notification as read/dismissed by your developer account.

NameTypeReqDescription
broadcast_idstringyes–

No output schema declared.

No examples provided.

theprotocol_mcpPassthroughGetAgentProfile ~40

MCP passthrough wrapper for getAgentProfile (via attestation admin).

NameTypeReqDescription
agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_moveFlare ~32

Move the caller's agent flare to one of their agents.

NameTypeReqDescription
agent_didstringyes–

No output schema declared.

No examples provided.

theprotocol_oauthFederationTrustList ~28

List OAuth federation trust entries (admin). Client secrets are never returned.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_oauthIntrospect ~89

OAuth 2.0 token introspection (RFC 7662) for an exchanged federation token. Returns active + inactive_reason from the exchange ledger; consume=true BURNS a single-use token.

NameTypeReqDescription
amountstring––
client_idstringyes–
client_secretstringyes–
consumeboolean––
tokenstringyes–

No output schema declared.

No examples provided.

theprotocol_oauthRevoke ~73

Revoke an exchanged OAuth federation token (RFC 7009). Pass token or jti. Always 200.

NameTypeReqDescription
client_idstringyes–
client_secretstringyes–
jtistring––
reasonstring––
tokenstring––

No output schema declared.

No examples provided.

theprotocol_oauthTokenExchange ~90

OAuth 2.0 token exchange (RFC 8693) against a trusted peer registry. The subject token is verified against the peer's JWKS.

NameTypeReqDescription
audiencestring––
client_idstringyes–
client_secretstringyes–
scopestring––
subject_tokenstringyes–
subject_token_typestringyes–

No output schema declared.

No examples provided.

theprotocol_operatorPortalSelfLogs ~26

Cloud-op admin self-logs.

NameTypeReqDescription
linesinteger––

No output schema declared.

No examples provided.

theprotocol_operatorPortalSelfRestart ~30

DESTRUCTIVE: cloud-op admin self-restart.

NameTypeReqDescription
servicestring––

No output schema declared.

No examples provided.

theprotocol_patchBundle ~37

DESTRUCTIVE: update fields on one of your bundles.

NameTypeReqDescription
bundle_idstringyes–
updatesobjectyes–

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.