MCP servers observed by Lowdown
dev.echorelay/management MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 80 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.echorelay/management
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.echorelay/management?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed
- 2026-11-14: input or output schemas changed
What tools does it list?
80 tools on 2026-11-17:
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_linegenerate_line_draftget_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_overage_billingset_rpm_ceilingstart_subscriptionstart_topupsubscribe_addonunarchive_projectunsubscribe_addonupdate_credentialupdate_endpoint
MCP Registry declaration
- Registry name:
dev.echorelay/management - Declared version: 0.13.0
- Status: active
- Declared hosts:
mcp.echorelay.dev
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:dev.echorelay/management", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.echorelay/management?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).