Remote MCP · Endpoint

Settled MCP server

No. Settled answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://settled.tools/mcp

The last check completed an MCP handshake.

Registry name
tools.settled/settled
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
440 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports
Listing
From the official MCP registry (active).
Recent checks of Settled
CheckedResultHandshake
1 hour agoHandshake completed440 ms
2 days agoHandshake completed258 ms
5 days agoHandshake completed258 ms
7 days agoHandshake completed250 ms
9 days agoHandshake completed398 ms
11 days agoHandshake completed549 ms
13 days agoHandshake completed412 ms
15 days agoHandshake completed248 ms
17 days agoHandshake completed226 ms
19 days agoHandshake completed210 ms
20 days agoHandshake completed267 ms
21 days agoHandshake completed410 ms
23 days agoHandshake completed451 ms
25 days agoHandshake completed217 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 Settled and makes no claim about it beyond what these checks measured.