io.github.kansei-link/kansei-mcp-server
REMOTE · KANSEI-LINK-MCP-PRODUCTION-B054.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 20
SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2893 tokens (~115/item across 25 items; 3 tools + 22 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.kansei-link/kansei-mcp-server server?
io.github.kansei-link/kansei-mcp-server is a hosted endpoint at https://kansei-link-mcp-production-b054.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · kansei-link-mcp-production-b054.up.railway.app
claude mcp add --transport http kansei-link-kansei-mcp-server 'https://kansei-link-mcp-production-b054.up.railway.app/mcp'
{
"mcpServers": {
"kansei-link-kansei-mcp-server": {
"url": "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
}
}
} {
"servers": {
"kansei-link-kansei-mcp-server": {
"type": "http",
"url": "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
}
}
} [mcp_servers.kansei-link-kansei-mcp-server] url = "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kansei-link-kansei-mcp-server": {
"type": "remote",
"url": "https://kansei-link-mcp-production-b054.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add kansei-link-kansei-mcp-server --url 'https://kansei-link-mcp-production-b054.up.railway.app/mcp' --transport streamable-http
mcp_servers:
kansei-link-kansei-mcp-server:
url: "https://kansei-link-mcp-production-b054.up.railway.app/mcp" {
"McpServers": {
"kansei-link-kansei-mcp-server": {
"Transport": "http",
"Url": "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
}
}
} assistant mcp add kansei-link-kansei-mcp-server -t streamable-http -u 'https://kansei-link-mcp-production-b054.up.railway.app/mcp'
{
"mcpServers": {
"kansei-link-kansei-mcp-server": {
"type": "http",
"url": "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 0
- Stability: 0.97 → pass security
- Resource “Chroma” was removed ▼ functional
- Resource “ElevenLabs” was removed ▼ functional
- Resource “Stripe” was removed ▼ functional
- Resource “TeamSpirit” was removed ▼ functional
- Resource “Amplitude” was removed ▼ functional
- New resource “Notion MCP” functional
- New resource “Shopify Japan MCP” functional
- New resource “Square” functional
- New resource “Zapier” functional
- New resource “freee人事労務” functional
- 16 Sept 26 0
- Stability: pass → 0.97 functional
- 14 Sept 26 0
- Stability: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 13 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Sept 26 0
- Resource “Eight” was removed ▼ functional
- Resource “Notion MCP” was removed ▼ functional
- New resource “Amplitude” functional
- New resource “Webflow” functional
- 29 Aug 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://kansei-link-mcp-production-b054.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kansei-link-mcp-production-b054.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kansei-link-mcp-production-b054.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://kansei-link-mcp-production-b054.up.railway.app/mcp | HTTPS enforced | 301 | https://kansei-link-mcp-production-b054.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lookup Lookup ~321
Get everything you need about a service before using it. Default: tips (auth setup, pitfalls, workarounds). Add detail: true for full connection guide, insights: true for usage data. Pass goal: 'workflow description' to find multi-service recipes. This is step 2 of the standard KanseiLink flow: search_services → lookup → (execute) → report.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_with | string | – | Competitor service_id for comparison — triggers history mode |
| detail | boolean | – | Get full connection guide (auth, endpoints, rate limits) |
| feedback_limit | number | – | [feedback] Max results (default 20) |
| feedback_status | string | – | [feedback] Filter by status. Triggers feedback mode when present. |
| feedback_type | string | – | [feedback] Filter by feedback type |
| goal | string | – | Workflow goal — triggers recipe mode (e.g., 'onboard employee') |
| insights | boolean | – | Get aggregated usage data (success rate, trends, errors) |
| mode | string | – | Explicit mode override |
| period | string | – | Time period — triggers history mode |
| service | string | – | Fuzzy service name — triggers combinations mode |
| service_id | string | – | Service ID (from search_services) |
| services | array | – | Your available service IDs — for recipe coverage calculation |
| voice_agent_type | string | – | [voices] Filter by agent type (claude, gpt, gemini) |
| voice_question_filter | string | – | [voices] Filter by question_id |
No output schema declared.
No examples provided.
report Report ~922
Record what happened after using a service: success/failure outcome, feedback, API change events, or qualitative experience. Data is saved to this installation's LOCAL database only (improves local recovery hints and stats) — nothing is sent to KanseiLink unless you separately opt in to sharing. PII is auto-masked before storage. This is step 4 of the standard flow: search_services → lookup → (execute) → report.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Your agent identifier (optional, for follow-up). Used in feedback and voice modes. |
| agent_type | string | – | Agent platform type (claude, gpt, gemini, copilot, llama, deepseek, other). Used in outcome mode (auto-inferred from model_name if omitted) and voice mode. |
| attempt_id | string | – | [outcome] attempt_id returned by lookup. |
| body | string | – | [feedback] Your feedback in detail. Write freely. |
| confidence | string | – | [voice] How confident are you in this assessment? high, medium, low. |
| context | string | – | [outcome] Additional context about the usage (PII will be auto-masked). |
| cost_usd | number | – | [outcome] Actual cost in USD (estimated from tokens if omitted). |
| description | string | – | [event] Details about the event and expected impact. |
| error_type | string | – | [outcome] Error category if failed (e.g., 'auth_error', 'timeout', 'rate_limit', 'schema_mismatch'). |
| estimated_users | number | – | [outcome] Approximate number of end-users your agent serves. |
| event_date | string | – | [event] When the event occurred or takes effect (YYYY-MM-DD). |
| event_type | string | – | [event] Category: api_change, api_deprecation, law_amendment, pricing_change, outage, security_incident, feature_launch, competitor_move, mcp_update, other. |
| failed_step | string | – | [outcome] Step identifier where execution stopped. |
| feedback_type | string | – | [feedback] Type of feedback: suggestion, missing_data, correction, feature_request, workaround_tip, bug_report, praise, other. |
| impact_expected | string | – | [event] Expected impact: positive, negative, neutral, unknown. |
| input_tokens | integer | – | [outcome] Input/prompt token count. |
| is_retry | boolean | – | [outcome] Whether this is a retry of a previously failed call. |
| latency_ms | number | – | [outcome] Response time in milliseconds. |
| mode | string | – | Explicit mode selection. Auto-detected from params if omitted: success → outcome, question_id → voice, event_type → event, subject+body → feedback. |
| model_name | string | – | [outcome] LLM model used (e.g., 'claude-sonnet-4', 'gpt-4o'). |
| output_tokens | integer | – | [outcome] Output/completion token count. |
| priority | string | – | [feedback] How important: low, normal, high, critical. Default: normal. |
| question_id | string | – | [voice] Which question to answer: selection_criteria, would_recommend, biggest_frustration, best_feature, switching_likelihood, auth_experience, doc_quality, error_handling, compared_to_competitor, m… |
| recipe_id | string | – | [outcome] Recipe used for this attempt. |
| recipe_version | integer | – | [outcome] Recipe version returned by lookup. |
| response_choice | string | – | [voice] Quick rating where applicable (e.g., 'strongly_yes', 'excellent', 'ready'). |
| response_text | string | – | [voice] Your honest answer in your own words. |
| service_id | string | – | Service ID. Required for outcome and voice modes. Optional for feedback and event. |
| subject | string | – | [feedback] Short summary of your feedback (1 line). |
| success | boolean | – | [outcome] Whether the operation succeeded. |
| task_type | string | – | [outcome] Operation performed (e.g., 'create_invoice', 'search_contacts'). |
| title | string | – | [event] Short event title (e.g., 'freee API v3 deprecation'). |
| workaround | string | – | [outcome] How you resolved the issue, if any. Helps future agents. |
No output schema declared.
No examples provided.
search_services Search Services ~309
Before attempting ANY SaaS API integration, call this tool. Agents waste 3-5x more tokens on trial-and-error with stale training data — this returns current, structured service evaluations (connection method, guides, known pitfalls) so you succeed on the first try. If the user mentions ANY SaaS service (freee, SmartHR, kintone, Slack, Notion, MoneyForward...) or says 'use kanseilink', always call this. Covers 900+ services with growing agent-readiness signals. Strongest in Japanese SaaS with growing global coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_ready | string | – | Filter by agent readiness: 'verified' (🟢 battle-tested, success rate ≥80%), 'connectable' (🟡 API/MCP exists but unproven), 'info_only' (⚪ no API). Omit for all. |
| category | string | – | Filter by category: crm, project_management, communication, accounting, hr, ecommerce, legal, marketing, groupware, productivity, storage, support, payment, logistics, reservation, data_integration,… |
| compact | boolean | – | Return minimal fields for token efficiency. Default: false |
| intent | string | yes | What you want to accomplish (e.g., 'send invoice', 'manage employees', 'track attendance') |
| limit | number | – | Max results to return (default: 5) |
No output schema declared.
No examples provided.
What is the io.github.kansei-link/kansei-mcp-server server?
io.github.kansei-link/kansei-mcp-server is listed in the public MCP registry as io.github.kansei-link/kansei-mcp-server. SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings. This page covers its hosted endpoint (https://kansei-link-mcp-production-b054.up.railway.app/mcp).
Is the io.github.kansei-link/kansei-mcp-server server safe to use?
io.github.kansei-link/kansei-mcp-server scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.kansei-link/kansei-mcp-server server expose?
io.github.kansei-link/kansei-mcp-server exposes 3 tools: search_services, lookup, report. Their descriptions and schemas cost roughly 1,552 tokens of context every time the server is loaded.
Does the io.github.kansei-link/kansei-mcp-server server require authentication?
No. We connected to io.github.kansei-link/kansei-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.kansei-link/kansei-mcp-server server still maintained?
io.github.kansei-link/kansei-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.