haia-trace-mcp
by 0x0shephard
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| --dir | No | Path to the Trace root directory containing events/, templates/ and the guard review log. Resolved to its real path once; every run file, template and review log must resolve inside it. | .trace |
| --http | No | Serve Streamable HTTP instead of stdio, e.g. --http 127.0.0.1:3000. Binding is loopback-only unless --http-allow-remote is passed. | |
| --auth-jwks | No | Path to a local JWKS file used to verify RS256/ES256 bearer tokens. No network call is made; the operator provides the file. | |
| --auth-scope | No | Scope that a bearer token must carry, e.g. trace:read. Can be given multiple times. | |
| --public-url | No | The externally visible resource URL used as the expected token aud when behind TLS termination, e.g. https://host/mcp. | |
| --auth-issuer | No | OAuth 2.1 authorization server issuer; bearer tokens must carry this as their iss claim. Required when --http is used. | |
| --guard-config | No | Path to the guard policy file (haia-guard.config.json). Every key in that file is optional; the documented defaults apply when it is omitted. The config is never re-read while the server runs. | |
| --templates-dir | No | Directory of custom receipt templates, subject to the same real-path and symlink rules as --dir. | |
| --auth-hmac-secret | No | Path to an HS256 secret file for token verification, intended for a local authorization server only. | |
| --http-allow-remote | No | Allow the HTTP transport to bind a non-loopback address. | false |
| --http-insecure-no-auth | No | Disable token verification on the HTTP transport, for the MCP Inspector. Refused when not bound to loopback. | false |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |