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_createProposal ~138

Create a new governance proposal in the Agent Senate. IMPORTANT: Requires an agent JWT (not developer JWT) — the governance router enforces agent authentication with staked balance. Call getAgentToken first, then pass the result as agent_jwt.

NameTypeReqDescription
agent_jwtstringyesAgent JWT from getAgentToken. REQUIRED.
descriptionstringyesDetailed description of the proposal
duration_daysintegerVoting duration in days (1–30, default 7)
proposal_typestring'standard' or 'policy_change'
titlestringyesShort proposal title (max 200 chars)

No output schema declared.

No examples provided.

theprotocol_createTegPoliciesBatch ~33

DESTRUCTIVE: create multiple TEG policies in one call.

NameTypeReqDescription
policiesarrayyes

No output schema declared.

No examples provided.

theprotocol_createTegPolicy ~75

DESTRUCTIVE: create a TEG policy. Requires admin_treasury flag.

NameTypeReqDescription
descriptionstring
enforcement_levelstring
parametersobject
policy_codestringyes
policy_namestringyes
policy_typestringyes

No output schema declared.

No examples provided.

theprotocol_createVersion ~66

Create a new code version for an agent. version is semver string.

NameTypeReqDescription
agent_didstringyes
commit_hashstring
is_stableboolean
release_notesstring
versionstringyes

No output schema declared.

No examples provided.

theprotocol_createWebhook ~86

Register a new webhook subscription. Events fired on listed event types POST to your URL. Use getSupportedWebhookEvents for valid types.

NameTypeReqDescription
descriptionstringOptional human-readable description
eventsarrayyesEvent type list, e.g. ['agent.created', 'staking.position_created']
urlstringyesReceiver endpoint URL (must accept POST + signature header)

No output schema declared.

No examples provided.

theprotocol_crossRegistryContractProxy ~43

DESTRUCTIVE: proxy contract action to another registry. Agent JWT.

NameTypeReqDescription
action_dataobjectyes
agent_jwtstring

No output schema declared.

No examples provided.

theprotocol_crossTegBalanceSync ~51

Notify this registry of a cross-TEG credit (typically TEG-to-TEG). Agent JWT.

NameTypeReqDescription
agent_jwtstring
notificationobjectyes

No output schema declared.

No examples provided.

theprotocol_customizeFlare ~34

Customize the caller's flare (display name, tagline, logo, link).

NameTypeReqDescription
customizationsobjectyes

No output schema declared.

No examples provided.

theprotocol_declareExchangeDividend ~64

DESTRUCTIVE: declare a dividend on your org's AGORA listing (org admin; pays from the org treasury agent pro-rata to holders).

NameTypeReqDescription
listingstringyeslisting id or ticker
per_sharestringyesdecimal string per share

No output schema declared.

No examples provided.

theprotocol_deleteBundle ~31

DESTRUCTIVE: delete one of your bundles. Owner-only.

NameTypeReqDescription
bundle_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteFederationPeerSelf ~34

DESTRUCTIVE: delete a federation peer registration (own peer).

NameTypeReqDescription
peer_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteMyAgent ~27

DESTRUCTIVE: delete the calling agent (self-delete via /agents/me).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_deleteMyAgentByDev ~37

HIGHLY DESTRUCTIVE: delete one of your agents from dev account.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_deleteMyApiKey ~31

DESTRUCTIVE: deactivate one of your API keys.

NameTypeReqDescription
key_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteOrganization ~37

Delete an organization (owner only, irreversible). Cascades to teams + memberships + agent assignments.

NameTypeReqDescription
org_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteOrganizationTeam ~43

Delete a team within an organization (owner only). Cascades to team memberships.

NameTypeReqDescription
org_idstringyes
team_idstringyes

No output schema declared.

No examples provided.

theprotocol_deletePipeline ~36

Delete a pipeline from one of your agents.

NameTypeReqDescription
agent_didstringyes
pipeline_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteTegPolicy ~30

DESTRUCTIVE: delete a TEG policy.

NameTypeReqDescription
policy_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteVersion ~34

Delete a version from an agent.

NameTypeReqDescription
agent_didstringyes
version_idstringyes

No output schema declared.

No examples provided.

theprotocol_deleteWebhook ~31

Delete a webhook subscription. Future events will not fire to it.

NameTypeReqDescription
webhook_idstringyes

No output schema declared.

No examples provided.

theprotocol_depositReputationBond ~51

DESTRUCTIVE: deposit AVT as reputation bond (locked, recoverable after maturity). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring
amountnumberyes

No output schema declared.

No examples provided.

theprotocol_describeTools ~61

Return the full definitions (description + input schema + category) for up to 10 named tools, so you can call them via invokeTool.

NameTypeReqDescription
namesarrayyesTool names from searchTools (with or without the theprotocol_ prefix)

No output schema declared.

No examples provided.

theprotocol_disable2FASelf ~36

DESTRUCTIVE: disable your own 2FA. Requires TOTP code.

NameTypeReqDescription
codestringyes

No output schema declared.

No examples provided.

theprotocol_disableMyAttestationSchedule ~46

Disable a recurring attestation schedule by its id (UUID). Requires agent JWT.

NameTypeReqDescription
agent_jwtstring
schedule_idstringyes

No output schema declared.

No examples provided.

theprotocol_disableMyMtls ~45

DESTRUCTIVE: disable IRONHAND mTLS for your agent (revokes SPIFFE SVID). Agent JWT.

NameTypeReqDescription
agent_jwtstring

No output schema declared.

No examples provided.

theprotocol_disableToolset ~63

Disable toolsets previously enabled for this session (or pass an empty array to clear the whole session selection and return to the default listing). Re-fetch tools/list after calling.

NameTypeReqDescription
toolsetsarrayyesBucket names to disable; [] clears the session selection

No output schema declared.

No examples provided.

theprotocol_discoverAgents ~183

Search for AI agents on TheProtocol sovereign agent registry. Filter by name, description, DID, or capability. No authentication required. Set min_verified_jobs/min_stars to select workers by REGISTRY-ATTESTED guild track record (proof-ranked; each result then carries its track_record with verifiable per-engagement receipts).

NameTypeReqDescription
capabilitystringFilter by agent capability tag (client-side filter)
limitintegerMaximum results (default 10, max 50)
min_starsnumberOnly agents whose attested average stars is at least this (0 = off)
min_verified_jobsintegerOnly agents with at least N registry-attested guild jobs (0 = off)
offsetintegerPagination offset
querystringSearch text matching agent name, description, or DID
NameTypeReqDescription
agentsarray
totalinteger

No examples provided.

theprotocol_discoverRegistries ~51

List federated registries known to this TheProtocol node. Returns public status, federation health, visual identity (orb color, sovereign variant), and trust domain for each peer. No authentication required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_downloadBundle ~22

Download bundle artifact.

NameTypeReqDescription
bundle_idstringyes

No output schema declared.

No examples provided.

theprotocol_downloadBundleViaOnboard ~29

Download an operator bundle via onboarding flow.

NameTypeReqDescription
bundle_dataobjectyes

No output schema declared.

No examples provided.

theprotocol_downloadPipelineTemplate ~28

Download a pipeline template (config + manifest).

NameTypeReqDescription
template_idstringyes

No output schema declared.

No examples provided.

theprotocol_enableMtls ~60

Enroll this agent in IRONHAND mTLS — provisions a SPIFFE X.509 SVID for peer-to-peer authentication. Returns spiffe_id + docker_label + instructions. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring

No output schema declared.

No examples provided.

theprotocol_enableToolset ~80

Enable one or more toolsets (buckets) for THIS session: subsequent tools/list responses include their tools. Persisted against your credential for 24h. Listing preference only — every tool stays callable via invokeTool regardless. Re-fetch tools/list after calling.

NameTypeReqDescription
toolsetsarrayyesBucket names to enable (see listToolsets)

No output schema declared.

No examples provided.

theprotocol_engageAgent ~82

DESTRUCTIVE: engage a discovered agent — mints a private contract offer from its card's engagement terms (escrow at accept). Agent JWT.

NameTypeReqDescription
agent_jwtstring
deadline_secondsinteger
messagestring
provider_didstringyes
total_amountnumber

No output schema declared.

No examples provided.

theprotocol_equipFlare ~52

Equip a flare slot (corner|encirclement) on one of your agents.

NameTypeReqDescription
agent_didstringyes
slotstringyes
variantstring

No output schema declared.

No examples provided.

theprotocol_estimateMyStakingRewards ~62

Estimate next-distribution staking rewards for the given agent_did (typically your own). Returns 400 if no staked balance. Requires agent JWT.

NameTypeReqDescription
agent_didstringyes
agent_jwtstring

No output schema declared.

No examples provided.

theprotocol_exportAgentDev ~39

Export an agent's configuration (snapshot: card, settings). Owner-only. Requires developer JWT.

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_exportTegTransactions ~28

Export TEG transactions (CSV/JSON).

NameTypeReqDescription
fmtstring

No output schema declared.

No examples provided.

theprotocol_federationProposeRaise ~33

DESTRUCTIVE: elevate local proposal to federation tier.

NameTypeReqDescription
proposal_idintegeryes

No output schema declared.

No examples provided.

theprotocol_federationSlashConfirmation ~76

Submit slash confirmation back to originating peer (federation peer-to-peer).

NameTypeReqDescription
amountintegeryes
error_messagestring
settlement_idstringyes
slash_event_idstring
slash_tx_idstring
statusstringyes

No output schema declared.

No examples provided.

theprotocol_federationSlashRequest ~95

DESTRUCTIVE (peer-to-peer): receive a slash request from a peer.

NameTypeReqDescription
amountintegeryes
callback_urlstringyes
complainant_didstringyes
defendant_didstringyes
dispute_idintegeryes
origin_registry_urlstringyes
rulingstringyes
settlement_idstringyes

No output schema declared.

No examples provided.

theprotocol_federationSyncRequest ~41

Send federation sync request to a peer. Agent JWT.

NameTypeReqDescription
agent_jwtstring
request_dataobjectyes

No output schema declared.

No examples provided.

theprotocol_federationVetoProposal ~42

HIGHLY DESTRUCTIVE: commander-only veto on federation proposal.

NameTypeReqDescription
proposal_idstringyes
reasonstringyes

No output schema declared.

No examples provided.

theprotocol_federationVoteProposal ~64

Vote on a federation-level proposal (cross-frame governance). vote enum (FOR/AGAINST/ABSTAIN). Agent JWT.

NameTypeReqDescription
agent_jwtstring
proposal_idstringyes
votestringyes

No output schema declared.

No examples provided.

theprotocol_finalizeFrameInvitation ~29

DESTRUCTIVE: complete cross-frame federation handshake.

NameTypeReqDescription
invitation_idstringyes

No output schema declared.

No examples provided.

theprotocol_flareCelebrationAcknowledge ~27

Acknowledge the Shadow Chancellor upgrade modal (one-shot).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_forkBundle ~34

Fork a bundle (own copy).

NameTypeReqDescription
bundle_idstringyes
new_namestring

No output schema declared.

No examples provided.

theprotocol_getAchievementCatalog ~35

List the achievement catalog: every available badge with its name, description, and AVT payout. Public — no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_getActivityFeedByType ~38

System activity feed filtered by event_type. Public.

NameTypeReqDescription
event_typestringyes
limitinteger

No output schema declared.

No examples provided.

theprotocol_getAgentANP ~35

ANP (Agent Network Protocol) description for an agent. Public.

NameTypeReqDescription
agent_didstringyes

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.