English Français العربية

Bay Run

Official registry AI and agents

Free OpenAI-compatible inference with signed provenance receipts and 3 focused MCP tools.

Source code Website Documentation

What can you do with Bay Run?

  • coprocessor — the primary bounded Guard-first call over user_text and optional documents.
  • run_pin — the direct alias for one of the four canonical Pins, using its published {pin_id,input} shape.
  • solve_task — the open-ended fallback when no canonical Pin matches; provide task_description and input.
  • OpenAPI
  • advanced MCP tools
  • full LLM reference
  • SDK and framework integrations

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http bay-run 'https://run.huggingbay.xyz/mcp/' --header 'Authorization: <Mint the bounded launch bearer using the form-encoded client_credentials request shown at https://run.huggingbay.xyz/quickstart, then send Authorization: Bearer <token>.>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "bay-run": {
            "type": "http",
            "url": "https://run.huggingbay.xyz/mcp/",
            "headers": {
                "Authorization": "<Mint the bounded launch bearer using the form-encoded client_credentials request shown at https://run.huggingbay.xyz/quickstart, then send Authorization: Bearer <token>.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Bay Run
  2. Quickstart: connect to MCP
  3. Default MCP tools
  4. Trust and data policy
  5. Hugging Bay mirror catalog

Bay Run

Bay Run is the decision and execution layer for durable specialist Pins at the canonical origin: https://run.huggingbay.xyz.

The default MCP front door is exactly three tools, in this order: coprocessor, run_pin, solve_task.

Quickstart: connect to MCP

Use the canonical Streamable HTTP MCP endpoint: https://run.huggingbay.xyz/mcp/. The live copy-paste auth and request contract is kept at https://run.huggingbay.xyz/quickstart.

Mint a resource-bound demo bearer, then make the primary Guard-first call:

BASE=https://run.huggingbay.xyz
TOKEN=$(curl -fsS -X POST "$BASE/oauth/token" \
  -H 'Content-Type: application/json' \
  -d '{"grant_type":"urn:bay-run:grant-type:demo","scope":"mcp:demo","resource":"https://run.huggingbay.xyz/mcp/"}' \
  | python3 -c 'import json,sys; print(json.load(sys.stdin)["access_token"])')

curl -fsS -X POST "$BASE/mcp/" \
  -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"coprocessor","arguments":{"user_text":"<untrusted request>"}}}'

coprocessor runs the canonical Guard first and never generates text or executes tools. Add documents when retrieved chunks need bounded post-SAFE reranking. Read its action and evidence before deciding whether a caller-owned generation or tool call may continue.

Default MCP tools

Point an MCP client at https://run.huggingbay.xyz/mcp/. The public default surface is:

  • coprocessor — the primary bounded Guard-first call over user_text and optional documents.
  • run_pin — the direct alias for one of the four canonical Pins, using its published {pin_id,input} shape.
  • solve_task — the open-ended fallback when no canonical Pin matches; provide task_description and input.

Advanced compatibility capabilities remain available through explicit live references:

Trust and data policy

Read the canonical data policy before sending input. The live quickstart documents receipt semantics, 401 recovery, and the published limits; do not infer capabilities from advanced routes.

Hugging Bay mirror catalog

Hugging Bay’s mirror catalog is available at https://huggingbay.xyz. Use each artifact's published download plan for the currently admitted files. A drop-in HF_ENDPOINT compatibility origin is not part of the public contract yet, so this repository does not advertise one prematurely.

For current catalog and serving information, use the generated Bay Run status snapshot. Mirror counts and family breakdowns are intentionally not copied here because they change.

Frequently asked questions

What is Bay Run?

Free OpenAI-compatible inference with signed provenance receipts and 3 focused MCP tools.

How do I install Bay Run?

It runs as a remote server. In Claude Code: claude mcp add --transport http bay-run 'https://run.huggingbay.xyz/mcp/' --header 'Authorization: <Mint the bounded launch bearer using the form-encoded client_credentials request shown at https://run.huggingbay.xyz/quickstart, then send Authorization: Bearer <token>.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Bay Run need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Bay Run open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Bay Run?

It is published by barneywohl. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.