Remote MCP · Endpoint

Atomadic MCP MCP server

No. Atomadic MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.atomadic.tech/mcp

The last check completed an MCP handshake.

Registry name
tech.atomadic/atomadic
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
59 ms
Tools exposed
68 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance.
Listing
From the official MCP registry (active).
Recent checks of Atomadic MCP
CheckedResultHandshake
1 hour agoHandshake completed59 ms
9 days agoHandshake completed127 ms
9 days agoHandshake completed167 ms
11 days agoHandshake completed157 ms
12 days agoHandshake completed69 ms
13 days agoHandshake completed67 ms
14 days agoHandshake completed82 ms
14 days agoHandshake completed322 ms
16 days agoHandshake completed96 ms
19 days agoHandshake completed299 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed78 ms
26 days agoHandshake completed141 ms
28 days agoHandshake completed236 ms

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

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