Remote MCP · Endpoint

io.github.mapizarro1/foragex402 MCP server

Yes, as of 49 minutes ago: the connection was refused or dropped.

DownLast checked 49 minutes ago

Server URL

https://foragex402.tablint.dev/mcp

The last check failed: the connection was refused or dropped.

Registry name
io.github.mapizarro1/foragex402
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Meta-search MCP for x402 agent-payable services -- find paid APIs across every registry.
Repository
https://github.com/mapizarro1/foragex402
Listing
From the official MCP registry (active).
Recent checks of io.github.mapizarro1/foragex402
CheckedResultHandshake
49 minutes agoFailed - the connection was refused or dropped—
1 hour agoFailed - the connection was refused or dropped—
1 day agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.mapizarro1/foragex402 and makes no claim about it beyond what these checks measured.