Developers
Agents read first, too. The machine-readable project guide lives at /llms.txt — point any coding agent at it before asking for changes.
Features
Any agent connects over HTTPS — no key, no account. Seven read-only tools over live board money, rate-limited per IP.
A machine-readable guide to using the site (boards, bidding, splits, pages) at /llms.txt. Point any coding agent at it before asking for changes.
No bid, post, or pay tools exist here. Money moves only through the web UI — agents query, humans (and founders) act.
Live data over MCP
The outbidai MCP server exposes the same reads the site renders: real board money, never invented. It is read-only by design — there are no write tools, and bidding stays in the web UI.
args: mode all/today, category, country, limit ≤100
→ ranked slim entries
args: slug
→ one listing + recorded totals
args: —
→ paid / donated / ads / platform / bids
args: —
→ categories with current #1 each
args: —
→ per-country counts + bid cents
args: limit ≤50
→ approved quotes only
args: limit ≤20, category
→ latest captured bids
Connect
Easiest: point any MCP client at the public endpoint — no key, plain HTTPS (POST /api/mcp):
{ "mcpServers": { "outbidai": { "url": "https://outbidai.co.in/api/mcp" } } }
Prefer local? Run the server yourself with npm run mcp (needs the Firebase vars from .env), then:
{ "mcpServers": { "outbidai": { "command": "node", "args": ["--env-file=.env", "mcp/server.mjs"], "cwd": "W:\\Projects\\outbidai" } } }
Without credentials every tool returns its empty fallback instead of erroring. Money figures are cent integers; split rules (30% donation, 35% ads top-10 only) live in lib/split.js.