Remote MCP · Endpoint

Kinro MCP server

No. Kinro answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.kinro.com/mcp

The last check completed an MCP handshake.

Registry name
com.kinro/kinro
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
63 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Business insurance advice and real carrier quotes for U.S. small businesses from a licensed broker.
Listing
From the official MCP registry (active).
Recent checks of Kinro
CheckedResultHandshake
1 hour agoHandshake completed63 ms
18 hours agoHandshake completed70 ms
2 days agoHandshake completed74 ms
3 days agoHandshake completed63 ms
4 days agoHandshake completed77 ms
5 days agoHandshake completed95 ms
6 days agoHandshake completed85 ms
7 days agoHandshake completed70 ms
10 days agoHandshake completed54 ms
13 days agoHandshake completed124 ms
15 days agoHandshake completed72 ms
17 days agoHandshake completed61 ms
19 days agoHandshake completed62 ms
21 days agoHandshake completed55 ms
23 days agoHandshake completed76 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Kinro and makes no claim about it beyond what these checks measured.