MCP servers observed by Lowdown
io.github.blink1217/quant-swarm MCP server: daily status and tool changes
Answered initialize and tools/list on the latest check (2026-11-19) (Lowdown checks this server every 3 days); 16 tools listed. 1 of 4 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; 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.blink1217/quant-swarm
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.blink1217/quant-swarm?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 1
- Required authentication: 3
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 3 of 4 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
11 tools on 2026-11-19:
gym.estimate_cloud_rungym.evaluate_formulagym.evaluate_graphgym.label_regimesgym.paired_previewgym.probe_fragilitygym.prop_challenge_simtournament.forward_leaguetournament.leaderboardtournament.submittournament.verdict
MCP Registry declaration
- Registry name:
io.github.blink1217/quant-swarm - Declared version: 1.1.1
- Status: active
- Declared hosts:
mcp.1.21initiative.com
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.blink1217/quant-swarm", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.blink1217/quant-swarm?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.blink1217/quant-swarm -- uvx quant-swarm
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).