# Kinro (remote · api.kinro.com)

Business insurance advice and real carrier quotes for U.S. small businesses from a licensed broker.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.kinro.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-kinro-kinro/api.md), [page](https://verifymcp.io/servers/com-kinro-kinro/api)

## Channel facts

- Endpoint: `https://api.kinro.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## 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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1088 tokens (~544/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Kinro MCP server?

Kinro is a hosted endpoint at https://api.kinro.com/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.

### Claude

```bash
claude mcp add --transport http com-kinro-kinro 'https://api.kinro.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-kinro-kinro": {
      "url": "https://api.kinro.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-kinro-kinro": {
      "type": "http",
      "url": "https://api.kinro.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-kinro-kinro]
url = "https://api.kinro.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-kinro-kinro": {
      "type": "remote",
      "url": "https://api.kinro.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-kinro-kinro --url 'https://api.kinro.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-kinro-kinro:
    url: "https://api.kinro.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-kinro-kinro": {
      "Transport": "http",
      "Url": "https://api.kinro.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-kinro-kinro -t streamable-http -u 'https://api.kinro.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-kinro-kinro": {
      "type": "http",
      "url": "https://api.kinro.com/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-11-05 (score 80, +1)

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

### 2026-11-02 (score 79, +1)

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

### 2026-10-31 (score 78, +1)

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

### 2026-10-29 (score 77, +1)

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

### 2026-10-27 (score 76, +1)

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

### 2026-10-25 (score 75, +1)

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

### 2026-10-23 (score 74, +1)

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

### 2026-10-21 (score 73, +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.

## MCP tools (2)

### `ask_kinro` (~811 tokens)

Ask Kinro about business insurance

Ask Kinro, a licensed business insurance broker, about the user’s business insurance: what coverage fits the business, carrier eligibility and exclusions, and quotes. Kinro’s AI advisor, Leo, answers. Kinro is not tied to any carrier: it gets real quotes from several carriers in one conversation, so the user does not have to start a separate quoting session with each carrier. Its answers rest on carrier underwriting rules and live quotes, and as the broker Kinro is accountable for its advice and carries errors and omissions insurance for it. Kinro returns coverage answers and any follow-up questions needed to prepare the request. You speak to Kinro for the user: tell it what the user needs, answer its follow-up questions from what the user has told you, ask the user what you do not know, and send the user’s follow-up requests in the same conversation. Kinro handles every conversation as a real insurance request, including on its test endpoint. When testing there and the user has you make up a business, choose details that look real, with no placeholders such as “Test Lane”, and give them as plain facts the way its owner would. Do not call the details fake, fictional, or a test, because Kinro does not quote details it is told are not real. The first call opens a Kinro insurance request for the business and saves what the user shares, so Kinro can prepare quotes. To quote, Kinro sends the business’s details to insurance carriers; carriers get no permission to contact the user. Kinro contacts the user outside this chat, by email or text, only at contact details the user shares and agrees to be contacted at. Each call sends a new message, so do not repeat a call to retry it. Kinro’s messages say what to expect next. Some answers, like quotes, arrive later: when Kinro says it is still working, call get_kinro_messages with wait set to true to get its next messages. A quote message links to the customer’s quote page on kinro.com, with the full quote and its documents: if…

Input parameters:

- `conversation_id` (string): The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID.
- `files` (array): Insurance documents the user attached, such as a current policy, declarations page, certificate of insurance (COI), loss run, or a photo of one: PDF, PNG, or JPEG, up to 25 MB each. Pass each one her…
- `message` (string, required): What you tell Kinro for the user: what the user wants, such as advice, a quote, or a change to one, and the facts about the business the user has given you that Kinro needs to move forward. Write it…

Output parameters:

- `conversation_id` (string): The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID.
- `messages` (array): Kinro's messages, oldest first, each to show the user as written, including links. When nothing new has arrived, one note says so.

### `get_kinro_messages` (~277 tokens)

Get Kinro's messages

Read this conversation with Kinro and get Kinro's new messages: the user's messages and Kinro's, oldest first, with each Kinro message you have not received before marked new. Show the user every new message as written, including links. Returns the latest 5 messages by default; set limit (up to 100) for more or fewer, and new messages are always included. When Kinro says it is still working, for example on a reply or a quote, set wait to true: the call returns as soon as a new message arrives, or after a short wait with a note that nothing is new. Messages you already received stay readable, so use it to recover a reply or quote you missed or lost. It sends nothing to Kinro.

Input parameters:

- `conversation_id` (string): The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID.
- `limit` (integer): How many of the latest messages to return. Default 5, at most 100.
- `wait` (boolean): Set true to wait for Kinro's next message when nothing new has arrived yet, such as while Kinro works on a reply or prices a quote. The call returns as soon as a new message arrives.

Output parameters:

- `conversation_id` (string): The conversation_id returned by ask_kinro. Reuse it for this conversation; omit on the first message. Never invent one or reuse another conversation's ID.
- `has_more` (boolean): True when earlier messages exist. History is limited to the latest 100 messages; newly delivered messages are also included.
- `messages` (array): The conversation's latest messages, oldest first.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-kinro-kinro/api#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69

## Common questions

### What is the Kinro MCP server?

Kinro is an MCP server listed in the public MCP registry as com.kinro/kinro. Business insurance advice and real carrier quotes for U.S. small businesses from a licensed broker. This page covers its hosted endpoint (https://api.kinro.com/mcp).

### Is the Kinro MCP server safe to use?

Kinro scores 80 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 Kinro MCP server expose?

Kinro exposes 2 tools: ask_kinro, get_kinro_messages. Their descriptions and schemas cost roughly 1,088 tokens of context every time the server is loaded.

### Does the Kinro MCP server require authentication?

No. We connected to Kinro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Kinro MCP server still maintained?

Kinro is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Kinro MCP server?

VerifyMCP ran 13 checks on Kinro, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.kinro.com/mcp
- Website: https://kinro.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-kinro-kinro/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-kinro-kinro/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-kinro-kinro/api.json
- HTML version of this page: https://verifymcp.io/servers/com-kinro-kinro/api