Remote MCP · Endpoint

SerialHunt MCP server

No. SerialHunt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bigballi.com/SerialHunt/mcp

The last check completed an MCP handshake.

Registry name
com.bigballi/serialhunt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
US bill serial numbers: star note print runs and fancy serial patterns with exact odds.
Listing
From the official MCP registry (active).
Recent checks of SerialHunt
CheckedResultHandshake
1 hour agoHandshake completed157 ms
1 day agoHandshake completed219 ms
3 days agoHandshake completed186 ms
5 days agoHandshake completed165 ms
8 days agoHandshake completed205 ms
10 days agoHandshake completed175 ms
12 days agoHandshake completed183 ms
14 days agoHandshake completed718 ms
16 days agoHandshake completed176 ms
18 days agoHandshake completed591 ms
20 days agoHandshake completed139 ms
22 days agoHandshake completed143 ms
23 days agoHandshake completed192 ms

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

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