Remote MCP · Endpoint

Everyday agent tools MCP server

No. Everyday agent tools answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fourzerotwo.si/mcp/v/tools

The last check completed an MCP handshake.

Registry name
si.fourzerotwo/tools
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
411 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Time zones and world business days, VAT rates and maths, currency conversion, UK business days…
Listing
From the official MCP registry (active).
Recent checks of Everyday agent tools
CheckedResultHandshake
1 hour agoHandshake completed411 ms
1 day agoHandshake completed433 ms
2 days agoHandshake completed386 ms
3 days agoHandshake completed408 ms
4 days agoHandshake completed373 ms
5 days agoHandshake completed408 ms
6 days agoHandshake completed472 ms
9 days agoHandshake completed231 ms
11 days agoHandshake completed206 ms
14 days agoHandshake completed534 ms
16 days agoHandshake completed375 ms
18 days agoHandshake completed306 ms
20 days agoHandshake completed371 ms
22 days agoHandshake completed200 ms
24 days agoHandshake completed175 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 Everyday agent tools and makes no claim about it beyond what these checks measured.