Remote MCP · Endpoint

Kitbench MCP server

No. Kitbench answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kitbench.net/mcp

The last check completed an MCP handshake.

Registry name
net.kitbench/kitbench
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
659 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Exact Japanese text & date tools: char count, business days with JP holidays, era, tax, units.
Listing
From the official MCP registry (active).
Recent checks of Kitbench
CheckedResultHandshake
1 hour agoHandshake completed659 ms
1 day agoHandshake completed489 ms
2 days agoHandshake completed1.29 s
2 days agoHandshake completed594 ms
4 days agoHandshake completed504 ms
7 days agoHandshake completed499 ms
9 days agoHandshake completed493 ms
12 days agoHandshake completed516 ms
14 days agoHandshake completed646 ms
16 days agoHandshake completed565 ms
18 days agoHandshake completed540 ms
20 days agoHandshake completed523 ms
22 days agoHandshake completed574 ms
24 days agoHandshake completed538 ms
25 days agoHandshake completed580 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 Kitbench and makes no claim about it beyond what these checks measured.