M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
L

Licinexus MCP Server

Community
MCP server for Brazilian public procurement and CNPJ data
How to install ↓ Compare GitHub source repository ↗
Category
Other #174 of 230
Stars
★ 80 Popular
Transport
stdio (local process)
Runtime
Node.js 18+
Credentials
No credential needed
License
MIT
Last commit
Tools
18
46FMRS · D

This is an open-source MCP server focused on Brazilian public procurement and CNPJ open data, covering bids, contracts, price registration records, agencies, PCA, suppliers, and aggregate analysis across 18 tools, 4 prompts, and 2 resources. It is keyless and signup-free with simple install config, making it useful for analysts and developers doing public data queries; it does not provide Licinexus's proprietary matchmaking or scoring, has no official SLA, and its data accuracy depends on upstream public APIs.

Strongest · Documentation 12/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
8/20
Maintenance
10/20
Documentation
12/20
Setup experience
10/20
Why each score
Reliability 6/20
Static review sees only the README and server.json; no repository source, CI workflows, or committed tests were provided. The README claims a '15/15 endpoint smoke test' and a 'retry budget', but these are unverified assertions and, per the calibration rules, earn no credit. The manifest declares stdio transport, 18 tools, 4 prompts, 2 resources, yet tool parameters appear only as prose (e.g. palavraChave, somenteVigentes) with no JSON schema, so declared tools cannot be confirmed to match real behavior. Startup depends on npx fetching @licinexusbr/mcp pinned at 0.2.2, with no verifiable lockfile; the README itself admits PNCP may take 15-30s, and error handling is a textual promise only. Score 6: the happy path is plausible but tests and edge-case evidence are entirely absent, and nothing supports a higher score.
Security and permissions 8/20
No red lines observed: no malware, credential theft, covert exfiltration, unconfirmed destructive default operations; all data sources are public APIs (PNCP, BrasilAPI/MinhaReceita) and CNPJ_PROVIDER is explicitly marked non-secret and key-free. The README states clear scope boundaries (no private infrastructure, no proprietary data) and points to SECURITY.md for responsible disclosure. Deductions: aside from README self-description, there is no source-level evidence that operations are strictly read-only, that no local persistence occurs, or that network calls stay within the declared domain; execution via npx -y installs an npm package at runtime, an inherent supply-chain trust surface without committed integrity or lock verification. Score 8.
Maintenance 10/20
Signals: MIT license, 78 stars, 4 open issues, not archived, manifest and npm version aligned at 0.2.2, and a phased roadmap with a public release (v0.1.0). This suggests organized maintenance and clear ownership (Licinexus). Deductions: no source, commit history, release timeline, dependency-update policy, or issue-response record is verifiable; 'best effort, no SLA, triage within 7 days' is a weak commitment; the roadmap includes incomplete phases (Fase 7) and a suspicious future date (11/05/2026), reducing credibility. Score 10: active with clear license but governance and versioning evidence is thin.
Documentation 12/20
Documentation is layered and readable: bilingual entry points, install examples for six-plus clients (Claude Desktop, Cursor, Continue, Cline, Zed, programmatic SDK), troubleshooting for absolute-path npx, EACCES, version caching, timeouts, logging (LICINEXUS_LOG_LEVEL) and localized errors (LICINEXUS_LANG), plus tool/prompt/resource tables and a scope statement. Deductions: the 18 tools lack parameter types, required flags, defaults, pagination, and return shapes; rate limits, data freshness, and accuracy disclaimers are undisclosed; the text contains a future date and an unverified '15/15 endpoints' claim. Usable but with hidden assumptions; score 12.
Setup experience 10/20
The install path is concise: Node >=18 plus an MCP client, with a short JSON snippet using command npx and args -y @licinexusbr/mcp, no keys or database, covering config file locations and UI entry points for mainstream clients, plus thorough troubleshooting. Deductions: no in-repo source or executable verification, so package usability cannot be confirmed; reliance on online npx fetching is a fragile step; Claude Desktop on Linux is not officially supported; the walkthrough rests on README claims rather than checkable evidence. Well below the static ceiling of 15; score 10.

Static review · not runListed 2026-09-10

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • LLM users and analysts who need Brazilian public procurement open data
  • Developers using Claude Desktop, Cursor, Continue, Cline/Roo Code, or Zed
  • Govtech, compliance, supplier intelligence, and bidding researchers
  • Teams wanting keyless, signup-free access to PNCP and CNPJ public data

Not for

  • Users needing Licinexus's proprietary matchmaking engine, supplier scoring, price aggregation, or AI-generated artifacts
  • Scenarios requiring an official SLA or paid support (this is a community project, best effort, no SLA)
  • Users expecting access to private databases or non-public data
  • ChatGPT web users, since the consumer web app does not support MCP stdio

Required permissions

  • Network access to public HTTPS endpoints: PNCP and BrasilAPI (or MinhaReceita)
  • Local execution: downloads and runs the npm package @licinexusbr/mcp via npx, using the local npm cache (e.g. ~/.npm/_npx/)
  • Process communication: JSON-RPC over stdin/stdout with the MCP client
  • In-memory local cache: short-TTL LRU caching of heavy responses
  • Optional environment variables: CNPJ_PROVIDER (brasilapi default or minhareceita), LICINEXUS_LOG_LEVEL, LICINEXUS_LANG
  • No API keys or account credentials required

Risks and side effects

  • Data comes from public government APIs; PNCP can take 15–30 seconds to respond, and broad queries may time out
  • Public data may be delayed, missing, or inconsistent, so LLM output needs human review and should not be the sole basis for legal or bidding decisions
  • npx downloads and executes a third-party npm package, so supply-chain risk depends on the trustworthiness of that package's publishing channel
  • npx caching may run an older version unless @latest is specified
  • Using an absolute npx path from which npx writes a local machine path into your config file
  • Debug logging may include query parameters, so avoid exposing sensitive context

Setup

Before you start

Runtime：Node.js 18+

Other optional settings (3)
CNPJ_PROVIDER optional CNPJ data source: 'brasilapi' (default) or 'minhareceita'; both are free public APIs, no key needed.
LICINEXUS_LOG_LEVEL optional Set to debug to inspect requests/responses in the terminal while the client makes calls.
LICINEXUS_LANG optional Language of tool error messages: pt (default) or en.
  1. Make sure Node.js 18 or later is installed.
  2. Add the licinexus server to your MCP client config. For Claude Desktop: open Settings → Connectors → Edit Config and edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json), adding {"licinexus": {"command": "npx", "args": ["-y", "@licinexusbr/mcp"]}} under mcpServers.
  3. Save the file, then quit and reopen the client completely (Cmd+Q on macOS — closing the window is not enough).
  4. Verify under Settings → Connectors → licinexus that 18 tools are listed. Cursor uses ~/.cursor/mcp.json, Continue uses ~/.continue/config.json, and Zed uses the context_servers field in ~/.config/zed/settings.json. Note that this is a stdio server, so running npx @licinexusbr/mcp directly in a terminal appears to hang — that is normal, it is waiting for a client to connect over JSON-RPC via stdin/stdout.
claude_desktop_config.json 
{
  "mcpServers": {
    "licinexus": {
      "command": "npx",
      "args": ["-y", "@licinexusbr/mcp"]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "licinexus": {
      "command": "npx",
      "args": [
        "-y",
        "@licinexusbr/mcp"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add licinexus -- npx -y @licinexusbr/mcp

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After restarting the client, Settings → Connectors → licinexus should list all 18 tools (e.g. search_licitacoes, get_cnpj_data). Then ask "Quais ferramentas do licinexus você tem disponíveis?" — if Claude lists the 18 tools, the connection works.

Troubleshooting

  1. 'Server failed to start' or 'command not found: npx': the client cannot find npx on PATH; run which npx and put the absolute path in the config's command field
  2. Tools do not appear after saving config: fully restart the client (Cmd+Q on macOS); MCP servers only load at startup
  3. EACCES or permission errors: run npm cache clean --force and retry npx -y @licinexusbr/mcp
  4. An old version is running: use args ["-y", "@licinexusbr/mcp@latest"]
  5. Timeouts on large queries: PNCP can be slow and the server already implements a retry budget; refine the query with more specific filters
  6. Need logs: run with LICINEXUS_LOG_LEVEL=debug; switch error message language to English with LICINEXUS_LANG=en
  7. Running it directly in a terminal appears to hang: that is expected for a stdio server waiting for a client

Things to try

Once connected, you can ask your AI assistant things like:

  • Show me the CNPJ data for 00000000000191 (Banco do Brasil)
  • Which IT procurement notices were published in the Southeast in the last 7 days above R$ 500k?
  • Is there an active price registration record with available balance for notebooks in São Paulo state?
  • What does the Juiz de Fora city government plan to buy this year according to the PCA?

Tools 18

search_licitacoes read-only
Search bids by date, modality, state (UF), agency CNPJ, value, or keyword
get_licitacao read-only
Get full details of a bid by its PNCP control number
list_licitacao_itens read-only
List a bid's items (lots): descriptions, quantities, values
list_licitacao_resultados read-only
List dispute results per item: winners, prices, suppliers
list_licitacao_arquivos read-only
Retrieve bid documents (PDFs, attachments, terms of reference)
search_contratos read-only
Search contracts by date, agency, supplier, or value
get_contrato read-only
Get full details of a contract
list_contrato_termos read-only
List contract amendments (extensions, value or term changes)
Show 10 more tools
list_contrato_instrumentos read-only
List billing instruments (invoices, bills)
search_atas_rp read-only
Search price registration records — only active ones by default; finds usable contracts
get_ata_rp read-only
Get full price registration details plus items (with available balance) and files
get_orgao read-only
Public agency profile (branch of government, sphere, legal nature)
get_fornecedor_contratos read-only
Public contracts of a CNPJ acting as a supplier
search_pca read-only
Annual Procurement Plan (PCA) — an early signal of what will be bought
list_pca_itens read-only
Planned items of a specific PCA
get_cnpj_data read-only
Receita Federal company registry data (CNAEs, partners, capital, status) via BrasilAPI (default) or MinhaReceita
aggregate_licitacoes_por_periodo read-only
Time series of bid counts (and optionally values) over a window of up to 5 years, with day/week/month/year bucketing; filters by modality, UF, municipality, CNPJ, and government sphere
compare_periodos read-only
Compare two periods side by side, returning totals plus absolute and percentage deltas

Use cases

Ask which IT bids in the Southeast over R$500k were published in the last 7 days
Check whether an active price registration record (ata de registro de preço) still has balance for a keyword in a given state
Look up a CNPJ's contract history with federal agencies over the past two years
See what a municipality plans to buy this year according to its PCA
Produce a feasibility checklist and summary for a bid
Compare bid counts and values across two periods, e.g. to test whether procurement was front-loaded in an election year

Supported clients

Claude Desktop
Cursor
Continue
Cline
Roo Code
Zed
ChatGPTPartial support

Listed from the project's documentation, not tested by this site.

Overview

The Licinexus MCP Server, maintained by Licinexus and released under the MIT license, is distributed as the npm package @licinexusbr/mcp over stdio. It wraps public endpoints of Brazil's Portal Nacional de Contratações Públicas (PNCP) and Receita Federal CNPJ company registry data into 18 tools, 4 prompts, and 2 resources, letting MCP clients such as Claude Desktop, Cursor, Continue, Cline/Roo Code, and Zed answer natural-language questions about bids, contracts, price registration records (ata de registro de preço), public agencies, annual procurement plans (PCA), supplier contracts, and company registration data. The server returns raw structured public data and leaves analysis to the LLM; it deliberately excludes Licinexus's proprietary matchmaking engine, supplier scoring, or AI-generated artifacts. No API keys, signup, or local database are required — data comes directly from public APIs (PNCP and BrasilAPI, with a CNPJ provider switch via environment variable), and the transport is stdio.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 72ceda9b83ba Data synced 2026-10-19 Read the FMRS scoring method