Remote MCP · Endpoint

TAP Certified MCP server

No. TAP Certified answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://theatlasproject.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.theatlasproject/tap-certified
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
196 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check if an AI agent is certified; list the TAP Registry and certifications. Free, read-only.
Listing
From the official MCP registry (active).
Recent checks of TAP Certified
CheckedResultHandshake
36 minutes agoHandshake completed196 ms
8 days agoHandshake completed99 ms
9 days agoHandshake completed108 ms
11 days agoHandshake completed92 ms
12 days agoHandshake completed97 ms
12 days agoHandshake completed106 ms
14 days agoHandshake completed94 ms
14 days agoHandshake completed101 ms
16 days agoHandshake completed96 ms
19 days agoHandshake completed95 ms
21 days agoHandshake completed103 ms
24 days agoHandshake completed97 ms
26 days agoHandshake completed107 ms
28 days agoHandshake completed89 ms

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

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