MCP servers observed by Lowdown
io.github.RectaBuild/recta MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 10 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-18 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.RectaBuild/recta
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.RectaBuild/recta?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 3 of 3 compared days.
- 2026-11-18: input or output schemas changed, descriptions changed, tool names changed; tool count 9 → 10
- 2026-11-15: input or output schemas changed, descriptions changed
- 2026-11-12: input or output schemas changed, descriptions changed
What tools does it list?
10 tools on 2026-11-18:
recta_aboutrecta_fit_checkrecta_preflightrecta_prepare_signed_requestrecta_request_templaterecta_saving_oddsrecta_send_signed_requestrecta_service_descriptorrecta_statusrecta_trial_evaluation
MCP Registry declaration
- Registry name:
io.github.RectaBuild/recta - Declared version: 1.3.4
- Status: active
- Declared hosts:
api.recta.build
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.RectaBuild/recta", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.RectaBuild/recta?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.RectaBuild/recta -- npx -y @recta/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).