Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

EchoRelay

REMOTE · MCP.ECHORELAY.DEV · SCANNED SEP 20

A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.

0 this week 92 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security91
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 9617 tokens (~120/item across 80 items; 80 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 80 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
Install

How do I install the EchoRelay MCP server?

EchoRelay is a hosted endpoint at https://mcp.echorelay.dev/, 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 · mcp.echorelay.dev

# add to Claude Code
claude mcp add --transport http dev-echorelay-management 'https://mcp.echorelay.dev/'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-echorelay-management": {
      "url": "https://mcp.echorelay.dev/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-echorelay-management": {
      "type": "http",
      "url": "https://mcp.echorelay.dev/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-echorelay-management]
url = "https://mcp.echorelay.dev/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-echorelay-management": {
      "type": "remote",
      "url": "https://mcp.echorelay.dev/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-echorelay-management --url 'https://mcp.echorelay.dev/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-echorelay-management:
    url: "https://mcp.echorelay.dev/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-echorelay-management": {
      "Transport": "http",
      "Url": "https://mcp.echorelay.dev/"
    }
  }
}
# add to Vellum
assistant mcp add dev-echorelay-management -t streamable-http -u 'https://mcp.echorelay.dev/'
// mcp.json
{
  "mcpServers": {
    "dev-echorelay-management": {
      "type": "http",
      "url": "https://mcp.echorelay.dev/"
    }
  }
}

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.

  • 20 Sept 26 −2
    • Authorization: pass → fail security
    • New tool “set_overage_billing”, which the server declares destructive security
    • Tool “get_billing” rewrote its description, which is the text the model reads security
    • Tool “subscribe_addon” rewrote its description, which is the text the model reads security
    • Server version: 1.14.0 → 1.15.0 functional
  • 17 Sept 26 0
    • Tool “list_dlq” rewrote its description, which is the text the model reads security
  • 16 Sept 26 +2
    • Authorization: fail → pass security
    • First check of Authorization: partial security
    • Tool “archive_project” rewrote its description, which is the text the model reads security
    • Tool “create_project” rewrote its description, which is the text the model reads security
    • Tool “create_project_token” rewrote its description, which is the text the model reads security
    • Tool “list_dlq” rewrote its description, which is the text the model reads security
    • Tool “list_project_tokens” rewrote its description, which is the text the model reads security
    • Tool “list_projects” rewrote its description, which is the text the model reads security
    • Tool “protect_project” rewrote its description, which is the text the model reads security
    • Tool “rename_project” rewrote its description, which is the text the model reads security
    • Tool “revoke_project_token” rewrote its description, which is the text the model reads security
    • Tool “unarchive_project” rewrote its description, which is the text the model reads security
    • “create_project_token” reworded the description of “expiresInDays” cosmetic
    • “create_project_token” reworded the description of “label” cosmetic
    • “create_project_token” reworded the description of “scopes” cosmetic
    • “revoke_project_token” reworded the description of “tokenId” cosmetic
  • 13 Sept 26 0
    • Tool “rollback_config” rewrote its description, which is the text the model reads security
    • “rollback_config” added an optional parameter “confirmUnsigned” cosmetic
  • 12 Sept 26 0
    • Tool “rollback_config” rewrote its description, which is the text the model reads security
    • “rollback_config” added an optional parameter “confirmRevision” cosmetic
  • 4 Sept 26 0
    • Tool “get_dlq_entry” rewrote its description, which is the text the model reads security
    • Tool “get_request” rewrote its description, which is the text the model reads security
    • Tool “list_dlq” rewrote its description, which is the text the model reads security
    • Tool “rename_project” rewrote its description, which is the text the model reads security
    • “discard_dlq_entry” reworded the description of “id” cosmetic
    • “get_dlq_entry” reworded the description of “id” cosmetic
    • “retry_dlq_entry” reworded the description of “id” cosmetic
  • 28 Aug 26 +11
    • Judged manipulation: unverified → pass security
    • Schema quality: unverified → excellent functional
  • 27 Aug 26 −11
    • Judged manipulation: pass → unverified security
    • Schema quality: excellent → unverified functional
    • Server version: 1.13.0 → 1.14.0 functional
    • New tool “generate_line_draft” functional
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 20 Sept 2026 · Probed https://mcp.echorelay.dev

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=echorelay.dev CN=YE2,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 56dd766f8ce63c6ae931fe7a8a27c888dd0
SANs: *.echorelay.dev, echorelay.dev
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 secure

Validation of mcp.echorelay.dev. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
echorelay.dev. present 2371 13 Verified
mcp.echorelay.dev. Verified address RRset verified with the apex keys
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.echorelay.dev/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://mcp.echorelay.dev/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy script-src 'self' 'nonce-031a58b960f5bcedf3722b2638e44471' 'sha256-4FqAsKYYgAp9u0EQQ/5kYTh/MCiR+GodCLMScWjsIPc=' https://cdn.paddle.com; report-uri /csp-report; report-to csp-endpoint
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Protected resource metadata

Document https://mcp.echorelay.dev/.well-known/oauth-protected-resource
Retrieved No
Problem metadata_unreachable

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.echorelay.dev Verified 200
http (plaintext) http://mcp.echorelay.dev HTTPS enforced 301 https://mcp.echorelay.dev/
MCP tools · 80 exposed · ~9,617 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. 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 →

Tool Tokens
list_subscription_plans ~47

List the available subscription plans (Free, Pro, Scale) with monthly EUR price, credit allowance, per-project RPM cap, and how many active projects the plan includes. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

preview_line_draft ~36

Preview one line draft without publishing it.

NameTypeReqDescription
lineKeystringyesThe line key, e.g. "v1".

No output schema declared.

No examples provided.

preview_plan_change ~89

Preview what would happen if change_plan were called with this plan: the immediate-charge amount (cents), the next-invoice amount, the effective date, and the kind (`applied` for in-cycle upgrade, `scheduled` for at-period-end downgrade / cancel). Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
planstringyesTarget plan to preview a switch to.

No output schema declared.

No examples provided.

protect_project ~94

Turn on archive protection for a project you own: archive_project (on every surface: panel, REST, and this tool) then refuses until it is lifted. Idempotent. Permanent from here: there is no tool or API call to turn it back off; only contacting support can. Requires an ACCOUNT-scoped management token and the `config` scope.

NameTypeReqDescription
slugstringyesThe slug of a project you own.

No output schema declared.

No examples provided.

publish_line_draft ~37

Publish one line draft now and clear only its schedule.

NameTypeReqDescription
draftRevisionintegeryes
lineKeystringyes

No output schema declared.

No examples provided.

remove_member ~64

Remove a member (accepted or pending) from this project by their member ID or email. Owner only.

NameTypeReqDescription
emailstringEmail address (alternative to memberId — removes the first matching member).
memberIdstringMember record UUID (from list_members).

No output schema declared.

No examples provided.

rename_project ~92

Rename a project you own (the display name only: the slug, which identifies the project in URLs and API paths, never changes). Requires an ACCOUNT-scoped management token and the `config` scope. 404-equivalent error when you do not own the slug.

NameTypeReqDescription
namestringyesThe new display name (1–100 chars).
slugstringyesThe slug of a project you own.

No output schema declared.

No examples provided.

resend_invite ~84

Re-send the invitation email for a still-pending invite, by member ID or email (from list_members). The original accept link is reused. Already-accepted members are rejected. Owner only.

NameTypeReqDescription
emailstringEmail address (alternative to memberId — targets the first matching pending invite).
memberIdstringMember record UUID (from list_members).

No output schema declared.

No examples provided.

resume_addon ~123

Resume (un-cancel) a pending-cancel add-on whose paid-through cycle has not yet ended. Clears the cancellation so the add-on renews normally at the next cycle boundary. No new charge — the cycle was already paid. Stackable add-ons cannot be resumed; buy a new unit instead. Returns {addonKey, project, nextRenewalAt, resumed}. Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
addonKeystringyesAdd-on key to resume (e.g. "log_retention", "rpm_5000").

No output schema declared.

No examples provided.

retry_dlq_entry ~119

Re-enqueue a DLQ entry to the main relay stream and delete it from the DLQ. A replay is billed like any relay — it charges the entry's original credit cost to the project before re-sending; if the balance is too low the entry stays in the DLQ and this returns an insufficient-credits error (top up and retry). Succeeds if the entry exists, errors if it's already gone (retried or discarded). Requires edit access.

NameTypeReqDescription
idstringyesDead-letter entry id from list_dlq.

No output schema declared.

No examples provided.

reveal_rotation_successor ~91

One-shot retrieval of the plaintext for a successor minted by the auto-rotation scheduler (not by rotate_api_key — that returns its own plaintext directly). Decrypts the at-rest ciphertext, returns it once, then destroys it; a second call errors. Only available while the predecessor still has an unrevealed successor.

NameTypeReqDescription
keyIdstringyesUUID of the predecessor key whose successor to reveal.

No output schema declared.

No examples provided.

revoke_api_key ~45

Manual hard revoke. The key stops authenticating on the next request. Owner anywhere, editor on own keys.

NameTypeReqDescription
keyIdstringyesUUID of the key to revoke.

No output schema declared.

No examples provided.

revoke_project_token ~118

Revoke a PROJECT-scoped management token on a project you own, any holder's, not just your own (the account-owner kill switch for a leaked or retired integration's management token). Soft-revoke: the row stays for traceability and the management token is rejected immediately. Idempotent. Requires an ACCOUNT-scoped management token and the `config` scope.

NameTypeReqDescription
slugstringyesThe slug of a project you own.
tokenIdstringyesThe management token UUID (from create_project_token or list_project_tokens).

No output schema declared.

No examples provided.

rollback_config ~266

Preview or apply publishing a retained line revision over what is currently published, clearing any pending schedule. Without confirmRevision this only returns the diff (the redacted change-gate preview, same shape as config_diff) between what is currently published and the target revision — it changes nothing. To apply, call again with confirmRevision set to the diff's currentRevision; if a publish landed since the preview, confirmRevision is now stale and the call is refused with error "rollback_confirmation_conflict" instead of silently overwriting the newer publish — read the fresh diff and confirm again. Applying also requires confirmUnsigned, the preview's unsignedFingerprint, so a signing secret expiring between the preview and the confirm cannot roll a target back unsigned without you having seen it named.

NameTypeReqDescription
confirmRevisionintegerThe currently-published revision number from the preview diff. Omit to preview only; include to apply.
confirmUnsignedstringThe preview diff's unsignedFingerprint. Required whenever confirmRevision is given: a target's retained signing secret expires on a clock, so this proves the confirm saw the same set of targets the p…
lineKeystringyes
revisionintegeryes

No output schema declared.

No examples provided.

rotate_api_key ~66

Mint a linked successor for an existing key. Returns the successor plaintext exactly once — store it now. The predecessor stays valid through its overlap window so callers can swap without downtime. Owner anywhere, editor on own keys.

NameTypeReqDescription
keyIdstringyesUUID of the key to rotate.

No output schema declared.

No examples provided.

schedule_line_publish ~44

Schedule one non-empty line draft. Active subscribers required.

NameTypeReqDescription
draftRevisionintegeryes
lineKeystringyes
scheduledAtstringyes

No output schema declared.

No examples provided.

set_burst_opt_in ~133

Enable or disable the auto-decaying burst window for live traffic and publish the change immediately. When enabled, brief spikes a little above your steady RPM cap are absorbed at the normal credit rate (no surcharge, no burst SKU) instead of being rejected. Sustained overage decays back to your steady cap; headroom returns once traffic cools below the cap or you add RPM. Burst usage is tracked so you can see when to upgrade. Default is off (steady cap is a hard 429). Requires edit access.

NameTypeReqDescription
enabledbooleanyestrue to enable the burst window; false to disable.

No output schema declared.

No examples provided.

set_docs_shared ~153

Turn the line's public OpenAPI docs on or off. When enabled, the line's spec is published at docs.{baseDomain}/{slug}/{lineKey} (and …/openapi.json); when disabled those URLs return 404. The `docsShared` field on each line read (list_lines) reflects the current state. Requires edit access.

NameTypeReqDescription
commitModestringDefaults to publish. Draft writes require draftRevision.
draftRevisionintegerCurrent line draft revision, required for draft writes.
enabledbooleanyestrue to publish the line's public docs; false to take them down.
lineKeystringyesThe line key, e.g. "v1".

No output schema declared.

No examples provided.

set_key_policy ~78

Owner-only. Edit the project's key policy. Only fields present in the patch are touched. Editors calling this get an error — use get_key_policy to read.

NameTypeReqDescription
defaultKeyTtlDaysinteger|null
editorsMayCreateNonExpiringKeysboolean
maxKeyTtlDaysinteger|null

No output schema declared.

No examples provided.

set_member_role ~99

Change a member's role between editor, viewer, and billing. Identify the member by their member ID or email (from list_members); the project owner's own role cannot be changed. Returns the updated member record. Owner only.

NameTypeReqDescription
emailstringEmail address (alternative to memberId — targets the first matching member).
memberIdstringMember record UUID (from list_members).
rolestringyesThe new role.

No output schema declared.

No examples provided.

set_outbound_allowlist ~177

Narrow the project's outbound host allowlist — the hosts a target may point at. The current list is on get_project as `outboundHostAllowlist` (empty means any public host). This tool may only narrow it: `patterns` must be a strict subset of, or equal to, the current list, compared as exact strings — submitting a wildcard that would cover an existing exact host, or clearing to empty, is refused as a widen. Widening the list is web-only, in the panel. Refused when the project already has a target (inactive lines included) outside the submitted list. Requires edit access.

NameTypeReqDescription
patternsarrayyesThe full replacement list of allowed hosts, e.g. ["api.stripe.com", "*.internal.example.com"]. Must be a subset of the current outboundHostAllowlist.

No output schema declared.

No examples provided.

set_overage_billing ~119

Turn the project owner's overage billing on or off, for the whole account. Returns `{overageBilling}`, the setting get_billing reads back. Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
enabledbooleanyesTrue (the default) bills credits past your allowance and prepaid balance as overage; false slows the account to the free rate once its credits are gone instead, and nothing is refused. Turning it off…

No output schema declared.

No examples provided.

set_rpm_ceiling ~149

Set or clear a self-set ceiling on this project's own effective live-traffic RPM (Traffic shaping) — for when your origin can't take the throughput your plan grants. Never plan-gated: the ceiling can only LOWER your effective RPM below your plan/add-on rate, never raise it, and never touches billing. Steady traffic is capped at the ceiling; if Burst Protect is on, its headroom is measured above the ceiling, not above the plan rate. The current value is on get_project as `rpmCeiling` (null = no ceiling). Requires edit access.

NameTypeReqDescription
rpmCeilinginteger|nullyesA positive integer to set the ceiling, or null to clear it.

No output schema declared.

No examples provided.

start_subscription ~73

Begin a new Pro or Scale subscription for the project owner. Returns `{checkoutUrl, plan}` — surface the URL to the human for approval. Errors if the owner is already on an active paid plan (use change_plan instead). Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
planstringyes

No output schema declared.

No examples provided.

start_topup ~106

Begin a credit-pack top-up for the project owner. Pass the pack`s `eurCents` (from list_credit_packs). Returns `{checkoutUrl, credits, eurCents, directCharge}` or `{transactionId, credits, eurCents, directCharge:true}` on subsequent MCP purchases. Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
eurCentsintegeryesPack price in EUR cents, matching a pack returned by list_credit_packs.

No output schema declared.

No examples provided.

subscribe_addon ~234

Subscribe the project owner to a monthly add-on (RPM upgrade, team seat, extended log retention, extra file storage in +5 GB blocks, …). Charges the saved payment method immediately, then auto-renews every 30 days until `unsubscribe_addon` — or until the subscription ends, after which the already-paid cycle stays active to its own end date and stops without further charges. Requires an active Pro/Scale subscription and a saved PM. RPM upgrades (rpm_*) are per-project and apply to THIS project automatically. Returns `{addonKey, project, monthlyEurCents, transactionId, chargeStatus, activatedAt, nextRenewalAt}`. `transactionId`: The Paddle transaction id, or null while Paddle has not yet listed the charge. The purchase is recorded either way; do not retry it. `chargeStatus`: `pending` or `completed`. Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
addonKeystringyesStable key from list_addons (e.g. "team_member", "rpm_2000", "log_retention", "file_storage").

No output schema declared.

No examples provided.

unarchive_project ~86

Restore an archived project you own to the data plane. Restoring consumes one of your plan's active-project slots, so at the limit this returns an error telling you to archive another project or upgrade. Idempotent for an already-active project. Requires an ACCOUNT-scoped management token and the `config` scope.

NameTypeReqDescription
slugstringyesThe slug of a project you own.

No output schema declared.

No examples provided.

unsubscribe_addon ~67

Cancel an active add-on subscription. Stops future charges; the current cycle stays active until expiry. RPM upgrades are cancelled for THIS project. Returns `{addonKey, project, cancelledAt}`. Owner-only; requires a token minted with the billing scope.

NameTypeReqDescription
addonKeystringyes

No output schema declared.

No examples provided.

update_credential ~202

Rename a credential and/or rotate its secret, publishing the change immediately so every target that uses this credential picks it up right away. Omit a secret field (or the whole `auth` object) to keep the existing value — the vault can never show a secret back to confirm it, so leaving it out means "unchanged," not "cleared." The destination host cannot be changed here: create a new credential for a new destination.

NameTypeReqDescription
authobjectSame shape as create_credential. Omit to keep the existing auth entirely.
credentialIdstringyesUUID of the credential (from list_credentials).
destinationHoststringPermanent — may only restate the credential's current host (omit it, or send back what list_credentials reported). Any other value is refused; a credential is never re-aimed, it is replaced.
namestringNew name. Omit to keep the existing one.

No output schema declared.

No examples provided.

update_endpoint ~124

Update an endpoint immediately or in its line draft. The patch is merged field-by-field. Requires edit access.

NameTypeReqDescription
commitModestringDefaults to publish. Draft writes require draftRevision.
draftRevisionintegerCurrent line draft revision, required for draft writes.
endpointIdstringyesThe endpoint UUID.
lineKeystringyesThe line key.
patchobjectyesPartial endpoint document — same shape as create_endpoint, every field optional.
scheduledAtstringCompatibility alias: stage this update then schedule its line.

No output schema declared.

No examples provided.

Common questions

What is the EchoRelay MCP server?

EchoRelay is an MCP server listed in the public MCP registry as dev.echorelay/management. A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP. This page covers its hosted endpoint (https://mcp.echorelay.dev).

Is the EchoRelay MCP server safe to use?

EchoRelay 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 EchoRelay MCP server expose?

EchoRelay exposes 80 tools: get_project, list_lines, list_endpoints, get_endpoint, get_config, and 75 more. Their descriptions and schemas cost roughly 9,617 tokens of context every time the server is loaded.

Does the EchoRelay MCP server require authentication?

Yes. EchoRelay 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 EchoRelay MCP server still maintained?

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