Remote MCP · Endpoint

xytara MCP Executor MCP server

No. xytara MCP Executor answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://xytara-mcp-executor.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
com.naxytra/xytara-mcp-executor
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
165 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Pay-per-call MCP tools and signed on-chain attestations: 20 free/day, then x402 or a spend key.
Listing
From the official MCP registry (active).
Recent checks of xytara MCP Executor
CheckedResultHandshake
1 hour agoHandshake completed165 ms
18 hours agoHandshake completed156 ms
2 days agoHandshake completed276 ms
3 days agoHandshake completed260 ms
4 days agoHandshake completed184 ms
5 days agoHandshake completed146 ms
6 days agoHandshake completed276 ms
7 days agoHandshake completed295 ms
10 days agoHandshake completed274 ms
13 days agoHandshake completed169 ms
15 days agoHandshake completed137 ms
17 days agoHandshake completed132 ms
19 days agoHandshake completed122 ms
21 days agoHandshake completed144 ms
23 days agoHandshake completed133 ms
25 days agoHandshake completed120 ms
27 days agoHandshake completed270 ms
28 days agoHandshake completed133 ms
29 days agoHandshake completed246 ms

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

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