_ registry / mcp http-sse · checked 2h ago

council-ai

https://mcp.council-ai.app

Registry code: d40a0add39745378

api record

Multi-LLM council MCP: parallel frontier models, consensus scoring, verdict-first code review

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.council-ai.app/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 it live, free and safe measured by this hub
Is council-ai live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is council-ai free to use?
Yes — the hub reached it with no key and no payment.
What tools does council-ai have?
10 tools: library_delete, library_upload, council_review, council_query, council_result, library_list, library_search, council_query_with_rag, ….
Is council-ai 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.
reachable
live
uptime, 30 days
99.1%

90 days 99.2%· all time 99.2%

latency
255ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 491 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • ask several llms the same question
  • get a consensus answer from models
  • review code with multiple models
  • search a personal document library
  • upload a document for retrieval
takes → gives
text, code, documents → text, data
tools
8 reads2 changes data
note
resells another provider
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 10 tools
10 never probed 0 of 10 classified

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.

  • library_delete changes data unknown never probed

    Permanently delete a document from the user's Council RAG library — the record, every indexed chunk, AND the stored file are removed. This cannot be undone; re-adding the document requires uploading it again. Get document IDs from library_list. Use when the user asks to remove a document or when the 200-document library cap blocks an upload. Confirm with the user before deleting anything they did not explicitly name. No model call, no budget consumption.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "documentId"
      ],
      "properties": {
        "documentId": {
          "type": "string",
          "minLength": 1,
          "description": "ID of the document to delete, as returned by library_list or library_upload."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • library_upload changes data unknown never probed

    Upload a document into the user's Council RAG library so future council_query_with_rag and library_search calls can retrieve it. Accepts PDF, Word (docx), text, and markdown files as base64 — images are not supported. Max 10MB per file via MCP (the web library at https://council-ai.app/settings?tab=library takes up to 50MB); libraries hold up to 200 documents. Ingestion (chunking + embedding) runs in the background: the returned document starts in "pending" status — check library_list for it to reach "ready" before querying against it. No model call, no budget consumption.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "filename",
        "contentBase64"
      ],
      "properties": {
        "tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Free-form tags to attach to the document, e.g. [\"contracts\", \"2026\"]."
        },
        "filename": {
          "type": "string",
          "maxLength": 512,
          "minLength": 1,
          "description": "Original filename including extension — the extension drives type detection. Example: \"vendor-contract-2026.pdf\"."
        },
        "mimeType": {
          "type": "string",
          "maxLength": 255,
          "description": "MIME type, e.g. \"application/pdf\". Optional — the backend verifies the real type from the file's magic bytes regardless."
        },
        "projectId": {
          "type": "string",
          "description": "Council project workspace to file the document under. Omit for the general library."
        },
        "contentBase64": {
          "type": "string",
          "minLength": 1,
          "description": "The file's raw bytes, base64-encoded (standard alphabet, no data: URI prefix). For a plain-text or markdown document, base64-encode the UTF-8 text."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • council_review reads unknown 13h ago

    Multi-model code review. Sends a unified diff (or code snippet) to multiple frontier AI models from different labs in parallel, each acting as an independent reviewer with an explicit verdict + findings contract. Returns a verdict-first synthesis: overall SHIP/NO-SHIP, consensus score, confirmed findings (flagged by 2+ models), then dissents (single-model findings with reasoning), then each reviewer's verdict. Diffs are capped at 14,000 characters — split larger changes by file or hunk and call once per chunk. Bills against the user's Council AI monthly budget like any council query.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "diff"
      ],
      "properties": {
        "diff": {
          "type": "string",
          "minLength": 1,
          "description": "The unified diff (git diff output) or code snippet to review. Max 14,000 characters — if your diff is larger, split it by file or hunk and review each part separately. Example: the output of `git diff HEAD~1`."
        },
        "async": {
          "type": "boolean",
          "default": false,
          "description": "When true, return {queryId, status:\"running\"} immediately and fetch the finished review with council_result. Use when your MCP client enforces a fixed tool-call timeout, or with 4+ reviewers — async runs also give slow reasoning models a much larger time budget before they are cut off."
        },
        "focus": {
          "enum": [
            "bugs",
            "security",
            "performance",
            "architecture",
            "all"
          ],
          "type": "string",
          "default": "all",
          "description": "Review focus: \"bugs\" (correctness), \"security\", \"performance\", \"architecture\", or \"all\" (default — full review, bugs prioritized)."
        },
        "models": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "minItems": 2,
          "description": "Model IDs to include as reviewers (2-10). Defaults to the user's preferred council. Use council_models to list available IDs."
        },
        "context": {
          "type": "string",
          "maxLength": 3000,
          "description": "What the change is supposed to do: intent, constraints, related files or invariants reviewers cannot see from the diff alone. Improves signal, reduces false positives."
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • council_query reads unknown 16h ago

    Send a prompt to a council of frontier AI models across 9 labs (Anthropic, OpenAI, Google, xAI, DeepSeek, Qwen, Mistral, Moonshot, z.ai). Returns each model's independent response plus a moderator-synthesized consensus answer with an agreement score and the key point of disagreement, when one exists. Use when a single-model answer might hallucinate or when verification across labs matters (research, contracts, architecture, legal, medical, code review). Adaptive-cost pattern: for a quick check, call with 2-3 models; if consensusScore comes back low (or keyDisagreement matters to the decision), escalate by re-running with more models — easy questions stay cheap, disputed ones get more compute. TIMEOUTS: a full council can run for minutes. If your MCP client has a fixed tool-call timeout, set async=true — you get a queryId back immediately and fetch the finished result with council_result. Call council_models first to pick specific model IDs, and council_usage to check remaining budget. Bills against the user's Council AI monthly budget.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prompt"
      ],
      "properties": {
        "mode": {
          "enum": [
            "independent",
            "sequential"
          ],
          "type": "string",
          "default": "independent",
          "description": "Cross-model visibility. 'independent' (default): all models answer in parallel, blind to each other — best for unbiased comparison; the synthesis reconciles them. 'sequential': models answer one at a time and each later model sees the earlier answers, debate-style — takes the SUM of per-model latencies instead of the max, so strongly consider async=true with it."
        },
        "async": {
          "type": "boolean",
          "default": false,
          "description": "When true, return {queryId, status:\"running\"} immediately instead of waiting for the council. Fetch the finished result with council_result. Use whenever your MCP client enforces a fixed tool-call timeout (a full council typically runs 1-3 minutes) or when querying 4+ models."
        },
        "models": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "minItems": 2,
          "description": "Model IDs to include (2-10). Defaults to a cross-lab flagship council. Use council_models to list available IDs. Example: [\"claude-fable-5.1\", \"gpt-5.6-sol\", \"gemini-3.8-flash\"]"
        },
        "prompt": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 1,
          "description": "The question or task to send to the council. Include all needed context — every query is stateless. Example: \"Is optimistic locking or a distributed lock the better fit for this checkout flow? [paste flow description]\""
        },
        "synthesize": {
          "type": "boolean",
          "default": true,
          "description": "When true (default), include the moderator synthesis + consensus score. Set false to get only the raw per-model responses (faster, cheaper)."
        },
        "synthesisDirective": {
          "type": "string",
          "maxLength": 8000,
          "minLength": 1,
          "description": "Optional instructions for the moderator that synthesizes the council's answers. The council models never see this — it only shapes the synthesis. Use for special modes, e.g. devil's advocate: \"Argue against the majority position — find the strongest case that the consensus is wrong and surface every dissenting point.\" Or output contracts: \"Answer VERDICT: SAFE/UNSAFE first, then justification.\" Omit for the standard balanced synthesis."
        }
      },
      "additionalProperties": false
    }
    arguments 50 lines
  • council_result reads unknown 16h ago

    Fetch the result of a council_query started with async=true. Returns status "running" while the council is still working (wait 30-60 seconds and call again), the full synthesis + per-model responses once complete, or status "failed" with the error. Polling is free — the council run itself was already billed by council_query.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "queryId"
      ],
      "properties": {
        "queryId": {
          "type": "string",
          "maxLength": 40,
          "minLength": 10,
          "description": "The queryId returned by council_query when called with async=true."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • library_list reads unknown 2h ago

    List the documents in the user's Council RAG library. Returns id, filename, source type, ingestion status, chunk count, and upload date for each document. No retrieval, no budget consumption.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • library_search reads unknown 13h ago

    Semantic search over the user's Council RAG library (uploaded PDFs, Word docs, contracts, research papers, codebases). Returns top-K chunks with source filename and page number. No model call, no budget consumption. Use to find direct quotes, check what the library contains, or scope a follow-up council_query_with_rag call.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "number",
          "maximum": 20,
          "minimum": 1,
          "description": "Number of chunks to return, 1-20. Default: 8."
        },
        "query": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "Semantic retrieval query — describe the content you want, not keywords. Example: \"termination and notice-period clauses in the vendor agreement\""
        },
        "project_id": {
          "type": "string",
          "description": "Restrict retrieval to a specific Council project workspace ID. Omit to search the whole library."
        }
      },
      "additionalProperties": false
    }
    arguments 26 lines
  • council_query_with_rag reads unknown 16h ago

    Like council_query, but first retrieves the most relevant passages from the user's personal Council RAG library (uploaded PDFs, Word docs, contracts, research papers, codebases) and injects them into every model's prompt. Use when the question is about content the user has uploaded — contract review, research synthesis across a paper library, code review against an architecture doc, etc. Ultra-tier only.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prompt"
      ],
      "properties": {
        "async": {
          "type": "boolean",
          "default": false,
          "description": "When true, retrieval runs immediately (sources are returned right away) but the council itself runs in the background — fetch the finished answer with council_result. Use when your MCP client enforces a fixed tool-call timeout or when querying 4+ models."
        },
        "models": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 10,
          "minItems": 2,
          "description": "Model IDs to include. Defaults to the user's preferred council."
        },
        "prompt": {
          "type": "string",
          "maxLength": 20000,
          "minLength": 1,
          "description": "The question or task to send to the council. Example: \"Review this NDA draft against our standard playbook terms.\""
        },
        "project_id": {
          "type": "string",
          "description": "Restrict retrieval to a specific Council project workspace."
        },
        "synthesize": {
          "type": "boolean",
          "default": true,
          "description": "When true (default), include the moderator synthesis + consensus score."
        },
        "library_query": {
          "type": "string",
          "description": "Optional retrieval-specific query. If omitted, the main prompt is used as the retrieval query. Set this when the user's prompt has unrelated framing but the concrete documents to retrieve are described by something different."
        },
        "retrieval_limit": {
          "type": "number",
          "maximum": 20,
          "minimum": 1,
          "description": "Number of chunks to retrieve. Default: 8."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • council_usage reads unknown 2h ago

    Return the user's current monthly cost-budget consumption (current spend, budget cap, percentage used, days until reset). Use to decide whether to warn the user before invoking another council_query, or to suggest using cheaper models. Per Council's rule: never show dollar amounts to the user in the response — use percentages.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • council_models reads unknown 2h ago

    List the AI models available to the current user. Returns ID, provider, tier, context window, and capability flags (web search, vision, streaming). Use the IDs returned here as the `models` array argument to council_query / council_query_with_rag.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d40a0add39745378.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d40a0add39745378/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d40a0add39745378/badge.svg)](https://brick.blue/agent/d40a0add39745378?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.