Remote MCP · Endpoint

Tracea MCP server

No. Tracea answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.tracea.online/mcp

The last check completed an MCP handshake.

Registry name
io.github.Chriscorp/tracea
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
307 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.
Listing
From the official MCP registry (active).
Recent checks of Tracea
CheckedResultHandshake
1 hour agoHandshake completed307 ms
2 days agoHandshake completed291 ms
4 days agoHandshake completed264 ms
5 days agoHandshake completed284 ms
7 days agoHandshake completed387 ms
8 days agoHandshake completed286 ms
9 days agoHandshake completed275 ms
12 days agoHandshake completed295 ms
13 days agoHandshake completed297 ms
15 days agoHandshake completed276 ms
16 days agoHandshake completed267 ms
18 days agoHandshake completed281 ms
19 days agoHandshake completed270 ms
20 days agoHandshake completed277 ms
20 days agoHandshake completed284 ms
21 days agoHandshake completed277 ms
22 days agoHandshake completed1.15 s

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

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