MCP servers observed by Lowdown
dev.spacepost/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 46 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 compared days; 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.spacepost/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.spacepost/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: 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?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
46 tools on 2026-11-16:
cancel_emailcreate_api_keycreate_audiencecreate_broadcastcreate_contactcreate_domaincreate_suppressioncreate_tenantcreate_webhookdelete_api_keydelete_audiencedelete_broadcastdelete_contactdelete_domaindelete_suppressiondelete_tenantdelete_webhookget_audienceget_broadcastget_broadcast_readinessget_contactget_domainget_emailget_tenantget_webhooklist_api_keyslist_audienceslist_broadcastslist_contactslist_domainslist_emailslist_suppressionslist_tenantslist_webhookspause_tenantsend_batch_emailssend_broadcastsend_emailunpause_tenantupdate_broadcastupdate_contactupdate_domainupdate_emailupdate_tenantupdate_webhookverify_domain
MCP Registry declaration
- Registry name:
dev.spacepost/mcp - Declared version: 0.2.2
- Status: active
- Declared hosts:
api.spacepost.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.spacepost/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.spacepost/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:dev.spacepost/mcp -- npx -y @spacepost/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).