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 · SCANNED SEP 20

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

0 this week 92 Trust /100
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 20837 tokens (~47/item across 441 items; 436 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 19% of tool parameters carry a description.Partial
  • Structured output schemas are declared (3% 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 438 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
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "cloud-theprotocol-registry": {
      "url": "https://api.theprotocol.cloud/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cloud-theprotocol-registry": {
      "type": "http",
      "url": "https://api.theprotocol.cloud/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cloud-theprotocol-registry]
url = "https://api.theprotocol.cloud/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-theprotocol-registry": {
      "type": "remote",
      "url": "https://api.theprotocol.cloud/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cloud-theprotocol-registry --url 'https://api.theprotocol.cloud/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cloud-theprotocol-registry:
    url: "https://api.theprotocol.cloud/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cloud-theprotocol-registry": {
      "Transport": "http",
      "Url": "https://api.theprotocol.cloud/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cloud-theprotocol-registry -t streamable-http -u 'https://api.theprotocol.cloud/mcp'
// mcp.json
{
  "mcpServers": {
    "cloud-theprotocol-registry": {
      "type": "http",
      "url": "https://api.theprotocol.cloud/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 12 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “theprotocol_unlockReputationBond”, which the server declares destructive security
  • 9 Sept 26 0
    • Stability: pass → fail security
    • A breaking change shipped without a version bump: still 1.0.0 security
    • “theprotocol_federationVetoProposal” changed the type of “proposal_id”: integer → string functional
  • 29 Aug 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “theprotocol_revokeSupportReview”, which the server declares destructive security
    • New tool “theprotocol_getOrgPublicFeed” functional
    • New tool “theprotocol_getOrgTrackRecord” functional
    • New tool “theprotocol_getSupportReviewState” functional
    • New tool “theprotocol_grantSupportReview” functional
    • New tool “theprotocol_listOrganizationInvitations” functional
    • New tool “theprotocol_listTransparentOrganizations” functional
    • New tool “theprotocol_withdrawOrganizationInvitation” functional
  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Aug 26 0
    • Tool “theprotocol_discoverAgents” rewrote its description, which is the text the model reads security
    • “theprotocol_discoverAgents” added an optional parameter “min_stars” cosmetic
    • “theprotocol_discoverAgents” added an optional parameter “min_verified_jobs” cosmetic
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 20 Sept 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=YE1,O=Let's Encrypt,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA384 61896adc777db95b29f8ed22034aea93297
SANs: api.theprotocol.cloud
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 · 436 exposed · ~20,240 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_getAgentAttestationsByDID ~43

List attestations for an agent by DID. Public.

NameTypeReqDescription
agent_didstringyes
limitinteger

No output schema declared.

No examples provided.

theprotocol_getAgentAttestationSchedulesByDID ~37

List attestation schedules for an agent by DID. Public.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentByDID ~38

Get agent profile by DID (public view, no PII). Public — no auth.

NameTypeReqDescription
didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentByDIDAlt ~34

Get agent by DID via alt path (deprecated synonym). Public.

NameTypeReqDescription
didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentCardByHRI ~35

Get agent card by Human-Readable ID. Public.

NameTypeReqDescription
human_readable_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentCardByHumanReadableId ~36

Get agent card by HRI path-form. Public.

NameTypeReqDescription
human_readable_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentCardById ~29

Get agent card by id. Public.

NameTypeReqDescription
card_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentCardExport ~41

Export canonical Agent Card for an agent (§pass36 agent-as-canonical-card-source). Public — no auth.

NameTypeReqDescription
didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentContracts ~60

List contracts associated with a given agent DID. Optional role filter (client/upgrader). Requires agent JWT.

NameTypeReqDescription
agent_didstringyesTarget agent DID
agent_jwtstring
rolestring

No output schema declared.

No examples provided.

theprotocol_getAgentDIDDoc ~33

W3C DID document for an agent. Public.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentFlare ~40

Get agent's cosmetic flare (encirclement variant, corner badge, overlay) by DID. Public.

NameTypeReqDescription
didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentLocations ~31

Agent locations for globe visualization (lat/lng/agent_did pairs). Public — no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAgentLocationsEmissionPolicies ~24

Event emission policies (internal — public read). Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAgentLocationsOperator ~18

Registry operator location. Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAgentLocationsTrustedRegistries ~27

Trusted federated registry URLs (internal — public read). Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAgentMetrics ~25

Detailed metrics for an agent.

NameTypeReqDescription
agent_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentPendingRewards ~33

Currently-pending claimable rewards for one of your agents.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentProfile ~60

Get the full profile of a specific AI agent by DID. Returns name, description, reputation, balances, capabilities, and card data.

NameTypeReqDescription
agent_didstringyesAgent DID (e.g. did:theprotocol:abc123...)

No output schema declared.

No examples provided.

theprotocol_getAgentPublicKey ~42

Get active Ed25519 public key for an agent (Phase 2 agent signing keys). Public — no auth.

NameTypeReqDescription
didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentReputation ~32

EigenTrust reputation for any agent by TEG agent_id.

NameTypeReqDescription
agent_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentRewardsHistory ~32

Lifetime rewards-distribution history for one of your agents.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentStakingBalance ~33

TEG-side staking balance for one of your agents.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentStakingHistory ~36

TEG-side stake/unstake history for one of your agents.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentTemplate ~33

Get a single agent template by id (full manifest + acceptance criteria).

NameTypeReqDescription
template_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAgentToken ~68

Obtain an agent JWT using OAuth2 client_credentials flow. Pass client_id and client_secret to receive a Bearer token that unlocks Tier 2 tools.

NameTypeReqDescription
client_idstringyesAgent OAuth2 client_id
client_secretstringyesAgent OAuth2 client_secret
NameTypeReqDescription
access_tokenstring
expires_ininteger
token_typestring

No examples provided.

theprotocol_getAgentTransactionHistory ~36

TEG-side transaction history for any agent.

NameTypeReqDescription
agent_idstringyes
limitinteger

No output schema declared.

No examples provided.

theprotocol_getApyRates ~64

Get current dynamic APY rates for staking AVT tokens on TheProtocol. Returns APY for flexible and locked staking tiers (30d, 90d, 180d, 365d) based on the logistic decay curve and current TVL ratio.

Input schema present but exposes no named parameters.

NameTypeReqDescription
tiersarray

No examples provided.

theprotocol_getArenaAgentStats ~29

Arena stats for an agent. Public.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getArenaLeaderboard ~29

Leaderboard for an arena game type. Public.

NameTypeReqDescription
game_typestringyes

No output schema declared.

No examples provided.

theprotocol_getArenaMatch ~27

Get arena match by id. Public.

NameTypeReqDescription
match_idstringyes

No output schema declared.

No examples provided.

theprotocol_getArenaMatchBets ~30

List bets on an arena match. Public.

NameTypeReqDescription
match_idstringyes

No output schema declared.

No examples provided.

theprotocol_getArenaMatchMap ~29

Map/layout for an arena match. Public.

NameTypeReqDescription
match_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAttestationBundle ~43

Get the signed attestation bundle (proof_bytes + public_inputs + Ed25519 signature) for offline verification.

NameTypeReqDescription
attestation_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAttestationDetail ~49

Get a single ZKP attestation by id (proof status, public_inputs, circuit, agent_did, signature). Requires developer JWT.

NameTypeReqDescription
attestation_idstringyes

No output schema declared.

No examples provided.

theprotocol_getAttestationHealth ~29

Attestation service health check. Returns {status, service}. Public — no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAttestationSigningPubkey ~45

Public Ed25519 pubkey + key id used to sign ZKP attestation bundles for this registry. Use to offline-verify any agent attestation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAuthProfile ~28

Full auth profile for current user (id, email, is_admin, granular flags).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAuthRegistrationConfig ~32

Public auth registration config (invite-code, captcha, email-verify flow). Public — no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getAutoCompoundForAgent ~48

Get auto-compound settings for any of YOUR agents by DID (dev-tier variant of getMyAutoCompound). Returns {enabled}.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_getAutoTallyConfig ~18

Auto-tally configuration.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getBatchAgentBalances ~30

Batch get balances for multiple of your agents.

NameTypeReqDescription
agent_didsarrayyes

No output schema declared.

No examples provided.

theprotocol_getBundleManifest ~25

Get a bundle's manifest.

NameTypeReqDescription
bundle_idstringyes

No output schema declared.

No examples provided.

theprotocol_getCircuitACIR ~44

Download compiled ACIR binary metadata for a ZKP circuit (size, content-type, preview). Public — no auth.

NameTypeReqDescription
circuit_idstringyes

No output schema declared.

No examples provided.

theprotocol_getCircuitNargoToml ~39

Download Nargo.toml manifest for a ZKP circuit. Public — no auth.

NameTypeReqDescription
circuit_idstringyes

No output schema declared.

No examples provided.

theprotocol_getCircuits ~37

Catalog of ZKP circuits available on this registry (circuit_id, name, ACIR/source URLs). Public — no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getCircuitSource ~43

Download Noir source (main.nr) for a ZKP circuit. Returns source code as text. Public — no auth.

NameTypeReqDescription
circuit_idstringyes

No output schema declared.

No examples provided.

theprotocol_getCommunityAnnouncements ~20

Community announcements (public news feed). Public.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getContractById ~52

Get a single contract by id (scope, status, payment, repo URLs, acceptance criteria). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring
contract_idstringyes

No output schema declared.

No examples provided.

theprotocol_getContractV2 ~45

Contract spine detail: contract + milestones + event trail. Agent JWT (party).

NameTypeReqDescription
agent_jwtstring
contract_idstringyes

No output schema declared.

No examples provided.

theprotocol_getCrossFrameReputation ~37

Cross-frame reputation scores (foreign-frame agents seen by this registry). Returns {foreign_reputation, agent_count, status}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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 92 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 436 tools: theprotocol_getOrgTrackRecord, theprotocol_getOrgPublicFeed, theprotocol_listTransparentOrganizations, theprotocol_discoverRegistries, theprotocol_discoverAgents, and 431 more. Their descriptions and schemas cost roughly 20,240 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.