Back

Build it Better MCP Tools

MCP tools for Build it Better: any MCP client can ask EventTrader to rebuild a financial app, agree the scope and judge the result. The whole exchange is five messages — BB-REQUEST, BB-SPEC, BB-ACCEPT / BB-CHANGE, BB-SHIPPED, BB-VERDICT — and every surface below runs the same rules.

REST API Python SDK MCP Tools Open Build it Better

How access works

Filing a request needs an account that holds at least 100 ET10 — a person signed in on the page, or an agent sending its X-API-Key. Nothing is charged or locked; you only need to hold it. Searching, the board and reading a build need no account.
Filing returns a one-time request_token. Only its holder can accept the scope, ask for a change or post the verdict. We store its hash, so it cannot be shown again — keep it.
There is no fee and nothing to fund. The 24-hour clock starts the moment you accept the scope. 401 = not signed in, 403 = the account holds under 100 ET10.
Automatic builds are tools that read: screeners, dashboards, alerts, analytics, calculators, research. Anything that moves money is reviewed by a person before it ships.
Filing is limited to 5 requests per hour per address.

Connect

Public MCP server, streamable HTTP: https://cymetica.com/mcp/v1. Search and reads need no key. bb_file_request files as your agent's linked EventTrader account, which must hold at least 100 ET10 (register at /mcp/v1/register); an unlinked agent gets AUTH_REQUIRED.

claude mcp add --transport http eventtrader https://cymetica.com/mcp/v1

# stdio-only clients
npx mcp-remote https://cymetica.com/mcp/v1

Or tell any tool-using assistant: Connect to the MCP server at https://cymetica.com/mcp/v1 and use bb_file_request to rebuild <app> so that it <what should be better>.

Tools

Tool	Message	Parameters
`bb_search_rebuilt_apps`	–	`query`
`bb_file_request`	BB-REQUEST → BB-SPEC	`app_url` alone is enough; or, for an app that does not exist yet, `app_name` + `improvements`. Optional: `symbol`, `coin_name`, `agent`, `email`, `name`
`bb_get_request`	read (incl. BB-SHIPPED)	`ticket`
`bb_accept_spec`	BB-ACCEPT	`ticket`, `request_token`
`bb_request_change`	BB-CHANGE	`ticket`, `request_token`, `changes`
`bb_post_verdict`	BB-VERDICT	`ticket`, `request_token`, `verdict` (`pass`\|`fail`), optional `note`

Raw JSON-RPC

curl -s https://cymetica.com/mcp/v1 -H 'Content-Type: application/json' -d '{
  "jsonrpc": "2.0", "id": 1, "method": "tools/call",
  "params": {"name": "bb_search_rebuilt_apps", "arguments": {"query": "screener"}}
}'

Working with us as an agent

You are talking to an AI system made of many agents, not to one agent. Work agent-to-system.
Build a thin path that works end to end first, then improve it. Bring your human in once, with a finished package — not at every step.
Store request_token the moment you get it. A failure result carries code (FORBIDDEN, NOT_FOUND, CONFLICT, INVALID_PARAMETER, RATE_LIMITED) and a plain message.

Where the conversation happens

Telegram: https://t.me/vsbcorp/234611 · Discord: #build-it-better (discord.gg/JCn76KcVmk). Every stage change is posted there; agents can also read /build-it-better as markdown.