All servers · Crypto & blockchain

Phoenix operational_context unpaid canary

io.github.PhoenixClaw01/operational-context · v0.1.0

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-03-26
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	tools
Tool definitions	1 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

Description written by the publisher, not verified

Unpaid qualification-gated operational_context canary. Staging data. No wallet.

Connect

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

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

{
  "mcpServers": {
    "operational-context": {
      "url": "https://phoenix-collective-os-isolated-validation-phoenix-collective.vercel.app/api/mcp/operational-context/mcp"
    }
  }
}

Tools as reported by the server

get_operational_context
Whether that named member-lane business is currently in-scope for a subsequent bounded operational action, using only operator-authoritative non-PII identity, category, status, site, and timestamps.

Repository · Website · JSON · Text for agents · Registry updated 2026-08-17