MCP servers observed by Lowdown
io.github.joelp22-maker/referencesource 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); 17 tools listed. On 2026-11-17 a tool description with a URL appeared (new domain: referencesource.org). MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 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:io.github.joelp22-maker/referencesource
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.joelp22-maker/referencesource?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 1 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, tool names changed; tool count 8 → 17; a tool description with a URL appeared (referencesource.org)
What tools does it list?
17 tools on 2026-11-17:
brief_for_joecompare_fieldcontrolcontrols_forfind_factget_recordlist_datasetsmessage_from_joemessage_supervisormodel_statusnext_task_for_musereplies_for_joerequest_keysearch_recordssubmit_task_resultverify_quoteworking_brief_for_muse
MCP Registry declaration
- Registry name:
io.github.joelp22-maker/referencesource - Declared version: 1.2.0
- Status: active
- Declared hosts:
referencesource.org
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.joelp22-maker/referencesource", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.joelp22-maker/referencesource?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.joelp22-maker/referencesource -- npx -y referencesource-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).