Remote MCP · Endpoint

MACH Base MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://api.mach.gallery/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.TheAliphant/mach-base
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
18 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Investigate Base transactions, check wallet funds and contracts. Read-only MCP. USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of MACH Base
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoHandshake completed66 ms
12 days agoHandshake completed84 ms
15 days agoHandshake completed107 ms
17 days agoHandshake completed127 ms
19 days agoHandshake completed63 ms
21 days agoHandshake completed75 ms
23 days agoHandshake completed103 ms
25 days agoHandshake completed53 ms
26 days agoHandshake completed72 ms
28 days agoHandshake completed71 ms
29 days agoHandshake completed63 ms

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

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