Bay Run
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Bay RunDiscover and serve an embedding model for my RAG pipeline on legal docs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Bay Run
Bay Run is a free-at-launch, OpenAI-compatible REST and MCP service for small-model inference at the canonical origin: https://run.huggingbay.xyz.
Free launch: 30 seconds
The launch tier is free. Mint a demo bearer with a form-encoded client_credentials request, then call the API. The published guardrails are 60 requests/minute and 1,500/day; demo bearers expire after 24 hours.
Start with the live, copy-paste quickstart: https://run.huggingbay.xyz/quickstart.
The repository’s standalone demo is a small classify → signed receipt → verify flow:
python examples/bakeoff.pyimport json
from urllib.parse import urlencode
from urllib.request import Request, urlopen
BASE = "https://run.huggingbay.xyz"
def post(path, body, headers):
request = Request(BASE + path, data=json.dumps(body).encode(), headers=headers)
return json.load(urlopen(request))
token_request = Request(
BASE + "/oauth/token",
data=urlencode({"grant_type": "client_credentials"}).encode(),
headers={"Content-Type": "application/x-www-form-urlencoded"},
)
token = json.load(urlopen(token_request))["access_token"]
headers = {"Authorization": f"Bearer {token}", "Content-Type": "application/json"}
result = post("/v1/classify", {"input": "The setup was quick and clear.", "model": "auto"}, headers)
receipt = result["provenance_receipt"]
verified = post("/v1/provenance/verify", {"receipt": receipt}, headers)
assert verified.get("valid") is True or verified.get("receipt_valid") is True
print(result["labels"][0])
print("receipt verified")This demo uses the real /v1/classify and provenance-verification surfaces; it does not invent a bake-off endpoint.
Related MCP server: spiderswitch
REST and SDKs
The REST surface includes OpenAI-compatible chat/completions (including SSE streaming and tools), embeddings, reranking, classification, summarization, RAG, calculation, JSON validation, and memory. The thin SDKs live beside this checkout during build/test:
pip install -e ../bayrun-sdk/python
npm install ../bayrun-sdk/jsfrom bayrun import Client
c = Client()
answer = c.classify("A helpful result.")
stream = c.chat([{"role": "user", "content": "Say hello."}], stream=True)import { Client } from "bayrun";
const c = new Client();
const answer = await c.classify("A helpful result.");
const stream = await c.chat([{ role: "user", content: "Say hello." }], { stream: true });Durable remember/recall/forget memory is owner-delegated and is not authorized for the shared demo bearer. Use a purpose-specific developer key or a client registered with token_endpoint_auth_method=client_secret_post.
Adapter snippets for OpenAI Python, Vercel AI SDK, LangChain, and LlamaIndex are in docs/integrations.md.
MCP: exactly three tools
Point an MCP client at https://run.huggingbay.xyz/mcp/. The live server exposes exactly:
get_task_quoterun_taskverify_result
Token and request-shape details are kept in the live quickstart so the copy-paste contract stays current.
Trust and data policy
REST results carry signed provenance receipts, and task execution returns a signed receipt that can be checked with the verification surface. Read the receipt semantics and the live verification request at https://run.huggingbay.xyz/quickstart.
Before sending data, read the canonical policy: https://run.huggingbay.xyz/.well-known/data-policy.json. The published policy says Bay Run does not train on inputs.
Hugging Face drop-in mirror catalog
Hugging Bay’s mirror catalog is available at https://huggingbay.xyz. For Hugging Face Hub clients that honor HF_ENDPOINT, point the client at the mirror origin:
export HF_ENDPOINT=https://huggingbay.xyzThe catalog currently lists 893+ mirrored models. Check the mirror’s current serving status before relying on a specific model or repository path.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseAqualityFmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.53
- AlicenseNot gradedqualityBmaintenanceMCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.MIT
- AlicenseAqualityBmaintenanceA local MCP bridge that registers multiple AI API endpoints, enabling agents to automatically discover and route to models based on capabilities like chat, vision, reasoning, embedding, image generation, TTS, STT, and rerank.69MIT
Related MCP Connectors
Connect MCP clients to 2,000+ AI models without managing provider API keys.
Hosted MCP server for LLM cost estimation, model comparison, and budget-aware routing.
Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/barneywohl/bay-run'
If you have feedback or need assistance with the MCP directory API, please join our Discord server