Remote MCP · Endpoint

Kitfinch MCP server

No. Kitfinch answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://kitfinch.com/mcp

The last check completed an MCP handshake.

Registry name
com.kitfinch/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Business software by trade for US small service businesses, with prices verified at the source.
Listing
From the official MCP registry (active).
Recent checks of Kitfinch
CheckedResultHandshake
2 hours agoHandshake completed293 ms
20 hours agoHandshake completed333 ms
2 days agoHandshake completed350 ms
4 days agoHandshake completed313 ms
6 days agoHandshake completed321 ms
9 days agoHandshake completed364 ms
11 days agoHandshake completed439 ms
13 days agoHandshake completed470 ms
15 days agoHandshake completed529 ms
17 days agoHandshake completed402 ms
19 days agoHandshake completed392 ms
21 days agoHandshake completed397 ms
23 days agoHandshake completed406 ms
24 days agoHandshake completed880 ms

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

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 Kitfinch and makes no claim about it beyond what these checks measured.