pro.aemb/agent-embassy
REMOTE · AEMB.PRO · SCANNED SEP 26
Agents pay for work and prove what happened.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5138 tokens (~321/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 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 pro.aemb/agent-embassy MCP server?
pro.aemb/agent-embassy is a hosted endpoint at https://aemb.pro/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 · aemb.pro
claude mcp add --transport http pro-aemb-agent-embassy 'https://aemb.pro/mcp'
{
"mcpServers": {
"pro-aemb-agent-embassy": {
"url": "https://aemb.pro/mcp"
}
}
} {
"servers": {
"pro-aemb-agent-embassy": {
"type": "http",
"url": "https://aemb.pro/mcp"
}
}
} [mcp_servers.pro-aemb-agent-embassy] url = "https://aemb.pro/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pro-aemb-agent-embassy": {
"type": "remote",
"url": "https://aemb.pro/mcp",
"enabled": true
}
}
} openclaw mcp add pro-aemb-agent-embassy --url 'https://aemb.pro/mcp' --transport streamable-http
mcp_servers:
pro-aemb-agent-embassy:
url: "https://aemb.pro/mcp" {
"McpServers": {
"pro-aemb-agent-embassy": {
"Transport": "http",
"Url": "https://aemb.pro/mcp"
}
}
} assistant mcp add pro-aemb-agent-embassy -t streamable-http -u 'https://aemb.pro/mcp'
{
"mcpServers": {
"pro-aemb-agent-embassy": {
"type": "http",
"url": "https://aemb.pro/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.
- 26 Sept 26 +6
- HTTPS: unverified → pass ▲ security
- Tool “prove_it” rewrote its description, which is the text the model reads security
- “research_paper” added an optional parameter “prior_receipt_id” cosmetic
- “agentid_issue” reworded the description of “idempotency_key” cosmetic
- “agentid_renew” reworded the description of “idempotency_key” cosmetic
- “agentid_revoke” reworded the description of “idempotency_key” cosmetic
- “agentid_verify” reworded the description of “idempotency_key” cosmetic
- “assurance_check” reworded the description of “idempotency_key” cosmetic
- “compute_alerts” reworded the description of “idempotency_key” cosmetic
- “compute_history” reworded the description of “idempotency_key” cosmetic
- “correct_copy” reworded the description of “idempotency_key” cosmetic
- “preflight_check” reworded the description of “idempotency_key” cosmetic
- “prove_it” reworded the description of “idempotency_key” cosmetic
- “proveit_verified_check” reworded the description of “idempotency_key” cosmetic
- “register_recovery” reworded the description of “idempotency_key” cosmetic
- “research_paper” reworded the description of “idempotency_key” cosmetic
- “trust_report” reworded the description of “idempotency_key” cosmetic
- “verified_check” reworded the description of “idempotency_key” cosmetic
- “agentid_issue” dropped the optional parameter “agent_wallet” cosmetic
- “agentid_renew” dropped the optional parameter “agent_wallet” cosmetic
- “agentid_revoke” dropped the optional parameter “agent_wallet” cosmetic
- “agentid_verify” dropped the optional parameter “agent_wallet” cosmetic
- “compute_alerts” dropped the optional parameter “agent_wallet” cosmetic
- “compute_history” dropped the optional parameter “agent_wallet” cosmetic
- “correct_copy” dropped the optional parameter “agent_wallet” cosmetic
- “preflight_check” dropped the optional parameter “agent_wallet” cosmetic
- “proveit_verified_check” dropped the optional parameter “agent_wallet” cosmetic
- “register_recovery” dropped the optional parameter “agent_wallet” cosmetic
- “research_paper” dropped the optional parameter “agent_wallet” cosmetic
- “trust_report” dropped the optional parameter “agent_wallet” cosmetic
- “verified_check” dropped the optional parameter “agent_wallet” cosmetic
- 25 Sept 26 +5
- Schema quality: 122 → 351 ▼ functional
- Tool coverage: 15% → 100% ▲ functional
- Schema quality: poor → excellent functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +2
- Tool “agentid_issue” rewrote its description, which is the text the model reads security
- Tool “agentid_renew” rewrote its description, which is the text the model reads security
- Tool “agentid_revoke” rewrote its description, which is the text the model reads security
- Tool “agentid_verify” rewrote its description, which is the text the model reads security
- Tool “assurance_check” rewrote its description, which is the text the model reads security
- Tool “compute_alerts” rewrote its description, which is the text the model reads security
- Tool “compute_history” rewrote its description, which is the text the model reads security
- Tool “compute_spot_prices” rewrote its description, which is the text the model reads security
- Tool “correct_copy” rewrote its description, which is the text the model reads security
- Tool “prove_it” rewrote its description, which is the text the model reads security
- Tool “register_recovery” rewrote its description, which is the text the model reads security
- Tool “trust_report” rewrote its description, which is the text the model reads security
- Tool “verified_check” rewrote its description, which is the text the model reads security
- Tool “research_paper” rewrote its description, which is the text the model reads security
- Schema quality: 1589 → 1752 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “correct_copy” functional
- 23 Sept 26 58
First indexed and scored.
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 26 Sept 2026 · Probed https://aemb.pro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aemb.pro | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5e9a78166e0a933abf2d5919f4aa3896ddf |
| SANs: aemb.pro | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 aemb.pro. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| pro. | present | 42154 | 8 | Verified |
| aemb.pro. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aemb.pro/mcp | Verified | 200 | |
| http (plaintext) | http://aemb.pro/mcp | HTTPS enforced | 301 | https://aemb.pro/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 →
agentid_issue Agent ID — Issue ~400
Use agentid_issue when you want to issue an Agent ID: a signed identity attestation binding an agent's public key to a verified accountable principal, with operator details and an expiry. Issuance is refused when the principal cannot be verified — that refusal is what makes the ID worth anything. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/issue.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key_scheme | string | – | Key scheme for agent_pubkey: eip191 or ed25519 (default eip191) |
| agent_pubkey | string | yes | The agent's public key (hex), the root of the Agent ID |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| operator_contact | string | yes | Public contact for the operator (max 320 chars) |
| operator_name | string | yes | Public name of the operator running the agent (max 200 chars) |
| principal_attestation_method | string | yes | How the Embassy verified the principal |
| principal_id | string | yes | ID of the accountable principal on file with the Embassy |
| principal_kind | string | yes | Kind of principal: human or legal_entity |
| principal_label | string | yes | Public label for the principal |
| validity_days | number | – | Days until the Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
agentid_renew Agent ID — Renew ~443
Use agentid_renew to renew an Agent ID: a fresh Agent ID, same identity chain, new expiry; old one retired. revocation_signature over agent-id-revoke:<OLD_agent_id> (64-char lowercase ID) — same contract as retiring: EIP-191 personal_sign (envelope required; raw ECDSA fails), 0x 65-byte hex; or ed25519 nacl.sign.detached, 64-byte hex. Signer: principal or Embassy-for-cause. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/renew.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected |
| idempotency_key | string | – | Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when om… |
| revocation_signature | string | yes | Hex signature over the exact UTF-8 message agent-id-revoke:<OLD_agent_id> (64-char lowercase ID, no trailing newline) — the signature covers the OLD Agent ID being retired. EIP-191: personal_sign the… |
| validity_days | number | – | Days until the renewed Agent ID expires; integer 1-730. Defaults to the Embassy standard when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
agentid_revoke Agent ID — Revoke ~419
Use agentid_revoke to retire an Agent ID instantly. revocation_signature: hex signature over the message agent-id-revoke:<agent_id> (64-char lowercase ID). EIP-191: personal_sign the message string (envelope required; raw ECDSA fails), 0x 65-byte hex, matched to the principal's revocation key. ed25519: nacl.sign.detached, 64-byte hex. Signer: principal or Embassy-for-cause. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/revoke.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The Agent ID string returned at issuance (64 hex characters; case-insensitive). Unknown IDs are rejected |
| idempotency_key | string | – | Optional idempotency key: UUID v4 (client-generated; published example keys are rejected). When provided, replaying the same key returns the original receipt instead of re-running the action; when om… |
| reason | string | yes | Why the Agent ID is being retired (required, max 500 characters) |
| revocation_signature | string | yes | Hex signature over the exact UTF-8 message agent-id-revoke:<agent_id> (64-char lowercase ID, no trailing newline). EIP-191: personal_sign the message STRING (personal_sign envelope REQUIRED — raw ECD… |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
agentid_verify Agent ID — Verify ~264
Use agentid_verify when you want to check an Agent ID's current standing: valid, revoked, expired, or unknown. Every status returns the identical response shape — the Agent ID, expiry, the full identity chain, an inclusion record, and the signed attestation envelope. Unknown IDs report unknown; never an error. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/agent-id/verify.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The Agent ID string returned at issuance (64 hex characters; case-insensitive). Rate-limited: 30 checks/min per client IP, 429 on exhaustion |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
assurance_check Assurance Check ~383
Use assurance_check when you need a go/no-go verdict BEFORE an agent acts on a provider: the Embassy probes the provider unpaid (no payment header, zero spend) and returns a signed ALLOW, ALLOW_WITH_RESTRICTIONS, ASK_HUMAN, REVERIFY, REROUTE, or QUARANTINE decision. UNVERIFIED is the honest default for unknowns — never a smear, never a badge. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/assurance/check.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The action the agent intends to take, e.g. 'transfer' (required, max 200 chars) |
| amount_usdc | string | yes | Amount at stake, as a positive decimal string, e.g. '0.25' |
| context | string | – | Optional free-text context for the assessment (truncated to 2000 chars) |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| permissions_requested | array | yes | Permissions the action needs, e.g. ['spend']. Non-empty array, max 50 entries; each entry truncated to 200 chars |
| provider_endpoint | string | yes | HTTPS URL of the provider to assess (max 2000 chars; no credentials in URL) |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
compute_alerts Compute Alerts ~247
Use compute_alerts when you want to know when GPU spot prices made a significant move: returns the current price-move alert list, sealed into your signed receipt. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/markets/compute/alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for all GPUs |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| limit | number | – | Max alerts to return; integer 1-50. Defaults to 25 |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
compute_history Compute History ~266
Use compute_history when you need GPU compute market history: a bounded time series of per-GPU cheapest/median/offer counts — or whole-market history when no GPU is named — sealed into your signed receipt. Prices are ephemeral asks, never delivered-cost guarantees. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/markets/compute/history.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | Optional GPU filter, e.g. 'H100 SXM' (max 64 chars). Omit for whole-market history |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| limit | number | – | Max history points to return; integer 1-200. Defaults to 50 |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
compute_spot_prices Compute Spot Prices ~231
Use compute_spot_prices when you need the live GPU spot market snapshot: current per-GPU-hour prices with filters for GPU model, offer type, verified hosts, minimum host reliability, GPU count, and result size. GET the paid_url with an x402 v2 PAYMENT-SIGNATURE header carrying the USDC authorization. Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/markets/compute/spot.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | Optional GPU model filter, e.g. 'H100 SXM' |
| max_results | integer | – | Max offers to return; integer 1-25 |
| min_gpus | integer | – | Minimum GPU count per offer; integer >= 1 |
| min_reliability | number | – | Minimum host reliability 0..1 (inclusive); hosts below it are excluded |
| type | string | – | Offer type filter: ondemand, bid, or reserved |
| verified | boolean | – | When true, only verified hosts; when false, only unverified hosts |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: GET the paid_url with an x402 v2 PAYMENT-SIGNATURE header carrying the USDC authorization |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to GET (with query params) for the market snapshot |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.25" |
| tool | string | yes | Tool name: compute_spot_prices |
No examples provided.
correct_copy Correct Copy ~332
Use correct_copy when you want a $25 correction pass over draft copy: normalizes formatting, verifies every link is alive, confirms your required terms appear, and scans for black-box leaks — then returns the corrected copy with a verification report and a signed receipt. You pay for the pass, never the method. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $25.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/copy/correct.
| Name | Type | Req | Description |
|---|---|---|---|
| draft | string | yes | The raw draft copy to correct (1-20000 chars) |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| links | array | – | HTTPS URLs the copy references; each is verified alive via HEAD (fallback GET), 8s timeout, redirects never followed (max 20) |
| register | string | yes | Voice register: founder-notes, elite, force, or bright-soft-junior |
| required_terms | array | – | Terms that must appear in the final copy (max 20; each term max 100 chars; counted case-insensitively) |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
preflight_check Preflight Check ~331
Use preflight_check before your agent spends on a paid tool or endpoint: the Embassy answers WHO is paid, WHAT is delivered, what CHANGED, the full COST, and WHO TAKES A CUT — then returns a signed PROCEED, PROCEED_WITH_CAUTION, BLOCKED, or UNKNOWN verdict with the full evidence envelope. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/preflight/check.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | principal_wallet + chain. Optional. |
| dry_run | boolean | – | true = free dry-run, intercepted before the payment gate |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| intent | object | yes | The intended invocation: operation (required), params_summary (sha256 of canonical params), advertised_cost_usdc |
| policy | array | – | Policy strings (max 20) |
| subject | object | yes | The spend target: server_id (required), artifact (mcpb:// | oci:// | https://), claimed_version |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
prove_it Prove-It — Verified Proof Receipts for Superintelligence (x402) ~248
Use prove_it when you want signed cryptographic proof that a URL is live and serving expected content: one automated fetch at request time, sealed into a signed Outcome Receipt with the full check transcript. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/check/prove.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| url | string | yes | HTTPS URL to prove live (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap. Default expectation: HTTP 200 |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
proveit_verified_check Prove-It Verified Check ~276
Use proveit_verified_check when you need a signed receipt that a compute-price check actually ran: one live GPU spot market snapshot (13 classes, cheapest rentable ask per class in USD/hour; one class when gpu is named), sealed into a signed Outcome Receipt. $0.25 per check. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/check/proveit-verified.
| Name | Type | Req | Description |
|---|---|---|---|
| gpu | string | – | Optional GPU class, e.g. 'H100 SXM' (max 64 chars). Omit for all 13 classes |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| type | string | – | Offer type: ondemand, bid, or reserved. Defaults to ondemand |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
register_recovery Register Recovery ~315
Use register_recovery when you want to escrow a client-encrypted recovery blob with the Embassy: it is stored opaquely (the Embassy cannot decrypt it), queued for human operator review within 24h, and you get a signed receipt proving the stored blob's hash. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $1.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/recovery/register.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_handle | string | – | Optional contact (email or handle) for the operator review |
| contact_name | string | yes | Your name or operator handle, recorded with the escrow |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| quorum_rules | string | yes | The release rules for this blob, e.g. '2-of-3 named trustees must approve release' |
| recovery_blob | string | yes | Client-encrypted blob (ENC:v1:base64...). Stored opaquely; only its SHA-256 and byte count enter the signed receipt |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
research_paper Research Paper ~350
Use research_paper when you want to buy a research paper: $222 for the paper, or $444 for paper+provenance (the paper plus the corpus evidence pack). Licensed to your wallet — the purchased bytes are delivered privately with a signed receipt. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $222.00, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/research/paper.
| Name | Type | Req | Description |
|---|---|---|---|
| bundle | string | – | Delivery tier: 'paper' ($222) or 'paper+provenance' ($444, paper plus the corpus evidence pack). Defaults to 'paper' |
| buyer_alias | string | – | Optional license display name (3-32 chars: letters, digits, . _ -). Defaults to the first 8 hex chars of the buyer wallet |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| paper_id | string | yes | Catalog ID of the paper, e.g. 'the-discontinuity-20260922'. Unknown IDs are rejected |
| prior_receipt_id | string | – | Optional prior research_paper receipt id for receipt-carried tier pricing on the paper+provenance bundle |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
trust_report Trust Report ~263
Use trust_report when you need a buy/don't-buy decision on a candidate x402 endpoint: the Embassy probes it unpaid (no payment header, zero spend) and returns a signed PROCEED, VERIFY_FIRST, or DO_NOT_PAY verdict — a decision, never a score. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.25, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/trust/report.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| url | string | yes | HTTPS URL of the candidate x402 endpoint to probe (max 2000 chars; no credentials in URL). Probed unpaid via GET, falling back to an empty-body POST when GET returns 404/405 |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
verified_check Verified Check ~370
Use verified_check when you need a pass/fail verdict that a URL serves expected content: expected HTTP status (default 200), a required body substring, and/or an exact match on one JSON field. One automated fetch at request time, signed receipt with per-condition results. POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header. See https://docs.cdp.coinbase.com/x402 Paid tool — $0.15, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/check/verify.
| Name | Type | Req | Description |
|---|---|---|---|
| expect_body_contains | string | – | Substring that must appear in the response body (max 5000 chars). Skipped when empty or omitted |
| expect_json_equals | – | – | Expected value at expect_json_path; compared by canonical JSON equality. Defaults to null when omitted |
| expect_json_path | string | – | Dot-separated path into the JSON body, e.g. 'data.price' (max 500 chars). Only evaluated when set |
| expect_status | number | – | Expected HTTP status code; truncated to an integer. Defaults to 200 when omitted |
| idempotency_key | string | yes | Idempotency key: UUID v4, client-generated, one per logical request. Replaying the same key on this tool returns the original receipt — the action is not re-run, and the first request's receipt wins… |
| url | string | yes | HTTPS URL to check (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Settlement asset |
| facilitator | string | yes | x402 facilitator |
| how | string | yes | How to pay: POST the tool inputs as JSON to paid_url with an x402 v2 PAYMENT-SIGNATURE header |
| networks | array | yes | EVM CAIP-2 network ids accepted |
| paid_url | string | yes | x402-paid HTTPS URL to POST the tool inputs to |
| payment_required | boolean | yes | Always true: this MCP tool is a payment pointer; the tool itself is monetized via x402. |
| price | string | yes | Exact price, e.g. "$0.15" |
| tool | string | yes | Tool name, e.g. verified_check |
No examples provided.
What is the pro.aemb/agent-embassy MCP server?
pro.aemb/agent-embassy is an MCP server listed in the public MCP registry as pro.aemb/agent-embassy. Agents pay for work and prove what happened. This page covers its hosted endpoint (https://aemb.pro/mcp).
Is the pro.aemb/agent-embassy MCP server safe to use?
pro.aemb/agent-embassy scores 71 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 pro.aemb/agent-embassy MCP server expose?
pro.aemb/agent-embassy exposes 16 tools: register_recovery, verified_check, prove_it, proveit_verified_check, trust_report, and 11 more. Their descriptions and schemas cost roughly 5,138 tokens of context every time the server is loaded.
Does the pro.aemb/agent-embassy MCP server require authentication?
No. We connected to pro.aemb/agent-embassy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pro.aemb/agent-embassy MCP server still maintained?
pro.aemb/agent-embassy is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.