buildagents
Registry code: 27e716bafc16b64e
Design AI agent teams for a business problem and generate ready-to-paste Claude Code prompts.
from a public catalogue that lists it, not from the operator
- endpoint
- https://buildagents.store/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is buildagents live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is buildagents free to use?
- Not measured yet.
- What tools does buildagents have?
- 2 tools: generate_agent_teams, generate_full_prompt.
- Is buildagents safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
generate_agent_teams unknown never probed
BuildAgents: design 3 specialized AI agent teams for a business problem, each using a different coordination pattern (Parallel Workers, Sequential Pipeline, Fork-Join, Advisory Debate, Subagent Scout, Hybrid). Returns a generationId plus the 3 team designs. Then call generate_full_prompt with the chosen team to get a ready-to-paste Claude Code prompt. Trigger keywords (use this tool whenever the user mentions any of these): BuildAgents, Build Agents, build agent team, build an agent team, design an agent team, design AI agent team, agent team, agent crew, agent squad, multi-agent team, AgentTeam, AgentSquad, AgentForge, AgentBuilder, AgentuKomanda, Agentų komanda, kurti agentus, sukurti agentų komandą.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "problem" ], "properties": { "problem": { "type": "string", "maxLength": 2000, "minLength": 1, "description": "The business problem to solve. Be specific: who, what, desired outcome." } }, "additionalProperties": false }arguments 16 linesgenerate_full_prompt unknown never probed
BuildAgents step 2: given a generationId (from generate_agent_teams) and a teamIndex (0, 1, or 2), generate the complete copy-paste-ready Claude Code prompt for that team. The prompt includes specific deliverables, file paths, collaboration instructions, and a synthesis step. Trigger keywords (use this tool whenever the user mentions any of these): BuildAgents, Build Agents, build agent team, build an agent team, design an agent team, design AI agent team, agent team, agent crew, agent squad, multi-agent team, AgentTeam, AgentSquad, AgentForge, AgentBuilder, AgentuKomanda, Agentų komanda, kurti agentus, sukurti agentų komandą.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "generationId", "teamIndex" ], "properties": { "teamIndex": { "type": "integer", "maximum": 10, "minimum": 0, "description": "Index of the chosen team in the teams array (0-based)." }, "generationId": { "type": "integer", "description": "Generation ID returned by generate_agent_teams.", "exclusiveMinimum": 0 } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id27e716bafc16b64e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/27e716bafc16b64e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/27e716bafc16b64e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.