Remote MCP · Endpoint

fourzerotwo MCP server

No. fourzerotwo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fourzerotwo.si/mcp

The last check completed an MCP handshake.

Registry name
si.fourzerotwo/data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
415 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
400+ data APIs for agents: UK companies, property, trade, tenders, recalls, sanctions. Free tier
Listing
From the official MCP registry (active).
Recent checks of fourzerotwo
CheckedResultHandshake
1 hour agoHandshake completed415 ms
1 day agoHandshake completed490 ms
2 days agoHandshake completed895 ms
3 days agoHandshake completed440 ms
4 days agoHandshake completed398 ms
5 days agoHandshake completed217 ms
6 days agoHandshake completed560 ms
9 days agoHandshake completed400 ms
11 days agoHandshake completed382 ms
14 days agoHandshake completed446 ms
16 days agoHandshake completed380 ms
18 days agoHandshake completed465 ms
20 days agoHandshake completed400 ms
22 days agoHandshake completed416 ms
24 days agoHandshake completed138 ms

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

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