Remote MCP · Endpoint

SingIt x402 MCP server

No. SingIt x402 answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://app.singitai.app/mcp

The last check completed an MCP handshake.

Registry name
app.singitai/singit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
363 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Chat, web search, page reading and market data; owner-set daily and per-request key limits (USDC).
Listing
From the official MCP registry (active).
Recent checks of SingIt x402
CheckedResultHandshake
20 minutes agoHandshake completed363 ms
3 days agoHandshake completed332 ms
14 days agoHandshake completed353 ms
14 days agoHandshake completed506 ms
15 days agoHandshake completed662 ms
16 days agoHandshake completed358 ms
18 days agoHandshake completed362 ms
18 days agoHandshake completed345 ms
19 days agoHandshake completed338 ms
21 days agoHandshake completed355 ms
22 days agoHandshake completed2.79 s
25 days agoHandshake completed407 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 SingIt x402 and makes no claim about it beyond what these checks measured.