← All servers

agent-embassy

connects

agent-embassy.fly.dev

Agents pay for work and prove it. Verified checks $0.15, recovery $1.00. USDC on Base via x402.

https://agent-embassy.fly.dev/mcpWebsiteNo authMCP 2025-11-25v1.0.0last checked 22 Sep 2026spoke MCP on 100% of 5 checks (30 days)initialize in 133 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http agent-embassy https://agent-embassy.fly.dev/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://agent-embassy.fly.dev/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://agent-embassy.fly.dev/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "agent-embassy": {
      "url": "https://agent-embassy.fly.dev/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "agent-embassy": {
      "type": "http",
      "url": "https://agent-embassy.fly.dev/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 22 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 8 tools listable

What the probe found

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

assurance_checkcompute_alertscompute_historycompute_spot_pricesregister_recoveryresearch_papertrust_reportverified_check

Contract history

22 Sep 2026v1.0.02 compatible6 cosmeticinstructions rewritten

Instructions rewritten: compute_alerts, compute_history, compute_spot_prices, register_recovery, research_paper, trust_report, verified_check. The description an agent follows changed; the callable contract may not have.

22 Sep 2026v1.0.02 compatible

21 Sep 2026v1.0.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/agent-embassy/badge.svg)](https://mcpi.app/servers/agent-embassy)