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 clave de API. |
| veriko_get_public_plan_comparisonA | Compara capacidades y precios públicos sin requerir clave de API. |
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 are mostly distinct: one lists public plans, the other compares capabilities and prices. However, there is potential overlap since a listing might include the same data, and an agent could be unsure whether to use list or comparison for pricing details.
Both tools follow a clear, consistent pattern: a shared 'veriko_' prefix followed by a verb_noun structure (list_public_plans, get_public_plan_comparison). All snake_case and predictable.
With only 2 tools, the set is borderline thin for a public plan API. While the narrow scope may justify a small count, it feels under-provisioned compared to typical 3–15 tool servers.
The surface covers listing and comparison of public plans, which likely satisfies the core read-only use case. A minor gap is the absence of a tool to fetch an individual plan’s full details by ID, though agents could work around it using the comparison tool.