Remote MCP · Endpoint

mitracore — trust layer for agent work MCP server

No. mitracore — trust layer for agent work answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://rta.lat/mitracore/mcp

The last check completed an MCP handshake.

Registry name
lat.rta/mitracore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
515 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Verify the artifact, meter the cost, enforce the mandate — one call.
Listing
From the official MCP registry (active).
Recent checks of mitracore — trust layer for agent work
CheckedResultHandshake
4 days agoHandshake completed515 ms
4 days agoHandshake completed680 ms
5 days agoHandshake completed867 ms
7 days agoHandshake completed2.12 s
8 days agoHandshake completed1.15 s
9 days agoHandshake completed1.16 s
10 days agoHandshake completed705 ms
11 days agoHandshake completed1.52 s
12 days agoHandshake completed615 ms
15 days agoHandshake completed1.17 s
18 days agoHandshake completed853 ms
20 days agoHandshake completed827 ms

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

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 mitracore — trust layer for agent work and makes no claim about it beyond what these checks measured.