Summary
The answer to 'how do I authenticate against this API' arrives before the first failed attempt.
Five tools replaced an earlier surface of 25, and lookup and report each auto-detect their mode from the arguments you pass. The measurement side is separate and off by default — installing the hook does not transmit anything until you consent.
What it is
A local SQLite catalog of SaaS services and MCP servers, exposed as five tools. The agent asks which service fits an intent, reads the auth setup and known gotchas, calls the real API, then reports how it went.
What you get
- search_services — find a service by what you are trying to do, not by name
- lookup — auth setup, pitfalls and workarounds for one service; also full connection guides, usage data, multi-service recipes and combinations
- report — send back success or failure, latency and the workaround that fixed it
- inspect — the anomaly queue, verification submissions, update proposals and snapshots
- analyze — token-savings and cost analysis across the services you call
- A monthly local report of your own session token totals, failed calls and retry chains
Requirements
Npx and any MCP client. Published as @kansei-link/mcp-server, stdio by default; a Streamable HTTP endpoint is also registered. The catalog ships inside the package as a SQLite file, so no signup and no network call is needed to read it.
Setup effort
One command — npx @kansei-link/mcp-server