Affixio MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AFFIX_API_KEY | No | Licence key. Defaults to local_operator for offline use. | local_operator |
| AFFIX_API_BASE | No | Override API base. Unset means SDK default. | |
| AFFIX_MCP_HOME | No | State directory. Defaults to ~/.affix-mcp. | ~/.affix-mcp |
| AFFIX_MCP_AGENT_ID | No | Default agent id. | |
| AFFIX_MCP_CURRENCY | No | Currency code. Defaults to GBP. | GBP |
| AFFIX_MCP_MAX_AMOUNT | No | Optional numeric cap. Denies above it. | |
| AFFIX_MCP_ALLOWED_TOOLS | No | Comma-separated list of allowed tools. Empty means any tool may attest. | |
| AFFIX_MCP_BLOCKED_PATTERNS | No | Comma-separated list of blocked argument patterns. Defaults to sk_live_, AKIA, PRIVATE KEY. | sk_live_,AKIA,PRIVATE KEY |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| attest_actionA | Record a local action and return a signed yes-or-no ACTION attestation. PII stays on the host. |
| verify_actionC | Verify a local ACTION attestation and return valid true or false with a reason. |
| gate_tool_callB | Policy gate for one privileged agent tool call. Returns allow or deny plus a signed decision. |
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 3 tools
Each tool targets a distinct stage in the attestation workflow: gating a tool call, recording an action, and verifying an attestation. There is no ambiguity between them, as the verb and noun clearly separate purposes.
All three tool names follow a consistent verb_noun pattern: gate_tool_call, attest_action, verify_action. This makes the naming predictable and easy to reason about.
With only three tools, the server is tightly scoped to its attestation/gating purpose without unnecessary bloat. Each tool serves a necessary role in the workflow.
The tool set covers the full lifecycle of attestation: gating a call, creating an attestation, and verifying it. No obvious gaps exist for the stated domain.