# io.github.kansei-link/kansei-mcp-server (remote · kansei-link-mcp-production-b054.up.railway.app)

SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.

- Trust score: 70/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `kansei-link-mcp-production-b054.up.railway.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054.md), [page](https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054)
- npm · `@kansei-link/mcp-server`: 32/100, [markdown](https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-server.md), [page](https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-server)

## Channel facts

- Endpoint: `https://kansei-link-mcp-production-b054.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2788 tokens (~111/item across 25 items; 3 tools + 22 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http kansei-link-kansei-mcp-server https://kansei-link-mcp-production-b054.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.kansei-link-kansei-mcp-server]
url = "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add kansei-link-kansei-mcp-server --url https://kansei-link-mcp-production-b054.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kansei-link-kansei-mcp-server:
    url: "https://kansei-link-mcp-production-b054.up.railway.app/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 69, +15)

- [security regression] Stability: 0.20 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “search_services” was removed
- [security regression] Tool “report” was removed
- [security regression] Tool “lookup” was removed
- [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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: fail → unverified
- [functional improvement] Schema quality: 738 → 111
- [functional improvement] Schema quality: 2216 → 753
- [functional improvement] Schema quality: unverified → good
- [functional] New prompt “build-workflow”
- [functional] New prompt “connect-service”
- [functional] New prompt “find-service”
- [functional] New resource “mcp-status”
- [functional] New resource “categories”
- [functional] New resource “freee MCP”
- [functional] New resource “HubSpot Japan MCP”
- [functional] New resource “Money Forward Cloud MCP”
- [functional] New resource “Notion MCP”
- [functional] New resource “ElevenLabs”
- [functional] New resource “Eight”
- [functional] New resource “Chroma”
- [functional] New resource “Garoon MCP”
- [functional] New resource “Chatwork MCP”
- [functional] New resource “Brave Search”
- [functional] New resource “LINE Messaging MCP”
- [functional] New resource “Microsoft Teams MCP”
- [functional] New resource “Qdrant”
- [functional] New resource “Slack MCP”
- [functional] New resource “Stripe”
- [functional] New resource “Tavily”
- [functional] New resource “Backlog MCP”
- [functional] New resource “Asana MCP”
- [functional] New resource “TeamSpirit”
- [functional] New resource “kintone MCP”
- [functional] New tool “lookup”
- [functional] New tool “report”
- [functional] New tool “search_services”

### 2026-08-01 (score 54, −9)

- [functional regression] Schema quality: 111 → 738
- [functional regression] Resource “Slack MCP” was removed
- [functional regression] Resource “Notion MCP” was removed
- [functional regression] Resource “Asana MCP” was removed
- [functional regression] Resource “Backlog MCP” was removed
- [functional regression] Resource “Brave Search” was removed
- [functional regression] Resource “Chatwork MCP” was removed
- [functional regression] Resource “Chroma” was removed
- [functional regression] Resource “Eight” was removed
- [functional regression] Resource “ElevenLabs” was removed
- [functional regression] Resource “Garoon MCP” was removed
- [functional regression] Resource “HubSpot Japan MCP” was removed
- [functional regression] Resource “LINE Messaging MCP” was removed
- [functional regression] Resource “Microsoft Teams MCP” was removed
- [functional regression] Resource “Money Forward Cloud MCP” was removed
- [functional regression] Resource “Qdrant” was removed
- [functional regression] Resource “Stripe” was removed
- [functional regression] Resource “Tavily” was removed
- [functional regression] Resource “TeamSpirit” was removed
- [functional regression] Resource “categories” was removed
- [functional regression] Resource “freee MCP” was removed
- [functional regression] Resource “kintone MCP” was removed
- [functional regression] Resource “mcp-status” was removed

### 2026-07-31 (score 63, +13)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 50, −11)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (3)

### `search_services` (~309 tokens)

Search Services

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.

Input parameters:

- `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, required): What you want to accomplish (e.g., 'send invoice', 'manage employees', 'track attendance')
- `limit` (number): Max results to return (default: 5)

### `lookup` (~321 tokens)

Lookup

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.

Input parameters:

- `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

### `report` (~833 tokens)

Report

Contribute data back to the KanseiLink community. Report success/failure after using a service (5 seconds, helps everyone), submit feedback, record API change events, or share your qualitative experience. PII is auto-masked. This is step 4 of the standard flow: search_services → lookup → (execute) → report.

Input parameters:

- `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.
- `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.
- `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…
- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 54
- 2026-07-31: 63
- 2026-07-30: 50
- 2026-07-29: 61
- 2026-07-28: 60
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://kansei-link-mcp-production-b054.up.railway.app/mcp
- Repository: https://github.com/kansei-link/kansei-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054/changelog.json
- HTML version of this page: https://verifymcp.io/servers/kansei-link-kansei-mcp-server/kansei-link-mcp-production-b054