io.github.kansei-link/kansei-mcp-server
io-github-kansei-link-kansei-mcp-server declares 3 capabilities across 3 tools, with 1 critical issue.
Issues
3 of 3 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
3 of 3 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
3 of 3 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
1 tool can modify data and declares no limit.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
search_services | read |
declared |
lookup | read |
inferred |
report | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-16 | 10 | tools/list on https://kansei-link-mcp-production.up.railway.app/mcp, published in the official MCP registry as io.github.kansei-link/kansei-mcp-server 1.2.4 |
| 2026-10-11 | 10 | tools/list on https://kansei-link-mcp-production-b054.up.railway.app/mcp, published in the official MCP registry as io.github.kansei-link/kansei-mcp-server 1.1.1 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.