| FMRS | 46 / 100 · D | 77 / 100 · B |
|---|
| Reliability | 6 / 20 | 12 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 16 / 20 |
|---|
| Documentation | 12 / 20 | 18 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 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
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training 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
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
|
|---|
| 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 HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
|
|---|
| 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
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
|
|---|
| Supported clients | Claude Desktop, Cursor, Continue, Cline, Roo Code, Zed, ChatGPT | Claude Desktop, Cursor, Codex, Antigravity |
|---|
| Tools | 18 | 26 |
|---|