FipeX MCP vs Licinexus MCP
A side-by-side look at the FipeX MCP and Licinexus MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose FipeX MCP for finance & fintech work over a hosted endpoint; choose Licinexus MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose FipeX MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Licinexus MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_licitacoes, get_licitacao, list_licitacao_itens.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 54/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16 | 80 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 18 |
| Full listing | View FipeX MCP | View Licinexus MCP |
Tools & capabilities
FipeX MCP tools
No tool names declared yet. Check the project README from the listing page.
Licinexus MCP tools 18
search_licitacoesSearch Brazilian public procurement bids (licitações) on PNCP. PNCP requires a date range and at least one modality code per query. If you do not specify, defaults are: last 7 days and modalities [6, 8, 9] (Pregão Eletrônico, Dispensa, Inexigibilidade — most common). Maximum date range per query: 365 days (PNCP limit). Wider windows return HTTP 422. For multi-year searches, issue multiple calls with date windows of <= 365 days each. Modality codes: 1 = Leilão - Eletrônico 2 = Diálogo Competitivo 3 = Concurso 4 = Concorrência - Eletrônica 5 = Concorrência - Presencial 6 = Pregão - Eletrônico 7 = Pregão - Presencial 8 = Dispensa de Licitação 9 = Inexigibilidade 10 = Manifestação de Interesse 11 = Pré-qualificação 12 = Credenciamento 13 = Leilão - Presencial Filters palavraChave, valorMinimo, valorMaximo are applied client-side over the page returned by PNCP.get_licitacaoGet the full details of a single licitação (procurement bid) on PNCP. Provide either numeroControlePNCP (the full PNCP control number string) or all three of orgaoCnpj, ano, sequencial.list_licitacao_itensList the items (lots) of a licitação on PNCP. Each item has description, quantity, unit, estimated unit value and category. Provide either numeroControlePNCP, or orgaoCnpj/ano/sequencial.list_licitacao_resultadosList the bidding results (winners, runners-up, prices, suppliers) for a specific item of a licitação. You must specify which item — use list_licitacao_itens first to discover item numbers.list_licitacao_arquivosList the files (edital PDFs, attachments, terms of reference) attached to a licitação on PNCP. Returns metadata and direct URLs — does not download the file content.search_contratosSearch public procurement contracts (contratos) on PNCP. Useful for analyzing market history, supplier behavior, and agency spending patterns. Defaults to last 30 days when no date range is provided. Maximum date range per query: 365 days (PNCP limit); wider windows return HTTP 422. For multi-year searches, issue multiple calls.get_contratoGet the full details of a public contract on PNCP. Provide either numeroControlePNCP or orgaoCnpj/ano/sequencial.list_contrato_termosList the additive terms (termos aditivos) of a contract — extensions, value increases/reductions, term changes. Useful to understand contract evolution.list_contrato_instrumentosList billing instruments (NFes, faturas) attached to a contract. Reveals real execution: when payments were due, NFe keys, etc.search_atas_rpSearch Atas de Registro de Preço (price-registry agreements) on PNCP. ARPs are pre-negotiated agreements that any compatible agency can use within the validity period — finding ones still in vigor with available balance is a key business opportunity. Defaults: last 90 days, only active (somenteVigentes=true). Maximum date range per query: 365 days (PNCP limit); wider windows return HTTP 422.get_ata_rpGet the full details of an Ata de Registro de Preço, optionally including its items (with available balance and supplier info) and attached files. Use orgaoCnpj/anoCompra/sequencialCompra (the parent procurement) and sequencialAta (the ARP within that procurement).get_orgaoGet a public agency's profile from PNCP: legal name, branch of government (poder), federal/state/municipal level (esfera), legal nature, address.- +6 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
FipeX MCP
{
"mcpServers": {
"fipex-mcp": {
"command": "npx",
"args": [
"-y",
"fipex-mcp"
]
}
}
}
Licinexus MCP
{
"mcpServers": {
"mcp-199": {
"command": "npx",
"args": [
"-y",
"@licinexusbr/mcp"
]
}
}
}
Frequently asked questions
FipeX MCP is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Licinexus MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick FipeX MCP for finance & fintech work and Licinexus MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
FipeX MCP has no declared pricing — check the project's own site. Auth: no auth required. Licinexus MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fipex-mcp and mcp-199 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FipeX MCP has a quality signal of 54/100 (Good) with 1 views, 0 installs and 16 GitHub stars. Licinexus MCP has 65/100 (Great) with 5 views, 0 installs and 80 GitHub stars.