MCP servers observed by Lowdown
io.github.cirralink-stack/kevaremesh-gateway 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); 16 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-14 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.cirralink-stack/kevaremesh-gateway
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.cirralink-stack/kevaremesh-gateway?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-14: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 15 → 16
What tools does it list?
16 tools on 2026-11-17:
kevaremesh_agent_commerce_statuskevaremesh_auto_usekevaremesh_check_owned_receiptkevaremesh_discover_provider_candidateskevaremesh_find_or_build_apikevaremesh_find_owned_apikevaremesh_get_owned_input_contractkevaremesh_locate_owned_receiptkevaremesh_preview_owned_apikevaremesh_quote_provider_batchkevaremesh_quote_provider_routekevaremesh_reconcile_gateway_receiptkevaremesh_retrieve_paid_api_resultkevaremesh_route_intentkevaremesh_search_marketplacekevaremesh_use_infrastructure
MCP Registry declaration
- Registry name:
io.github.cirralink-stack/kevaremesh-gateway - Declared version: 0.4.60
- Status: active
- Declared hosts:
kevaremesh-web.vercel.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.cirralink-stack/kevaremesh-gateway", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.cirralink-stack/kevaremesh-gateway?menu=install-check
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).