Is the Aemb Agent Embassy MCP server down?

mcp-registry/pro.aemb/agent-embassy · v1.0.0

As of 2026-10-21 11:36 UTC, the Aemb Agent Embassy MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 8 minutes.

Agents pay for work and prove what happened.

claude mcp add --transport http aemb-agent-embassy-mcp-server https://aemb.pro/mcp

{
  "mcpServers": {
    "aemb-agent-embassy-mcp-server": {
      "type": "http",
      "url": "https://aemb.pro/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (93/100)

What to fix (3)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fpro.aemb%2Fagent-embassy/fixes

{
  "name": "check_url_custom",
  "description": "Your conditions, one fetch: status, substring, JSON value — signed pass/fail receipt. Default status 200. Public proof: check_url_sealed. Watch: check_url_changes. 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.05, USDC on Base or Arbitrum One. Paid URL: https://aemb.pro/v1/check/ping.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url",
      "idempotency_key"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "HTTPS URL to check (max 2000 chars; no credentials in URL). Fetched once; up to 3 redirects followed, 10s timeout, 1MB body cap"
      },
      "expect_status": {
        "type": "number",
        "description": "Expected HTTP status code; truncated to an integer. Defaults to 200 when omitted"
      },
      "idempotency_key": {
        "type": "string",
        "description": "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 even if you resend different inputs. Published example keys are rejected. Keys are scoped per tool and per payer account: a key never returns another wallet's receipt."
      },
      "expect_json_path": {
        "type": "string",
        "description": "Dot-separated path into the JSON body, e.g. 'data.price' (max 500 chars). Only evaluated when set"
      },
      "expect_json_equals": {
        "description": "Expected value at expect_json_path; compared by canonical JSON equality. Defaults to null when omitted",
        "type": "string"
      },
      "expect_body_contains": {
        "type": "string",
        "description": "Substring that must appear in the response body (max 5000 chars). Skipped when empty or omitted"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": true,
    "destructiveHint": false
  },
  "title": "Check URL — Custom"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/pro.aemb/agent-embassy"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/pro.aemb/agent-embassy"}) over MCP.

Passed

• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.64% uptime over 30 days.

Largest tool definitions

• trust_preflight ~620 tokens
• agentid_issue ~581 tokens
• agentid_renew ~499 tokens
• correct_copy ~488 tokens
• check_url_custom ~486 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.aemb%2Fagent-embassy.svg)](https://glimind.com/server/mcp-registry%2Fpro.aemb%2Fagent-embassy?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fpro.aemb%2Fagent-embassy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.aemb%2Fagent-embassy.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fpro.aemb%2Fagent-embassy.svg
   :target: https://glimind.com/server/mcp-registry%2Fpro.aemb%2Fagent-embassy?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3a50af3339c677f1…, first seen 2026-10-18, included at leaf 23063 of 39,292. Version history · verify what your client received.

Tools (25)

• agentid_issue
• agentid_renew
• agentid_revoke
• agentid_verify
• attest_document
• attest_work
• check_url_changes
• check_url_custom
• check_url_sealed
• compute_alerts
• compute_history
• compute_spot_prices
• compute_spot_sealed
• correct_copy
• diligence_pack
• farcaster_kit
• give
• nostr_kit
• rank_the_rankers
• register_recovery
• research_paper
• ticker_shelf
• trust_assurance
• trust_preflight
• trust_report

Compare: most reliable security servers · most reliable other servers · most reliable web servers · most reliable data servers · most reliable payments servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Aemb Agent Embassy MCP server down right now?

As of 2026-10-21 11:36 UTC, the Aemb Agent Embassy MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Aemb Agent Embassy MCP server provide?

Aemb Agent Embassy MCP server advertises 25 tools, including agentid_issue, agentid_renew, agentid_revoke, agentid_verify, attest_document.

How do I install Aemb Agent Embassy MCP server?

Point your MCP client at this streamable-http endpoint: https://aemb.pro/mcp

Is the Aemb Agent Embassy MCP server safe to connect to an AI agent?

Glimind scanned all 25 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Aemb Agent Embassy MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.