Remote MCP · Endpoint

HumMatch MCP server

No. HumMatch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://hummatch.me/api/mcp

The last check completed an MCP handshake.

Registry name
me.hummatch/hummatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Match singers to songs by vocal range: score fit, karaoke difficulty, and voice type.
Listing
From the official MCP registry (active).
Recent checks of HumMatch
CheckedResultHandshake
1 hour agoHandshake completed147 ms
2 days agoHandshake completed265 ms
4 days agoHandshake completed316 ms
5 days agoHandshake completed299 ms
7 days agoHandshake completed154 ms
8 days agoHandshake completed150 ms
9 days agoHandshake completed120 ms
12 days agoHandshake completed314 ms
13 days agoHandshake completed309 ms
15 days agoHandshake completed260 ms
17 days agoHandshake completed117 ms
18 days agoHandshake completed105 ms
19 days agoHandshake completed113 ms
20 days agoHandshake completed118 ms
21 days agoHandshake completed106 ms
21 days agoHandshake completed161 ms
23 days agoHandshake completed116 ms

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

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