MCP servers observed by Lowdown
ai.sendraven/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 72 tools listed. On 2026-11-12 a tool description with a URL appeared. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 after 6 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:ai.sendraven/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.sendraven/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 67 → 72
- 2026-11-12: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 64 → 67; a tool description with a URL appeared
What tools does it list?
72 tools on 2026-11-18:
add_contactadd_sending_domainadd_suppressioncancel_scheduled_emailcount_segmentcreate_audiencecreate_automationcreate_broadcastcreate_conversion_goalcreate_segmentdecide_approvaldelete_automationdelete_contactdelete_mediaemit_eventenroll_in_automationfind_contactget_automationget_automation_metricsget_broadcastget_broadcast_metricsget_contactget_conversion_metricsget_emailget_email_metricsget_email_preferencesget_threadget_usageimport_contactsimport_topic_preferenceslist_audienceslist_automation_enrollmentslist_automationslist_broadcast_recipientslist_broadcastslist_conversion_goalslist_emailslist_medialist_pending_approvalslist_scheduled_emailslist_segmentslist_sending_domainslist_suppressionslist_tagslist_templateslist_threadslist_topicslist_webhook_deliverieslist_webhooksmark_thread_handledpick_broadcast_winnerpreview_broadcastremove_from_audienceremove_suppressionrender_templatereply_to_messageresume_broadcastsave_templatesave_topicsend_broadcastsend_emailsend_template_emailset_automation_statusset_email_preferencesset_utm_tagssuppress_manytag_contactupdate_automationupdate_contactupdate_email_tagsupload_mediaverify_sending_domain
MCP Registry declaration
- Registry name:
ai.sendraven/mcp - Declared version: 0.4.33
- Status: active
- Declared hosts:
mcp.sendraven.ai
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:ai.sendraven/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.sendraven/mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:ai.sendraven/mcp -- npx -y @sendraven/mcp
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).