bft-progress-council-mcp

About bft-progress-council-mcp

Use bft-progress-council-mcp with your agent

claude mcp add --transport http bft-progress-council-mcp https://api.meok.ai/v1/a2a/bft-progress-council

{
  "mcpServers": {
    "bft-progress-council-mcp": {
      "url": "https://api.meok.ai/v1/a2a/bft-progress-council"
    }
  }
}

Frequently asked questions

What is bft-progress-council-mcp?

bft-progress-council-mcp is an MCP (Model Context Protocol) server by csoai-org in the Autonomous Agents category. BFT Progress Council MCP — 5-voter Byzantine council halts agentic loops when no real progress is

How do I connect bft-progress-council-mcp to Claude, Cursor, or another MCP client?

bft-progress-council-mcp is a remote MCP server — add its endpoint (https://api.meok.ai/v1/a2a/bft-progress-council) to your client's MCP configuration (for example with "claude mcp add", or under "mcpServers" in Cursor's mcp.json) and restart the client.

Is bft-progress-council-mcp open source?

Yes — the source code is public at github.com/csoai-org/bft-progress-council-mcp.

Can AI agents pay to use bft-progress-council-mcp?

Not yet through Loomal — bft-progress-council-mcp is listed as a free directory entry. If its maintainer verifies ownership, they can set per-call USDC pricing that agents pay over x402, with settlement on Base.