Programmatic access to opportunities, strategies, and bet logging.
Query signals, log bets, and deploy strategies by talking to Claude, Cursor, or any MCP-compatible agent.
Generate a key in Settings → API Keys, then paste it below to generate ready-to-use install snippets.
Snippets use YOUR_API_KEY until you paste a key.
Click below. Cursor will open and prompt you to confirm.
Add to CursorPaste your API key above to enable.Run this in your terminal:
claude mcp add --transport http ev-blacksite https://evblacksite.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"NanoClaw is a Claude SDK wrapper — it picks up whatever MCP servers claude mcp add has already registered, so the one-liner above covers it too.
Claude Desktop only speaks stdio, so you need mcp-remote (an npx shim) to bridge it to our HTTP endpoint. Requires Node.js installed.
claude_desktop_config.json. Open that file in a text editor.~/Library/Application Support/Claude/claude_desktop_config.jsonev-blacksite entry below into mcpServers (create the object if it doesn't exist).{
"mcpServers": {
"ev-blacksite": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://evblacksite.com/api/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}Agents without native MCP can still use ev-blacksite — if the agent can run curl, it can speak MCP. Store the key in your platform's credential system (or an env var) and tell the agent to call the endpoint directly via JSON-RPC over SSE. Your real API key stays out of chat.
I want to use the EV Blacksite MCP server so you can help me with my betting account. Your platform (e.g. OpenClaw, or a bare LLM API with shell tools) doesn't have native MCP, but that's fine — the server is plain HTTP and you can reach it with curl.
Please do the following:
1. Pick a location in your workspace for the credentials. If your platform has a secrets directory (e.g. a ".secrets/" folder, a keyring command, or an env file), use that. Otherwise create a file outside version control (e.g. "agents/.secrets/ev-blacksite.json"). Write:
{
"url": "https://evblacksite.com/api/mcp",
"authorization": "Bearer YOUR_API_KEY"
}
Keep YOUR_API_KEY as a literal placeholder — I'll replace it in the file myself. Don't ask me to paste the key into this chat.
2. Tell me the exact file path you just created so I can open it and swap in my real key.
3. Once I confirm the key is in place, test the connection by calling tools/list via curl. Every request must include these three headers:
- Authorization: Bearer <the stored key>
- Content-Type: application/json
- Accept: application/json, text/event-stream
The body is JSON-RPC 2.0. Example:
curl -s -X POST https://evblacksite.com/api/mcp \
-H "Authorization: Bearer <key>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
The response is SSE ("event: message\ndata: {...}"). Parse the JSON after "data: " to get the result. Report back the list of tools you see.
4. From then on, when I ask about signals, bets, strategies, sizing, or my bankroll, make a JSON-RPC "tools/call" request with the matching tool name and arguments. Before you start guessing values, call get_docs(slug) to pull reference content — the server tells you what slugs it supports at initialize time.
5. Do not cache tool results across sessions; signals expire, strategies change, rate limits reset.