EchoRelay

warnings

mcp.echorelay.dev

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

https://mcp.echorelay.devNo authMCP 2025-11-25v1.13.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 103 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 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; 78 tools listable
Credentials demanded in prose	✕create_credential, get_metrics, get_subscription, start_subscription, change_plan, cancel_subscription, subscribe_addon, unsubscribe_addon, list_active_addons, list_projects, create_project, rename_project, archive_project, protect_project, unarchive_project, create_project_token, list_project_tokens, revoke_project_token These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

18 of the 78 tools listed anonymously say in their own descriptions that they need an account or a key (create_credential, get_metrics, get_subscription, start_subscription, change_plan, cancel_subscription, subscribe_addon, unsubscribe_addon, list_active_addons, list_projects, create_project, rename_project, archive_project, protect_project, unarchive_project, create_project_token, list_project_tokens, revoke_project_token), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

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

activate_linearchive_projectcancel_line_publishcancel_subscriptionchange_planconfig_diffcreate_api_keycreate_credentialcreate_endpointcreate_linecreate_projectcreate_project_tokendeactivate_linedefault_endpoint_templatedelete_credentialdelete_endpointdelete_linediscard_dlq_entrydiscard_draft_endpointdiscard_line_draftdowngrade_addondry_run_endpointduplicate_lineget_billingget_configget_dlq_entryget_endpointget_key_policyget_line_draftget_metricsget_projectget_receiptsget_requestget_subscriptioninvite_memberlist_active_addonslist_addonslist_api_keyslist_audit_eventslist_config_revisionslist_credentialslist_credit_packslist_dlqlist_endpointslist_lineslist_memberslist_project_tokenslist_projectslist_requestslist_subscription_planspreview_line_draftpreview_plan_changeprotect_projectpublish_line_draftremove_memberrename_projectresend_inviteresume_addonretry_dlq_entryreveal_rotation_successorrevoke_api_keyrevoke_project_tokenrollback_configrotate_api_keyschedule_line_publishset_burst_opt_inset_docs_sharedset_key_policyset_member_roleset_outbound_allowlistset_rpm_ceilingstart_subscriptionstart_topupsubscribe_addonunarchive_projectunsubscribe_addonupdate_credentialupdate_endpoint

Contract history

24 Aug 2026v1.13.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

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/echorelay/badge.svg)](https://mcpi.app/servers/echorelay)