PNCP
REMOTE · API.MCP.AI
Search Brazilian government tenders and public procurement (PNCP): find notices and auctions by keyw
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3197 tokens (~168/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.460 → 0.9.467 functional
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.459 → 0.9.460 functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.454 → 0.9.459 functional
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.452 → 0.9.454 functional
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.450 → 0.9.452 functional
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.449 → 0.9.450 functional
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.442 → 0.9.449 functional
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.429 → 0.9.442 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.mcp.ai/p_pncp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| mcp.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_pncp | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_pncp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authenticate ~99
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: "<jwt>" } after the user pastes, or with no args to get the link.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
marketplace ~532
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/<slug> link that opens without login.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| arguments | string | – | – |
| cancel_comment | string | – | – |
| cancel_reason | string | – | – |
| conversation | string | – | – |
| immediate | boolean | – | – |
| limit | number | – | – |
| mcp_id | string | – | – |
| message | string | – | – |
| prompt_body | string | – | – |
| prompt_category | string | – | – |
| prompt_description | string | – | – |
| prompt_slug | string | – | – |
| prompt_targets | array | – | – |
| prompt_title | string | – | – |
| prompt_tool | string | – | – |
| prompt_vars | string | – | – |
| query | string | – | – |
| report_context | string | – | – |
| request_details | string | – | – |
| request_name | string | – | – |
| tier_slug | string | – | – |
| tool_id | string | – | – |
No output schema declared.
No examples provided.
pncp_arquivos ~101
Documentos de uma licitação/edital (edital, termo de referência, anexos) com o LINK de download de cada arquivo (em geral PDF). A partir de cnpj+ano+sequencial (a referência devolvida pela pncp_buscar). Use pra trazer o PDF do edital pro usuário ou pra outra IA ler o conteúdo.
| Name | Type | Req | Description |
|---|---|---|---|
| ano | – | yes | – |
| cnpj | string | yes | – |
| sequencial | – | yes | – |
No output schema declared.
No examples provided.
pncp_atas ~80
Lista atas de registro de preços vigentes num período (referência de preços praticados pelo governo), opcionalmente por órgão (CNPJ).
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj | string | – | – |
| data_final | string | yes | – |
| data_inicial | string | yes | – |
| pagina | number | – | – |
| tamanho_pagina | number | – | – |
No output schema declared.
No examples provided.
pncp_buscar ~248
Busca licitações por PALAVRA-CHAVE no objeto (cobertura NACIONAL ampla, índice full-text), em editais, atas ou contratos. Retorna órgão, estado, município, modalidade, situação, datas e a referência (cnpj/ano/sequencial) pra detalhar. Aceita VÁRIOS termos em `termos[]`: cada um vira uma busca separada (disparadas com um intervalo entre si pra não pegar rate limit), e os resultados voltam fundidos e deduplicados numa lista só, com `termos_buscados`. IMPORTANTE: a busca full-text NÃO traz valor (vem sempre null) e não filtra por valor. Pra filtrar/ordenar por VALOR use pncp_listar (com apenas_abertas + termos + valor_min/valor_max) ou pncp_historico (faixa de valor sobre a base acumulada).
| Name | Type | Req | Description |
|---|---|---|---|
| ordenacao | string | – | – |
| pagina | number | – | – |
| status | string | – | – |
| tam_pagina | number | – | – |
| termo | string | – | – |
| termos | array | – | – |
| tipo | string | – | – |
No output schema declared.
No examples provided.
pncp_contratos ~73
Lista contratos públicos firmados num período, opcionalmente filtrando por órgão (CNPJ).
| Name | Type | Req | Description |
|---|---|---|---|
| cnpj_orgao | string | – | – |
| data_final | string | yes | – |
| data_inicial | string | yes | – |
| pagina | number | – | – |
| tamanho_pagina | number | – | – |
No output schema declared.
No examples provided.
pncp_detalhe ~121
Detalhe completo de uma licitação/contratação a partir de cnpj+ano+sequencial (a referência devolvida pela pncp_buscar). Com itens=true, inclui os itens da contratação com preços unitários, essencial pra pesquisa de preços. Com resultado=true, anexa o bloco `resultado` com o(s) fornecedor(es) vencedor(es) homologado(s).
| Name | Type | Req | Description |
|---|---|---|---|
| ano | – | yes | – |
| cnpj | string | yes | – |
| itens | boolean | – | – |
| resultado | boolean | – | – |
| sequencial | – | yes | – |
No output schema declared.
No examples provided.
pncp_historico ~166
Arquivo histórico de licitações: consulta editais que a plataforma acumulou ao longo do tempo (inclusive os que já encerraram ou saíram do ar), por PALAVRA-CHAVE no objeto, estado (UF), modalidade, situação e período de publicação. Diferente da pncp_buscar (consulta ao vivo), aqui a base é o arquivo próprio, útil pra histórico e séries.
| Name | Type | Req | Description |
|---|---|---|---|
| ate | string | – | – |
| desde | string | – | – |
| modalidade | string | – | – |
| pagina | number | – | – |
| situacao | string | – | – |
| tam_pagina | number | – | – |
| termo | string | – | – |
| uf | string | – | – |
| valor_max | number | – | – |
| valor_min | number | – | – |
No output schema declared.
No examples provided.
pncp_listar ~360
Busca PRINCIPAL de licitações abertas por palavra-chave, faixa de VALOR, estado, modalidade e período. Cobertura agregada e instantânea de vários portais. Já vem com VALOR estimado por item e RANQUEADA por valor (maior 1º) automaticamente. Os `termos` são EXPANDIDOS em sinônimos automaticamente (ex.: 'software' busca também saas, licença de uso, sistema...). TUDO opcional: sem datas, usa os próximos 30 dias por abertura. Use termos[] pra palavra-chave, valor_min/valor_max pra faixa, uf/modalidade pra estreitar; apenas_abertas=true (default). Cada item traz `id` + `valor`; pra itens/preços e leitura do edital use pncp_processo/pncp_texto. Passe incluir_valor:false pra uma lista rápida sem valor, ou expandir:false pra não expandir os termos. Modalidades: 1 Leilão-Elet, 4 Concorrência-Elet, 6 Pregão-Elet, 8 Dispensa, 9 Inexigibilidade, 12 Credenciamento.
| Name | Type | Req | Description |
|---|---|---|---|
| apenas_abertas | boolean | – | – |
| cnpj | string | – | – |
| data_final | string | – | – |
| data_inicial | string | – | – |
| expandir | boolean | – | – |
| incluir_valor | boolean | – | – |
| modalidade | number | – | – |
| municipio | string | – | – |
| ordenacao | string | – | – |
| pagina | number | – | – |
| tamanho_pagina | number | – | – |
| termos | array | – | – |
| uf | string | – | – |
| valor_max | number | – | – |
| valor_min | number | – | – |
No output schema declared.
No examples provided.
pncp_oportunidades ~332
Busca de OPORTUNIDADES de licitação (editais/pregões) com filtros ricos por palavra-chave, FAIXA DE VALOR da compra, UFs, modalidades, portais, registro de preço, participação exclusiva ME/EPP e superoportunidades. Cobertura agregada de vários portais. Devolve uma página com o `id` de cada oportunidade (use em pncp_processo pro detalhe completo), datas de abertura/encerramento e, quando `edital_legivel:true`, os campos `cnpj`/`ano`/`sequencial` pra LER o edital com pncp_texto/pncp_arquivos. Mesma fonte da pncp_listar, com mais filtros de qualificação.
| Name | Type | Req | Description |
|---|---|---|---|
| data_final | string | – | – |
| data_inicial | string | – | – |
| excluir | string | – | – |
| excluir_registro_preco | boolean | – | – |
| expandir | boolean | – | – |
| itens_desertos | boolean | – | – |
| modalidades | array | – | – |
| pagina | number | – | – |
| participacao_exclusiva | boolean | – | – |
| pesquisa_ampla | boolean | – | – |
| portais | array | – | – |
| somente_sigilosos | boolean | – | – |
| superoportunidades | boolean | – | – |
| termo | string | – | – |
| termos | array | – | – |
| tipo_item | string | – | – |
| tipo_periodo | string | – | – |
| ufs | array | – | – |
| valor_max | number | – | – |
| valor_min | number | – | – |
No output schema declared.
No examples provided.
pncp_orgaos ~195
Busca de ÓRGÃOS/entidades compradoras por nome, UF e/ou portal. Devolve portal, UF, uasg, nome e info de pagamento. Útil pra achar o órgão e usar o filtro em outras buscas. Aceita VÁRIOS nomes em `termos[]`: cada um vira uma busca separada (disparadas com intervalo entre si pra não pegar rate limit), resultados fundidos e deduplicados. ATENÇÃO: termo muito amplo (ex.: 'prefeitura', 'ministerio') estoura a fonte, prefira UF/portal ou um nome específico. Com antecipagov=true, consulta a base do programa AntecipaGov.
| Name | Type | Req | Description |
|---|---|---|---|
| antecipagov | boolean | – | – |
| pagina | number | – | – |
| portais | array | – | – |
| termo | string | – | – |
| termos | array | – | – |
| uf | string | – | – |
No output schema declared.
No examples provided.
pncp_pca ~74
Plano anual de contratações (PCA) por ano e classificação superior do catálogo: o que os órgãos planejam contratar no ano.
| Name | Type | Req | Description |
|---|---|---|---|
| ano_pca | number | yes | – |
| codigo_classificacao_superior | number | yes | – |
| pagina | number | – | – |
| tamanho_pagina | number | – | – |
No output schema declared.
No examples provided.
pncp_processo ~199
Detalhe de oportunidade(s) por `id` (de pncp_listar/pncp_oportunidades). DOIS modos: (1) `id` único → detalhe COMPLETO (objeto, situação, órgão, modalidade, ITENS com preços, `valor` estimado, datas) + `cnpj`/`ano`/`sequencial` pra LER o edital (pncp_texto/pncp_arquivos). (2) `ids` em LOTE → detalha vários numa só chamada (com throttle interno) e devolve RANKING por VALOR (maior 1º) — é a forma certa de RANQUEAR POR VALOR, já que a listagem não traz valor. Passe os `id` da página do pncp_listar em `ids` pra montar o ranking sem N chamadas.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | – | – |
| ids | array | – | – |
No output schema declared.
No examples provided.
pncp_resultado ~206
Quem GANHOU a licitação: o(s) fornecedor(es) vencedor(es) homologado(s) a partir de cnpj+ano+sequencial (a referência da pncp_buscar). Retorna, por vencedor, o CNPJ, a razão social, o valor REAL homologado (já com o desconto da disputa, melhor que o estimado), a natureza jurídica (separa estatal de privada, ex.: 'Empresa Pública') e o porte (ME/EPP vs Demais). Agrega por fornecedor (vários itens do mesmo vencedor viram uma linha) e traz o total homologado. Itens sem resultado são ignorados. Use numero_item pra um item específico; omita pra todos. Observação: a lista de PERDEDORES e os lances não vêm por aqui (só no Termo).
| Name | Type | Req | Description |
|---|---|---|---|
| ano | – | yes | – |
| cnpj | string | yes | – |
| numero_item | number | – | – |
| sequencial | – | yes | – |
No output schema declared.
No examples provided.
pncp_texto ~138
Texto INTEIRO do edital em markdown (com marcadores '## Página N'), pra você RESUMIR ou ler o documento todo. Mantém o link de download do PDF no retorno. A partir de cnpj+ano+sequencial (referência da pncp_buscar). Editais muito grandes vêm truncados (use de_pagina/ate_pagina). Documento escaneado retorna aviso (OCR pendente).
| Name | Type | Req | Description |
|---|---|---|---|
| ano | – | yes | – |
| ate_pagina | number | – | – |
| cnpj | string | yes | – |
| de_pagina | number | – | – |
| documento | – | – | – |
| sequencial | – | yes | – |
No output schema declared.
No examples provided.
report_bug ~50
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| conversation | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
show_version ~17
Show the current MCP platform and adapter versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
toolkit_info ~37
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the PNCP MCP server?
PNCP is a hosted endpoint at https://api.mcp.ai/p_pncp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcp.ai
claude mcp add --transport http mcp-dir-pncp-mcp 'https://api.mcp.ai/p_pncp'
What is the PNCP MCP server?
PNCP is an MCP server listed in the public MCP registry as io.github.mcp-dir/pncp-mcp. Search Brazilian government tenders and public procurement (PNCP): find notices and auctions by keyw. This page covers its hosted endpoint (https://api.mcp.ai/p_pncp).
Is the PNCP MCP server safe to use?
PNCP scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PNCP MCP server expose?
PNCP exposes 19 tools: pncp_buscar, pncp_listar, pncp_oportunidades, pncp_processo, pncp_detalhe, and 14 more. Their descriptions and schemas cost roughly 3,070 tokens of context every time the server is loaded.
Does the PNCP MCP server require authentication?
No. We connected to PNCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PNCP MCP server still maintained?
PNCP is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PNCP MCP server?
VerifyMCP ran 12 checks on PNCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about PNCP: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.