Tribunal TJMS: Conferência de Certificate, official-source lookup. Platform-hosted, pay per query wi
Scored across 7 tools
Each tool serves a distinct purpose: authentication, connection status, marketplace search, bug reporting, version display, toolkit overview, and the domain-specific certificate query. There is no functional overlap.
Names are highly inconsistent: some follow verb_noun patterns (report_bug, show_version, authenticate, connect), others are singular nouns (marketplace, toolkit_info), and one is a long Portuguese phrase (tribunal_tjms_obter_certidao_consultar). No consistent convention is used.
The count of 7 is within the typical range, but many tools are generic platform utilities rather than domain-specific operations. For a server titled 'Tribunal TJMS: Conferência de Certidão', the single domain tool feels out of place among the administrative ones, so the set is not well-scoped.
For the stated domain of certificate querying, only one operation is provided. While it covers the core need, missing features like listing certificates or checking status would require additional tools. The generic tools do not address this gap, so completeness is partial.
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.
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.
Tribunal TJMS: Conferência de Certidão, consulta em fonte oficial. Hospedado pela plataforma, sem credenciais da plataforma, pague por consulta com crédito pré-pago. Consulta informação de fontes e órgãos oficiais brasileiros (a mesma disponível ao cidadão), não é dado sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).
Inputs: data_pedido (required), numero_pedido (required), cpf, cnpj.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Tribunal TJTO: Certificate Judicial, official-source lookup. Platform-hosted, pay per query with pre
Tribunal TJMS: Cadastro de Pedido de Certificate (1º grau), official-source lookup. Platform-hosted,
Tribunal TJSC: Visualizar Certificate, official-source lookup. Platform-hosted, pay per query with p
Tribunal TJRJ: Visualizar Certificate, official-source lookup. Platform-hosted, pay per query with p
Add one secure layer between your agents and this server.