Remote MCP · Endpoint

AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor MCP server

No. AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://x402-audit.agentdiet.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.agentdiet/x402-audit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
347 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Audits any remote agent or MCP URL for JSON-RPC compliance, latency SLA, OpenAPI schema, and HTTP.
Website
https://x402-audit.agentdiet.dev/
Repository
https://github.com/robertoyanguas-ops/assay
Listing
From the official MCP registry (active).
Recent checks of AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor
CheckedResultHandshake
17 minutes agoHandshake completed347 ms
9 days agoHandshake completed125 ms
9 days agoHandshake completed99 ms
11 days agoHandshake completed117 ms
12 days agoHandshake completed275 ms
13 days agoHandshake completed124 ms
14 days agoHandshake completed214 ms
14 days agoHandshake completed142 ms
16 days agoHandshake completed285 ms
19 days agoHandshake completed175 ms
21 days agoHandshake completed128 ms
24 days agoHandshake completed1.58 s
26 days agoHandshake completed123 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with AgentDiet A2A, MCP & HTTP 402 Endpoint SLA Compliance Auditor and makes no claim about it beyond what these checks measured.