Public search of the Brazilian Federal Court of Accounts (TCU) case law: keyword search across rulin
Scored across 8 tools
The six platform tools (connect, marketplace, report_bug, etc.) are clearly distinct, and the two TCU tools have separate purposes: one lists recent acórdãos without a keyword, the other performs keyword searches. However, authenticate and connect both deal with credentials/status, which could cause minor confusion, and tcu_acordaos_recentes vs tcu_buscar overlap partially since both return TCU content. Overall, boundaries are clear with only slight ambiguity.
Naming is inconsistent: TCU-specific tools use snake_case with a 'tcu_' prefix (tcu_buscar, tcu_acordaos_recentes), while platform tools use camelCase or simple lowercase (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). No consistent verb/noun pattern or style across the set.
The total of 8 tools is within a reasonable range, but only 2 are TCU-specific; the other 6 are generic platform utilities. For a server titled 'TCU Jurisprudência', the count feels off—either too many unrelated tools or too few domain tools. It's borderline, not egregious.
The TCU domain is covered by a search and a recent-list tool, but lacks operations like fetching a specific acórdão by ID, filtering by date/relator, or browsing related jurisprudência. The platform tools cover their own generic concerns, but the domain surface feels minimal—no obvious dead ends, but notable gaps exist for a jurisprudence-focused server.
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.
Inputs: token.
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Inputs: no named parameters.
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
Lista os acórdãos mais recentes do TCU (dados abertos oficiais), paginado, sem palavra-chave: sumário, relator, colegiado, data da sessão e links. Pra buscar por tema, use tcu_buscar.
Inputs: inicio, quantidade.
Busca textual (por palavra-chave) na jurisprudência do TCU. Escolha a base: 'acordaos' (entendimentos exarados em acórdãos), 'jurisprudencia' (enunciados da jurisprudência selecionada) ou 'sumulas'. Retorna título, sumário/enunciado, trechos destacados (fragmentos), relator, colegiado e links pro inteiro teor.
Inputs: termo (required), base, inicio, tamanho.
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Case law search, court decisions and súmulas, across indexed public sources (STF, STJ, TST, state co
Search Brazilian case law from federal and state courts with verified decisions and source links.
Brazil's National Electronic Court Gazette (CNJ/DJEN), judicial publications and notifications. Sear
Brazilian case law: 1.1M+ decisions from 17 courts, with citable links to official sources.
Add one secure layer between your agents and this server.
