Remote MCP · Endpoint

io.github.normancomics/phantomoperator MCP server

No. io.github.normancomics/phantomoperator answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://freysaai.freysa.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.normancomics/phantomoperator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
11 tools
Uptime, last 30 days
60.0% from 10 checks
Described by its publisher as
Authorized privacy and exposure checks for people and agents; USDC on Base via x402.
Listing
From the official MCP registry (active).
Recent checks of io.github.normancomics/phantomoperator
CheckedResultHandshake
3 days agoHandshake completed33 ms
6 days agoHandshake completed41 ms
16 days agoHandshake completed37 ms
17 days agoHandshake completed33 ms
18 days agoHandshake completed34 ms
19 days agoFailed - the request timed out—
21 days agoFailed - the request timed out—
21 days agoFailed - the request timed out—
22 days agoFailed - the request timed out—
24 days agoHandshake completed31 ms

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

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 io.github.normancomics/phantomoperator and makes no claim about it beyond what these checks measured.