Phoenix operational_context unpaid canary

io.github.PhoenixClaw01Published by GitHub account PhoenixClaw01v0.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote canary MCP server with one tool that reports whether a named member-lane business is currently in scope for a bounded operational action.

What you can do
Check operational context: query whether a named member-lane business is currently in scope for a subsequent bounded operational action, using operator-authoritative non-PII identity, category, status, site and timestamps.
When to use it
Only for testing or evaluating a qualification-gated canary that answers a single in-scope question about a named member-lane business. It is not a general-purpose operational system.
Requirements
A remote streamable HTTP endpoint; no authentication, environment variables or headers are declared. The description calls it unpaid, qualification-gated and staging data.
Before you install
The description labels it an unpaid canary using staging data, so results should not be treated as production truth. It is qualification-gated, and no wallet is involved. It returns business identity, category, status, site and timestamps, which are described as non-PII.

Installation

In SourceWeft

  1. Open Phoenix operational_context unpaid canary in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PhoenixClaw01%2Foperational-context/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

1

get_operational_context

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.

Parameterssourcegrant_tokenrequiredbusiness_slugrequiredinvitee_identity

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.