SnapKitty MCP Server
OfficialServer 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| worm_sealB | Seal any payload into the SnapKitty WORM chain with SHA-256. Every event is chained to the previous seal — tamper-evident, append-only. |
| worm_readB | Read and optionally verify the SnapKitty WORM chain. Returns recent events and chain validity. |
| agent_buildC | Create a sovereign agent manifest with class, capabilities, model binding, and WORM seal. Classes: SENTINEL, ORACLE, BUILDER, ARCHIVIST, BERSERKER. |
| ada_contract_generateB | Generate an Ada-syntax sovereign governance contract for an agent. Defines permitted capabilities, trust level, and WORM-seals the contract. |
| twin_chatA | Chat with a local Ollama model as a sovereign digital twin. Response is WORM-sealed. Requires Ollama running locally. |
| sovereign_injectC | Generate a Mamba SSM injection specification from a Lean 4 theorem and Ada contract. This is the BOB orchestrator architecture: structured symbolic proofs injected into SSM state, bypassing the context window. |
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 6 tools
Each tool has a clear and distinct purpose: contract generation, agent building, SSM injection, twin chat, and WORM chain operations. No overlapping functionalities.
Most tools follow a [noun]_[verb] pattern (e.g., twin_chat, worm_read), but ada_contract_generate uses [noun_noun_verb] and sovereign_inject uses [adjective_noun_verb], introducing slight inconsistency.
With 6 tools, the server is well-scoped for its domain (contracts, agents, SSM injections, chat, and WORM chain). Not too many or too few.
Covers core operations (create, read, seal) for contracts, agents, and WORM chain. Minor gaps like missing update/delete for agents or contracts, but not critical for the intended use.