io.github.veriko-mx-labs/veriko
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERIKO_API_KEY | No | API key obtained from app.veriko.mx. Required unless VERIKO_MCP_PROFILE is set to 'plans'. | |
| VERIKO_MCP_PROFILE | No | Operational profile: core, all, a family name, or comma-separated families. Use 'plans' to access public plan tools without an API key. | |
| VERIKO_MCP_MAX_RISK | No | Maximum risk level: read, write (default), or destructive. | write |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| veriko_list_public_plansA | Lista los planes públicos sin requerir API key. |
| veriko_get_public_plan_comparisonA | Compara capacidades y precios públicos sin requerir API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one lists all public plans, the other compares plans' capabilities and prices. There is no realistic confusion between retrieving a list and generating a comparison.
Both tool names follow the same veriko_<verb>_<noun> snake_case pattern, using intuitive verbs 'list' and 'get'. The naming is perfectly consistent across the small set.
Two tools is on the thin side for a standalone server, though the narrow public-plan browsing/comparison scope makes the count understandable. The server feels minimal but not unreasonable.
The server covers the core public-plan workflow: discover plans and compare them. Minor gaps such as fetching details for a single plan or richer pricing breakdowns could exist, but they are not obvious blockers for the stated purpose.