Remote MCP · Endpoint

BUMIT MCP server

No. BUMIT answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://bumit.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.bumit/verify-business
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.54 s
Tools exposed
3 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Swiss business verification with per-check source provenance and evidence freshness.
Listing
From the official MCP registry (active).
Recent checks of BUMIT
CheckedResultHandshake
7 hours agoHandshake completed1.54 s
4 days agoHandshake completed1.26 s
14 days agoHandshake completed1.50 s
15 days agoHandshake completed2.76 s
15 days agoHandshake completed1.65 s
17 days agoHandshake completed940 ms
18 days agoHandshake completed2.16 s
19 days agoHandshake completed1.64 s
20 days agoHandshake completed1.40 s
21 days agoHandshake completed2.01 s
23 days agoFailed - the request timed out—
26 days agoHandshake completed2.55 s
28 days agoHandshake completed1.59 s

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

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