StratVerity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stratverity_quick_checkA | Static quick diagnostic of a strategy excerpt (look-ahead, repainting, overfitting). Never executes the code. |
| stratverity_verify_hashB | Verify the authenticity of a sealed audit proof by its SHA-256 hash. |
| stratverity_get_badgeD | Generate the embeddable badge URL for an audit. |
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 clearly distinct function: quick_check performs static diagnostics, verify_hash authenticates proofs, and get_badge generates badge URLs. There is no overlap or ambiguity between them.
All tools share the stratverity_ prefix and snake_case style, but quick_check uses an adjective-noun pattern while verify_hash and get_badge follow verb_noun. This is a minor deviation from an otherwise consistent convention.
Three tools is at the lower end but appropriate for the server's narrow audit-verification purpose. Each tool earns its place and the set is well-scoped without unnecessary bloat.
The core workflow is covered: run a quick diagnostic, verify a sealed proof, and generate a badge. A minor gap is the lack of a way to retrieve audit details or history, but agents can work around this for the main use cases.