MCP servers observed by Lowdown
io.github.JCLVSH/dropspace 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); 40 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:io.github.JCLVSH/dropspace
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.JCLVSH/dropspace?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.
- 2026-11-16: server version changed
- 2026-11-13: server version changed
What tools does it list?
40 tools on 2026-11-16:
analyze_personaapply_recommendationapprove_autopilot_draftconfigure_autopilotcreate_launchcreate_personadelete_all_postsdelete_launchdelete_personadelete_postdiscard_persona_analysisdismiss_recommendationfinalize_personagenerate_contentgenerate_mediaget_audienceget_autopilotget_batch_launch_analyticsget_changelogget_dropspace_statusget_launchget_launch_analyticsget_launch_statusget_media_jobget_personaget_usagelist_autopilot_reviewlist_autopilot_runslist_connectionslist_launcheslist_personaslist_recommendationspublish_launchreject_autopilot_draftretry_launchretry_launch_contentrun_autopilot_nowupdate_connection_profileupdate_launchupdate_persona
MCP Registry declaration
- Registry name:
io.github.JCLVSH/dropspace - Declared version: 2.54.3
- Status: active
- Declared hosts:
api.dropspace.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:io.github.JCLVSH/dropspace", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.JCLVSH/dropspace?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:io.github.JCLVSH/dropspace -- npx -y @jclvsh/dropspace
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).