MCP servers observed by Lowdown
io.github.polyrank/polyrank-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); 36 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 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.polyrank/polyrank-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.polyrank/polyrank-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?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-16: server version changed
- 2026-11-13: descriptions changed
What tools does it list?
36 tools on 2026-11-16:
polyrank_create_strategypolyrank_get_backtestpolyrank_get_custom_rankingpolyrank_get_lab_limitspolyrank_get_leaderboardpolyrank_get_market_consensuspolyrank_get_metric_windowspolyrank_get_metrics_catalogpolyrank_get_moverspolyrank_get_paper_runpolyrank_get_platform_statspolyrank_get_pulsepolyrank_get_smart_money_reportpolyrank_get_smart_money_reportspolyrank_get_strategypolyrank_get_top_roi_tradespolyrank_get_trader_by_tidpolyrank_get_trader_calibrationpolyrank_get_trader_calibration_by_tidpolyrank_get_trader_metricspolyrank_get_trader_skillpolyrank_get_traders_batchpolyrank_lab_askpolyrank_lab_get_chatpolyrank_lab_list_chatspolyrank_lab_replypolyrank_lab_stoppolyrank_list_backtestspolyrank_list_lab_templatespolyrank_list_ranking_templatespolyrank_list_strategiespolyrank_rank_walletspolyrank_resolve_tidpolyrank_run_backtestpolyrank_start_paperpolyrank_update_strategy
MCP Registry declaration
- Registry name:
io.github.polyrank/polyrank-mcp - Declared version: 0.5.1
- Status: active
- Declared hosts:
mcp.polyrank.app
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.polyrank/polyrank-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.polyrank/polyrank-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:io.github.polyrank/polyrank-mcp -- npx -y @polyrank/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).