| FMRS | 46 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 6 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 18 / 20 |
|---|
| Documentation | 12 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 14 / 20 |
|---|
| 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
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| 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
| - Users needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| 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
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| 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
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Desktop, Cursor, Continue, Cline, Roo Code, Zed, ChatGPT | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 18 | 11 |
|---|