MCP servers › br.ia.dilligence › certidoes
MCP server · registry snapshot 2026-10-29 · last tested 2026-10-29
certidoes MCP server
Registry name br.ia.dilligence/certidoes
Dilligence — certidões de empresas — the publisher's title
by dilligence.ia.br · domain (the registry's namespace rule)Website ↗
Certidões negativas de empresas (CNPJ) num pedido: pede nos órgãos, lê cada PDF e resume. — the publisher's description
Summary
br.ia.dilligence/certidoes is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain dilligence.ia.br. On 2026-10-29 ProtocolProbe connected to it in read-only mode and read its inventory: 34 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 34
- Last tested
- 2026-10-29
Tool list size
6,517 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (34 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-29. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-29 (dilligence.ia.br), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.0).
Observed fact
This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (remove_member, create_api_key, create_diligence, create_request, remove_item and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-29.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-29
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-28 (registry, as of the 2026-10-29 snapshot)
- First listed version
- 2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-29
- Package and repository
- checked 2026-10-29
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-28, listed on 2026-10-29 with version 1.0.0 (published 2026-10-28).
Source: the official MCP Registry list on 2026-10-28 and on 2026-10-29.
What it is
What does this server offer?
Observed inventoryNone of its 34 tools are described as changing anything. For 34 the reading was uncertain, so no mark is shown.
- signupon 21 other servers
“Cria a conta do usuário com o e-mail dele e 10 créditos grátis (10 certidões).”
3 inputs, 1 required
emailstringrequirednamestringagent_namestring“Seu nome, ex.”
- accounton 26 other servers
“Conta atual: saldo em créditos (1 crédito = 1 certidão emitida), membros, chaves, extrato e pagamento (pacotes, cartão salvo).”
Takes no inputs.
- buy_creditson 24 other servers
“Cria um link de pagamento do Stripe para o usuário comprar um pacote de créditos: 10 créditos por R$ 80, 30 créditos por R$ 200, 80 créditos por R$ 500.”
1 input, 1 required
creditsnumberrequired“Créditos do pacote”
- check_paymenton 14 other servers
“Confere se o usuário pagou o link de buy_credits e credita o saldo (uma vez só).”
1 input, 1 required
session_idstringrequired
- invite_memberon 8 other servers
“Convida alguém para o workspace (vê e edita todas as diligências).”
1 input, 1 required
emailstringrequired
- remove_memberon 6 other servers
“Tira um membro do workspace (id de account.members).”
1 input, 1 required
user_idstringrequired
- create_api_keyon 36 other servers
“Cria outra chave de API (para outro agente ou sistema).”
1 input, 1 required
labelstringrequired
- revoke_api_keyon 20 other servers
“Revoga uma chave (id de account.keys).”
1 input, 1 required
key_idstringrequired
- list_catalogon 17 other servers
“Certidões que buscamos: órgão, validade, taxa do órgão, se é automática.”
1 input
cnpjstring“Opcional: só as certidões que valem para esta empresa (pela sede na Receita)”
- list_templateson 116 other servers
“Modelos de diligência prontos (ma: aquisição/M&A, credito, fornecedor, licitacao, imovel), já ajustados à sede de cada CNPJ: TRT e TRF da região de cada empresa (todos os TRTs e TRFs); onde não busca…”
2 inputs
cnpjsarraynamestring“Nome da diligência, para sugerir o modelo”
- join_monitoring_waitlist
“Monitoramento contínuo de CNPJs (renovar certidões antes de vencer e avisar quando algo muda) está em acesso antecipado.”
2 inputs, 1 required
emailstringrequirednotestring“Opcional: quantos CNPJs e para quê, ex.”
- create_diligence
“Abre uma diligência para os CNPJs com a lista de documentos que o usuário quer.”
6 inputs, 1 required
namestringcnpjsarrayrequiredtemplatestring“Modelo de list_templates (ma, credito, fornecedor, licitacao, imovel): monta a lista ajustada à sede de cada empresa; certidoes e documents somam a ela”certidoesarray“ids de list_catalog”documentsarray“Títulos de documentos fora do catálogo”fetchboolean“Já pede as certidões aos órgãos”
Show 22 more tools
- fetch_certidoes
“Pede aos órgãos as certidões da diligência que ainda não foram pedidas (status "ready"), ou só item_ids (também repete as que pararam).”
2 inputs, 1 required
diligence_idstringrequireditem_idsarray
- list_requestson 13 other servers
“Pedidos do workspace: a pessoas (link de envio; quem abriu, lembretes) e aos órgãos (cada busca), com o que já chegou.”
1 input
open_onlyboolean
- create_requeston 7 other servers
“Faz um pedido de documentos.”
8 inputs, 1 required
torequired“"robot" ou {name, email, send}”diligence_idstringcnpjstringnamestringcertidoesarraydocumentsarrayitem_idsarraymessagestring
- remind_request
“Manda de novo o e-mail de um pedido a uma pessoa, com o que ainda falta (id de list_requests).”
1 input, 1 required
request_idstringrequired
- remove_itemon 2 other servers
“Tira um documento da lista da diligência.”
2 inputs, 2 required
diligence_idstringrequireditem_idstringrequired
- match_documents
“Lê uma lista de documentos pedidos (checklist colado, e-mail, planilha ou foto em base64) e diz, para cada um, quais certidões do catálogo atendem (source_ids) ou se é um documento que alguém precisa…”
3 inputs
textstringcontent_base64string“Arquivo (PDF, Excel, Word, CSV, imagem) em vez de text”filenamestring
- list_diligences
“Lista as diligências do workspace com progresso.”
Takes no inputs.
- get_diligence
“Situação de cada item (status, responsável, resultado, validade, código, resumo), links de envio e de leitura, e app_url.”
1 input, 1 required
idstringrequired
- wait_for_changeson 2 other servers
“Espera até 45 s por mudanças na diligência.”
2 inputs, 1 required
idstringrequiredcursorstring
- rename_diligence
“Renomeia a diligência.”
2 inputs, 2 required
diligence_idstringrequirednamestringrequired
- add_documenton 5 other servers
“Adiciona documentos à lista de uma diligência já aberta, para todas as empresas (ou só party_ids, de get_diligence.parties): certidoes (ids de list_catalog) e documents (títulos livres, ex.”
6 inputs, 1 required
diligence_idstringrequiredcertidoesarraydocumentsarraytitlestringparty_idsarrayfetchboolean
- get_itemon 46 other servers
“Detalhe completo de um item: resumo inteiro, motivo de ter parado, protocolo, próxima checagem, taxa, tentativas e histórico.”
2 inputs, 2 required
diligence_idstringrequireditem_idstringrequired
- read_documenton 13 other servers
“Lê o documento de um item (certidão emitida ou arquivo enviado): texto completo do PDF, resultado, validade e código.”
3 inputs, 2 required
diligence_idstringrequireditem_idstringrequiredinclude_fileboolean
- retry_item
“Busca a certidão de novo (item que falhou, parou num muro, ou para renovar).”
2 inputs, 2 required
diligence_idstringrequireditem_idstringrequired
- approve_fee
“Aprova a taxa do órgão para um item (ex.”
2 inputs, 2 required
diligence_idstringrequireditem_idstringrequired
- mark_not_applicable
“Marca o item como "não se aplica", com o motivo.”
3 inputs, 3 required
diligence_idstringrequireditem_idstringrequiredreasonstringrequired
- assign_item
“Define o responsável por um item: "me", o id de um membro (u:...), ou {name,email,send_email} de alguém de fora (recebe link de envio; e-mail só com send_email=true).”
3 inputs, 3 required
diligence_idstringrequireditem_idstringrequiredownerrequired
- bulk_items
“Uma ação em vários itens de uma vez: action="owner" (owner como em assign_item, ou null para tirar), "retry" (busca de novo as certidões que pararam ou não foram pedidas; gasta créditos quando saem),…”
5 inputs, 3 required
diligence_idstringrequiredactionstringrequireditem_idsarrayrequiredownerreasonstring
- request_documentson 1 other server
“Pede vários itens a uma pessoa de fora (ex.”
5 inputs, 3 required
diligence_idstringrequireditem_idsarrayrequiredemailstringrequirednamestringsend_emailboolean
- upload_documenton 6 other servers
“Anexa um arquivo (PDF, PNG, JPG) a um item, por file_url ou content_base64.”
5 inputs, 2 required
diligence_idstringrequireditem_idstringrequiredfile_urlstringcontent_base64stringfilenamestring
- shareon 6 other servers
“Liga ou desliga o link de leitura da diligência (quem tiver o link vê os itens e baixa os PDFs, sem login).”
2 inputs, 2 required
diligence_idstringrequiredenabledbooleanrequired
- export_documentson 1 other server
“Link de um ZIP com todos os documentos da diligência (pasta Documentos/) e uma planilha .xlsx com uma linha por documento: situação, resultado, validade, código, protocolo, resumo e link para o arqui…”
2 inputs, 1 required
diligence_idstringrequiredenable_shareboolean
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-29.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 13% of 82
- Tools with a description
- 100% of 34
- Typical description length
- 195 characters
The tool set
Counted from the listing
- Tools
- 34
- Size of the list
- about 3,513 tokens for an agent to load (characters ÷ 4)
- Naming
- 31 of 34 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-29 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://dilligence.ia.br/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"certidoes": {
"url": "https://dilligence.ia.br/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"certidoes": {
"type": "http",
"url": "https://dilligence.ia.br/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"certidoes","type":"http","url":"https://dilligence.ia.br/mcp"}'Claude Code
claude mcp add --transport http certidoes https://dilligence.ia.br/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"certidoes": {
"type": "streamableHttp",
"url": "https://dilligence.ia.br/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"certidoes": {
"httpUrl": "https://dilligence.ia.br/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.certidoes] url = "https://dilligence.ia.br/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"certidoes": {
"url": "https://dilligence.ia.br/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://dilligence.ia.br/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint dilligence.ia.br/mcp | Session opened | matches | our test · 2026-10-29 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-29 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-29. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about br.ia.dilligence/certidoes
Answered from the data aboveWho publishes br.ia.dilligence/certidoes?
The registry ties the namespace br.ia.dilligence to the domain dilligence.ia.br; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does br.ia.dilligence/certidoes need an API key or sign-in?
It opened a session without any credential on 2026-10-29. The registry entry declares no required credential; no declaration is not a guarantee.
Has br.ia.dilligence/certidoes been security tested?
Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-29, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,055 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 34 tools, 0 resources, 0 prompts.
- 4,110 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “br.ia.dilligence/certidoes: MCP server record.” Data checked 2026-10-29. https://protocolprobe.com/mcp/servers/br.ia.dilligence/certidoes
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/br.ia.dilligence/certidoes)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology