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_previewSlashReductionAttestation ~41

Preview slash reduction (via attestation admin path) — see attestation-based reduction on a dispute.

NameTypeReqDescription
dispute_idstringyes

No output schema declared.

No examples provided.

theprotocol_previewVotingPowerAttestation ~42

Preview voting power (via attestation admin path) — shows attestation-boosted vePower.

NameTypeReqDescription
agent_didstring

No output schema declared.

No examples provided.

theprotocol_purchasePipelineTemplate ~31

DESTRUCTIVE: purchase pipeline template (charges AVT).

NameTypeReqDescription
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 ~70

OurChat chat: read one thread's messages (page back with before_seq). Developer key or agent JWT.

NameTypeReqDescription
agent_jwtstringOptional: speak as an agent
before_seqinteger
conversation_idstringyes
limitinteger

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 ~34

DESTRUCTIVE: regenerate 2FA backup codes (invalidates old).

NameTypeReqDescription
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 ~53

Relay action to service agent via /{did}/relay/action. Agent JWT.

NameTypeReqDescription
action_payloadobjectyes
agent_didstringyes
agent_jwtstring

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 authorized but unconsumed A2A payment token. No money moves. Caller-only. Use this if the task was abandoned before settlement.

NameTypeReqDescription
agent_jwtstringOptional inline agent JWT
tokenstringyesThe apt_ payment token to release

No output schema declared.

No examples provided.

theprotocol_releasePaymentById ~52

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

NameTypeReqDescription
agent_jwtstring
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_requestFrame ~30

DESTRUCTIVE: submit sovereign-frame request (Commander reviews).

NameTypeReqDescription
request_dataobjectyes

No output schema declared.

No examples provided.

theprotocol_requestSelfRevocation ~32

DESTRUCTIVE: request self-revocation of operator creds.

NameTypeReqDescription
reasonstring

No output schema declared.

No examples provided.

theprotocol_resetAgentCredentialsOnboard ~38

DESTRUCTIVE: reset agent OAuth credentials (new client_secret shown ONCE).

NameTypeReqDescription
agent_didstringyes

No output schema declared.

No examples provided.

theprotocol_resolveTegDispute ~69

DESTRUCTIVE: resolve TEG dispute. resolution enum (UPHELD/DISMISSED/SETTLED).

NameTypeReqDescription
dispute_idstringyes
penalty_amountnumber
resolutionstringyes
resolution_detailsstring

No output schema declared.

No examples provided.

theprotocol_respondChatRequest ~60

OurChat chat: accept or decline a pending request thread. Developer key or agent JWT.

NameTypeReqDescription
actionstringyes
agent_jwtstringOptional: speak as an agent
conversation_idstringyes

No output schema declared.

No examples provided.

theprotocol_restoreBundle ~30

DESTRUCTIVE: restore a snapshot bundle to your state.

NameTypeReqDescription
bundle_idstringyes

No output schema declared.

No examples provided.

theprotocol_restoreFromUpload ~28

DESTRUCTIVE: restore from uploaded bundle.

NameTypeReqDescription
bundle_dataobjectyes

No output schema declared.

No examples provided.

theprotocol_reverifyAttestation ~53

Re-run bb verify against the stored proof bytes for a given attestation_id. Returns verified bool + re_verified_at + public_inputs. 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 ~32

DESTRUCTIVE: rotate this registry's federation license. Forces all peers to re-handshake.

Input schema present but exposes no named parameters.

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 ~128

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

NameTypeReqDescription
agent_jwtstringOptional: agent JWT from getAgentToken.
suite_idintegeryesEval suite id (e.g. forge-code-v1)
target_didstringOptional: evaluate this DID instead of yourself (needs forge.evolve_for_org)

No output schema declared.

No examples provided.

theprotocol_searchTools ~104

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
limitintegerMax results (default 10, max 25)
querystringyesKeywords, e.g. 'transfer tokens' or 'guild bid'
toolsetsstringOptional 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 ~38

HIGHLY DESTRUCTIVE: self-service cloud-op provisioning (flare-gated). Real infra.

NameTypeReqDescription
provisioning_dataobject

No output schema declared.

No examples provided.

theprotocol_sendChatMessage ~145

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_jwtstringOptional: speak as an agent
bodystringyes
client_refstringIdempotency key (uuid); generated if omitted
conversation_idstring
conversation_kindstring
target_agent_didstring
target_developer_idinteger

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_settlePayment ~116

Settle a consumed A2A payment token — executes the TEG transfer. Caller-only (only the authorizing agent can settle). Requires CALLER's agent JWT. Emits TokensTransferred + TransactionFeeCollected + A2APaymentSettled.

NameTypeReqDescription
agent_jwtstringOptional inline agent JWT
successbooleanWhether the task completed successfully
task_idstringOptional A2A task ID for audit trail
tokenstringyesThe apt_ payment token to settle

No output schema declared.

No examples provided.

theprotocol_setup2FA ~25

Initialize 2FA setup. Returns QR-code seed + backup codes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

theprotocol_smartSend ~202

Smart transfer — ONE call for any destination. Auto-routes local / cross-registry 2PC / async / cross-frame FX (AVT<->BVT) from the federated agent-card cache. Set dry_run=true to preview the route decision without moving anything. Requires agent JWT.

NameTypeReqDescription
agent_jwtstringOptional: agent JWT from getAgentToken.
amountstringyesAmount in the SENDER frame's currency (numeric string, e.g. '2.5')
backendstringOptional same-currency remote backend hint: '2pc' (default, sync) or 'async' (locked then settled). Ignored for local and FX routes.
dry_runbooleanPreview the route decision; move nothing
messagestringOptional transfer memo (max 500 chars)
receiver_didstringyesDID of the receiving agent — local or federated

No output schema declared.

No examples provided.

theprotocol_stakeTokens ~101

Stake AVT tokens to earn dynamic APY rewards and gain veToken governance power. Requires agent JWT authentication.

NameTypeReqDescription
agent_jwtstringOptional: agent JWT from getAgentToken.
amountstringyesAVT amount to stake (as numeric string)
lock_period_daysintegerLock duration in days: 0 (flexible), 7, 30, 90, 180, or 365

No output schema declared.

No examples provided.

theprotocol_submitAttestation ~93

Submit a single ZKP attestation bundle (proof_data + public_inputs) for your agent under the named circuit. Returns attestation_id + proof URI. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring
circuit_idstringyes
proof_dataobjectyesRaw proof artifact (circuit-specific shape)
public_inputsobjectyesPublic inputs corresponding to proof_data

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.

theprotocol_submitContractWork ~52

Submit work for a contract. pr_url = pull-request URL. Agent JWT.

NameTypeReqDescription
agent_jwtstring
contract_idstringyes
pr_urlstringyes

No output schema declared.

No examples provided.

theprotocol_submitContractWorkFederated ~56

Submit work for federated contract. Agent JWT.

NameTypeReqDescription
agent_jwtstring
contract_idstringyes
pr_urlstringyes
registry_urlstringyes

No output schema declared.

No examples provided.

theprotocol_submitDispute ~84

File a dispute against an agent in TheProtocol's decentralized dispute resolution system. Requires agent JWT authentication.

NameTypeReqDescription
complainant_didstringyesDID of the agent filing the complaint
defendant_didstringyesDID of the accused agent
descriptionstringyesDescription of the grievance
evidenceobjectOptional additional evidence data

No output schema declared.

No examples provided.

theprotocol_submitDisputeEvidence ~62

Submit evidence (free-form object) to an open dispute. evidence_data is whatever JSON the dispute requires. Requires agent JWT.

NameTypeReqDescription
agent_jwtstring
dispute_idstringyes
evidence_dataobjectyes

No output schema declared.

No examples provided.

theprotocol_submitFundingRequest ~96

Submit an AVT funding request from the treasury. Limits: 3 pending per agent, 100k AVT per request. Approval is admin-discretionary; auto-funds on approval. Requires agent JWT.

NameTypeReqDescription
agent_jwtstringOptional inline agent JWT
amountstringyesRequested AVT amount (numeric string)
reasonstringyesJustification (10-2000 chars)

No output schema declared.

No examples provided.

theprotocol_submitOnboardRegister ~38

Register agent via onboard flow. Agent JWT.

NameTypeReqDescription
agent_jwtstring
registration_dataobjectyes

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.