Kinro MCP server
com.kinro/kinrokinro.comstreamable-httpv0.4.0Scanned
Business insurance advice and real carrier quotes for U.S. small businesses from a licensed broker.
2 tools: 2 change things.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Kinro MCP server can do
The Kinro MCP server is published by kinro.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: ask_kinro and get_kinro_messages), but cannot delete data. None of its tools only reads.
1 tool reads private data (get_kinro_messages); 2 tools bring in text other people can write (ask_kinro and get_kinro_messages).
The fixed checks matched 2 findings (long-description and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 0.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
ask_kinroAsk Kinro, a licensed business insurance broker, about the user’s business insurance: what coverage fits the business, carrier eligibility and exclusions, and quotes.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,118 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...through the quote with the user, and never buy or enter payment details for them."
Description, as the server wrote it 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 you can open web pages, open it to go through the quote with the user, and never buy or enter payment details for them.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
get_kinro_messagesRead 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.Reads private dataReads text others write1 finding
Why it is in this group
- The name "get_kinro_messages" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe name "get_kinro_messages" says "get" and "message": it reads messages.
- private-dataThe description's first sentence says "read" and "conversation": it reads messages.
- untrusted-inputThe name "get_kinro_messages" says "get" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "conversation": it reads messages, which other people can write.
Findings
- Warn
The server marks "get_kinro_messages" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_kinro_messages" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.kinro.com/mcp: tools/list returned 2 tools to an anonymous client, including ask_kinro (write), get_kinro_messages (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_kinro_messages" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_kinro_messages" says "get": a word for reading.
- Infoask_kinro
The description is 2,118 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...through the quote with the user, and never buy or enter payment details for them."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http kinro https://api.kinro.com/mcpclaude mcp add --transport http kinro https://api.kinro.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__kinro__ask_kinro",
"mcp__kinro__get_kinro_messages"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as kinro. Review it before you use it.
Capability tags behind 2 rules
- mcp__kinro__ask_kinro untrusted-input
- mcp__kinro__get_kinro_messages private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kinro/kinro/verify?hash=64e9bb26b5b80f04de587ae498b31d40f3dbc862cd0e3779a999741b8fe83202" | jq -e '.changed == false'Pinned hash 64e9bb26b5b8, from Nov 13, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kinro/kinro/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kinro/kinro)Source: MCP Registry. Synced Oct 21, 2026, 17:57 UTC.
Kinro MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Kinro MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Kinro MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Kinro MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Kinro MCP server have?
- 2 tools: 2 write. ask_kinro and get_kinro_messages.
Does the Kinro MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Kinro MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Kinro MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.