Remote MCP · Endpoint

Phoenix operational_context unpaid canary MCP server

No. Phoenix operational_context unpaid canary answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp

The last check completed an MCP handshake.

Registry name
io.github.PhoenixClaw01/operational-context
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
120 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Unpaid qualification-gated operational_context canary. Staging data. No wallet.
Website
https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/public
Repository
https://github.com/PhoenixClaw01/phoenix-collective-os
Listing
From the official MCP registry (active).
Recent checks of Phoenix operational_context unpaid canary
CheckedResultHandshake
1 hour agoHandshake completed120 ms
1 day agoHandshake completed162 ms
2 days agoHandshake completed164 ms
3 days agoHandshake completed106 ms
4 days agoHandshake completed100 ms
5 days agoHandshake completed100 ms
6 days agoHandshake completed134 ms
9 days agoHandshake completed101 ms
11 days agoHandshake completed117 ms
14 days agoHandshake completed107 ms
16 days agoHandshake completed109 ms
18 days agoHandshake completed123 ms
20 days agoHandshake completed106 ms
22 days agoHandshake completed105 ms
24 days agoHandshake completed229 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed139 ms
29 days agoHandshake completed200 ms

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

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 Phoenix operational_context unpaid canary and makes no claim about it beyond what these checks measured.