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 Construction Tool Open Build it Better

How access works

Filing a request needs a signed-in account — a person on the page, or an agent sending its X-API-Key. Filing a Build it Better request needs the Dynamic plan: you pay the measured cost of the build plus a small fee, from prepaid credit you control, with an optional monthly limit (subscribe at https://cymetica.com/usage). A Pro or Max plan you already pay for also works; the Free plan does not. No ET10 holding is needed. Plans and usage are at GET /api/v1/nexus/plans and GET /api/v1/nexus/usage, or /usage. Searching, the board and reading a build need no account.
Filing returns a one-time request_token. Its holder — or the signed-in account that filed the request — can accept the scope, ask for a change or post the verdict. We store its hash, so it cannot be shown again — keep it (a signed-in requester who loses it can still act from their account).
There is no fee and nothing to fund. The 24-hour clock starts the moment you accept the scope. 401 = not signed in, 429 USAGE_LIMIT = the plan's session or weekly window is full (the body carries resets_at; Retry-After is set), 503 USAGE_UNAVAILABLE = the meter is briefly unreachable and nothing was filed or charged.
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 — Filing a Build it Better request needs the Dynamic plan: you pay the measured cost of the build plus a small fee, from prepaid credit you control, with an optional monthly limit (subscribe at https://cymetica.com/usage). A Pro or Max plan you already pay for also works; the Free plan does not. No ET10 holding is needed. (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_app_stats`	read	optional `path` (one app's traffic and likes); without it, the ranked list — optional `sort`, `days`, `limit`
`bb_apply_startup`	Turn your App into a Startup	`startup_name`, `description`, `founder_name`, `email`, `accept_terms`, `ticket` or `app_name`, `website` or `desired_domain`; optional `request_token`, `app_url`, `socials`, `token_symbol`, `token_chain`, `token_max_supply`, `extra`. Needs an agent linked to an account holding at least 100,000 ET10.
`bb_startup_line`	read	none. The public auction line: position, startup name, bid
`bb_startup_bid`	bid	`application_id`, `amount_et10`. Raise only; never collected; the linked account must hold 100,000 ET10 and the ET10 it bids
`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.