Is the KAI Router MCP server down?

mcp-registry/io.github.kingdt1991-netizen/kai-router · v1.1.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:53 UTC · handshake 407ms

As of 2026-11-22 16:53 UTC, the KAI Router MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
801
outages (90d)
0
tools
1

Find pay-per-call x402 tools (USDC on Base) for any task, ranked by relevance and real demand.

Point your MCP client at this streamable-http endpoint: https://gycvbmliobjydcdghhtj.supabase.co/functions/v1/kai-x402-router/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 2 warning(s) across 1 tool(s); ~132 tokens of tool definitions.
Scores higher than 4% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~132 tokens per session — lighter than 99% of servers.
71 → 71 since 2026-11-16
no tool-poisoning patterns
Descriptions30
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (3)

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: find_paid_tool

1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: find_paid_tool

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kingdt1991-netizen%2Fkai-router/fixes

find_paid_tool 1 change
{
  "name": "find_paid_tool",
  "description": "Find pay-per-call (x402, USDC on Base) tools for a task. Returns ranked tools with price, recent demand and the URL to call. Free.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 25,
        "minimum": 1
      },
      "query": {
        "type": "string",
        "description": "What you need, e.g. 'token price' or 'wallet risk check'"
      },
      "max_price_usdc": {
        "type": "number",
        "description": "Optional price ceiling per call"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.kingdt1991-netizen/kai-router"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.kingdt1991-netizen/kai-router"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fio.github.kingdt1991-netizen%2Fkai-router.svg)](https://glimind.com/server/mcp-registry%2Fio.github.kingdt1991-netizen%2Fkai-router?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kingdt1991-netizen%2Fkai-router?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.kingdt1991-netizen%2Fkai-router.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:56aaf5d2aa7fbd65…, first seen 2026-11-16, included at leaf 302645 of 384,671. Version history · verify what your client received.

Tools (1)

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the KAI Router MCP server down right now?

As of 2026-11-22 16:53 UTC, the KAI Router MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does KAI Router MCP server provide?

KAI Router MCP server advertises 1 tool, including find_paid_tool.

How do I install KAI Router MCP server?

Point your MCP client at this streamable-http endpoint: https://gycvbmliobjydcdghhtj.supabase.co/functions/v1/kai-x402-router/mcp

Is the KAI Router MCP server safe to connect to an AI agent?

Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of KAI Router MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve