Add betonit MCP server

[jiftuq]

Summary

• Adds betonit — a 1v1 betting protocol on Base chain where AI agents can create, take, and settle USDC bets
• Published on npm as betonit-cli
• MCP server exposes 7 tools: list_bets, get_bet, create_bet, take_bet, vote_winner, propose_settlement, respond_settlement

MCP config

{
  "mcpServers": {
    "betonit": {
      "command": "npx",
      "args": ["betonit-cli", "mcp"],
      "env": { "BETONIT_API_KEY": "your-key" }
    }
  }
}

Links

• Website: https://betonit.site
• GitHub: https://github.com/jiftuq/betonit
• npm: https://www.npmjs.com/package/betonit-cli
• OpenAPI spec: https://industrious-bee-858.convex.site/.well-known/openapi.json

[jiftuq]

The CI failure appears to be a permissions issue in the workflow, not related to my PR changes.

The check-readme-only job fails at github.rest.pulls.listFiles() with HttpError: Resource not accessible by integration. It looks like the workflow is missing contents: read permission — it only declares pull-requests: write.

Suggested fix for .github/workflows/check-readme-only.yml:

jobs:
  check-readme-only:
    permissions:
      contents: read        # needed for pulls.listFiles()
      pull-requests: write

Same for the handle-confirmation job which calls listLabelsOnIssue().

My PR only adds one line to README.md.

[olaservo]

Thanks for contributing to the MCP servers repo!

We've retired the third-party server list from the README in favor of the MCP Registry — see #3950 for context. The Official Integrations and Community Servers sections no longer exist in the README, so this PR no longer has a target.

Going forward, please publish your server to the MCP Registry using the quickstart guide:
https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx

That's where server discovery now happens. Thanks for building on MCP!

---

Note: I'm working through the backlog with help from Claude Code to give everyone a prompt response.