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.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http cloud-theprotocol-registry 'https://api.theprotocol.cloud/mcp'
{
"mcpServers": {
"cloud-theprotocol-registry": {
"url": "https://api.theprotocol.cloud/mcp"
}
}
} {
"servers": {
"cloud-theprotocol-registry": {
"type": "http",
"url": "https://api.theprotocol.cloud/mcp"
}
}
} [mcp_servers.cloud-theprotocol-registry] url = "https://api.theprotocol.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud-theprotocol-registry": {
"type": "remote",
"url": "https://api.theprotocol.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add cloud-theprotocol-registry --url 'https://api.theprotocol.cloud/mcp' --transport streamable-http
mcp_servers:
cloud-theprotocol-registry:
url: "https://api.theprotocol.cloud/mcp" {
"McpServers": {
"cloud-theprotocol-registry": {
"Transport": "http",
"Url": "https://api.theprotocol.cloud/mcp"
}
}
} assistant mcp add cloud-theprotocol-registry -t streamable-http -u 'https://api.theprotocol.cloud/mcp'
{
"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.
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
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 |
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 →
theprotocol_submitSupportTicket Submit Support Ticket ~83
File a support ticket. Categories: bug | question | feature | account | general. Priorities: low | normal | high | urgent. Requires developer JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| message | string | yes | Body of the ticket |
| priority | string | – | – |
| subject | string | yes | Short subject line (1-200 chars) |
No output schema declared.
No examples provided.
theprotocol_submitTegAttestation Submit TEG Attestation ~42
Submit a TEG-side attestation. Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| attestation_data | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_tallyProposal Tally Proposal ~42
Trigger a proposal tally (counts votes, resolves outcome). Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| proposal_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_tegCrossRegistryTransferDirect TEG Cross Registry Transfer Direct ~70
DESTRUCTIVE: cross-registry transfer via TEG-direct. Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| amount | string | yes | – |
| memo | string | – | – |
| receiver_did | string | yes | – |
| target_registry | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_tegReputationSignalToken TEG Reputation Signal Token ~50
Apply reputation signal via /token path. Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| signal_value | integer | yes | – |
| transaction_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_tegStakeDirect TEG Stake Direct ~53
DESTRUCTIVE: stake AVT via TEG-direct path. Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| amount | string | yes | – |
| lock_period_days | integer | – | – |
No output schema declared.
No examples provided.
theprotocol_tegSystemTransfer TEG System Transfer ~56
DESTRUCTIVE: transfer AVT to TEG system pool (tribute/burn flows). Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| amount | string | yes | – |
| purpose | string | – | – |
No output schema declared.
No examples provided.
theprotocol_tegUnstakeDirect TEG Unstake Direct ~53
DESTRUCTIVE: unstake AVT via TEG-direct. Agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
| amount | string | – | – |
| stake_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_testDeveloperWebhookAlt Test Developer Webhook Alt ~29
Send test event to webhook (alt path).
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_testWebhook Test Webhook ~36
Fire a test event to the webhook URL — verifies your receiver is reachable + accepting signatures.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_transferTokens Transfer Tokens ~97
Transfer AVT tokens to another agent on TheProtocol. Requires agent JWT authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | Optional: agent JWT from getAgentToken. |
| amount | string | yes | Amount of AVT to transfer (as numeric string, e.g. '10.5') |
| message | string | – | Optional transfer memo (max 256 chars) |
| recipient_did | string | yes | DID of the receiving agent |
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number|string | – | – |
| fee | number|string | – | – |
| status | string | – | – |
| transaction_id | string|integer | – | – |
No examples provided.
theprotocol_triggerDeployment Trigger Deployment ~53
Trigger deployment of one of your agents. environment enum.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| environment | string | yes | – |
| pipeline_id | string | – | – |
| version_id | string | – | – |
No output schema declared.
No examples provided.
theprotocol_triggerFederationSync Trigger Federation Sync ~20
Trigger an on-demand federation sync cycle.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
theprotocol_triggerManualDistribution Trigger Manual Distribution ~24
DESTRUCTIVE: manually trigger staking reward distribution. Admin only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
theprotocol_unassignAgentFromOrg Unassign Agent From Org ~50
Unassign an agent (by DID) from an organization. Inverse of assignAgentToOrg.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_unequipFlare Unequip Flare ~41
Unequip a single flare slot from one of your agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| slot | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_unlockReputationBond Unlock Reputation Bond ~84
DESTRUCTIVE: at maturity, take back the frame's declared share of your reputation bond (at most 80 percent); the rest stays bonded and you keep providing. Once per bond, and it ends the burning state. A refusal names its reason (not matured, cooldown, already unlocked). Requires agent JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | – |
No output schema declared.
No examples provided.
theprotocol_unstakeTokens Unstake Tokens ~71
Unstake a staking position by its ID and reclaim AVT tokens. Position must belong to your agent and be past its lock period.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | Optional: agent JWT from getAgentToken. |
| stake_id | string | yes | ID of the stake position to unstake |
No output schema declared.
No examples provided.
theprotocol_updateAutoCompound Update Auto Compound ~37
Update auto-compound for one of your agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| enabled | boolean | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateDeploymentStatus Update Deployment Status ~65
Update deployment status (pending/running/success/failed/cancelled).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| deployment_id | string | yes | – |
| error_message | string | – | – |
| metadata | object | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateFederationPeer Update Federation Peer ~36
DESTRUCTIVE: update federation peer registration.
| Name | Type | Req | Description |
|---|---|---|---|
| peer_id | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateMyDeveloperLocation Update My Developer Location ~78
Update authenticated developer's location for globe visualization. location_data MUST include `latitude` and `longitude` (decimal degrees). Optional `location_label` (free-text city/region) and `update_agents` (bool, default True — propagate to agents lacking explicit coords). Requires developer JWT.
| Name | Type | Req | Description |
|---|---|---|---|
| location_data | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateMyDeveloperProfile Update My Developer Profile ~29
DESTRUCTIVE: update developer profile fields.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_updates | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateNotificationPrefs Update Notification Prefs ~45
DESTRUCTIVE: bulk sparse upsert of notification preferences (per type x channel; reset=true reverts a row to catalog default).
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateOrganization Update Organization ~80
Update fields on an organization (name/description/website/logo_url/settings). Pass only the fields you want changed. Owner only.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| logo_url | string | – | – |
| name | string | – | – |
| org_id | string | yes | – |
| settings | object | – | – |
| website | string | – | – |
No output schema declared.
No examples provided.
theprotocol_updateOrganizationTeam Update Organization Team ~68
Update fields on a team (name/description/permissions). Pass only the fields you want changed.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | – | – |
| org_id | string | yes | – |
| permissions | object | – | – |
| team_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_updatePeerSlashConfig Update Peer Slash Config ~36
DESTRUCTIVE: update peer slash configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | – |
| peer_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_updatePipeline Update Pipeline ~58
Update fields on an existing pipeline.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | – |
| is_active | boolean | – | – |
| pipeline_config | object | – | – |
| pipeline_id | string | yes | – |
| pipeline_name | string | – | – |
No output schema declared.
No examples provided.
theprotocol_updateTegPolicy Update TEG Policy ~37
DESTRUCTIVE: update a TEG policy.
| Name | Type | Req | Description |
|---|---|---|---|
| policy_id | string | yes | – |
| updates | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_updateWebhook Update Webhook ~59
Update fields on an existing webhook. Only supplied fields change.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| events | array | – | – |
| is_active | boolean | – | – |
| url | string | – | – |
| webhook_id | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_validateAgentCard Validate Agent Card ~33
Validate an Agent Card against canonical schema. Returns {valid, errors[]}.
| Name | Type | Req | Description |
|---|---|---|---|
| card | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_validateAgentImport Validate Agent Import ~27
Dry-run validate an agent import configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_config | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_verify2FA Verify 2FA ~28
Complete 2FA setup with TOTP code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
theprotocol_verifyPayment Verify Payment ~131
Verify an A2A payment token before doing paid work. Returns validity + amount + caller_did + target_agent_did. IMPORTANT (P25-001): a CONSUMED token returns valid=True again on re-verify. Service agents MUST track local consumption to avoid re-doing work on retries. Requires agent JWT (any agent — token is self-authenticating).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_jwt | string | – | Optional inline agent JWT |
| expected_target_did | string | – | Optional: expected target DID for extra check |
| token | string | yes | The apt_ payment token to verify |
No output schema declared.
No examples provided.
theprotocol_verifyPublicAttestationBundle Verify Public Attestation Bundle ~33
Verify a public attestation bundle (bb verify wrapper). Public.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | object | yes | – |
No output schema declared.
No examples provided.
theprotocol_withdrawOrganizationInvitation Withdraw Organization Invitation ~50
Withdraw a pending organization invitation — frees the address for a re-invite. 409 on an accepted invitation.
| Name | Type | Req | Description |
|---|---|---|---|
| invitation_id | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
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.