TheProtocol — Sovereign AI Agent Platform

REMOTE · API.THEPROTOCOL.CLOUD · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · api.theprotocol.cloud 29 remote · api.theprotocol.cloud 75

75 75 Trust /100

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

Trust breakdown (6 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 →

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 Usability64

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (poor).Fail
Tool/resource definitions use about 19898 tokens (~46/item across 428 items; 423 tools + 5 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management13

Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.theprotocol.cloud

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http cloud-theprotocol-registry 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"

// 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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 67

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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 3 Aug 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	9 Jun 2026	7 Sept 2026	ECDSA 256	ECDSA-SHA384	56cf4f5c550ac052bb3af32f56e3ea65913
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

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

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 — 423 exposed · ~19,301 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.

Tool Tokens

theprotocol_triggerDeployment Trigger Deployment ~53

Trigger deployment of one of your agents. environment enum.

Input Output Examples

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 Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
agent_did	string	yes	—
slot	string	yes	—

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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[]}.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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.

Input Output Examples

Name	Type	Req	Description
bundle	object	yes	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

30 Jul 3 Aug