SnapKitty MCP Server
OfficialAllows chatting with local Ollama models, with responses WORM-sealed for verifiable integrity.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SnapKitty MCP Server Generate an Ada contract for cross-chain governance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@snapkitty/mcp-server
Sovereign-grade MCP server for SnapKitty Collective.
Exposes SnapKitty's core capabilities as MCP tools — callable from Claude, any MCP client, or directly via npx.
Tools
Tool | What it does |
| Seal any payload into the SHA-256 WORM chain |
| Read and verify the WORM chain |
| Create a sovereign agent manifest (SENTINEL/ORACLE/BUILDER/ARCHIVIST/BERSERKER) |
| Generate an Ada-syntax governance contract, WORM-sealed |
| Chat with a local Ollama model, response WORM-sealed |
| Generate a Mamba SSM injection spec from Lean 4 theorem + Ada contract |
Related MCP server: math-logic-mcp
Install
npm install -g @snapkitty/mcp-serverClaude Desktop config
{
"mcpServers": {
"snapkitty": {
"command": "snapkitty-mcp"
}
}
}Claude Code config (.mcp.json)
{
"mcpServers": {
"snapkitty": {
"command": "npx",
"args": ["@snapkitty/mcp-server"]
}
}
}Requirements
Node.js 20+
Ollama running locally (for
twin_chat— optional, other tools work offline)
Architecture
The sovereign_inject tool implements the BOB/METATRON architecture:
Lean 4 theorem ──┐
├──→ injection_vector (2048-dim) ──→ SSM state gate
Ada contract ──┘ h(t) = ā·h(t-1) + b̄·x(t) + W·v_injectStructured symbolic proofs are embedded into SSM hidden state directly — bypassing the context window. The proof gate fires before state advances. Invalid proofs block state transitions.
Sovereign Stack
Built by SnapKitty Collective | collectivekitty.com
Available Tools
6 toolsada_contract_generateB
Generate an Ada-syntax sovereign governance contract for an agent. Defines permitted capabilities, trust level, and WORM-seals the contract.
Inputs: agent_name (required), agent_class (required), purpose, trust_level, +1 more.
agent_buildC
Create a sovereign agent manifest with class, capabilities, model binding, and WORM seal. Classes: SENTINEL, ORACLE, BUILDER, ARCHIVIST, BERSERKER.
Inputs: name (required), agent_class (required), model, capabilities.
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.
Inputs: ada_contract (required), lean4_theorem (required), label.
twin_chatA
Chat with a local Ollama model as a sovereign digital twin. Response is WORM-sealed. Requires Ollama running locally.
Inputs: prompt (required), model, ollama_host, system_prompt.
worm_readB
Read and optionally verify the SnapKitty WORM chain. Returns recent events and chain validity.
Inputs: last_n, verify.
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.
Inputs: label (required), payload (required), meta.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Hosted MCP server for live Bittensor chain reads and self-custodial on-chain writes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Cardano blockchain data — exposes on-chain queries, address lookups, transaction history, token metadata, stake pool info, and network parameters to LLM agents.4MIT
- AlicenseAqualityDmaintenanceMCP server that gives small LLMs verified symbolic-math & logic tools.62Apache 2.0
- AlicenseCqualityDmaintenanceMCP server enabling LLMs to interact with a Cardano node by wrapping cardano-cli/torsten-cli, supporting queries, transactions, staking, and governance operations.64MIT
- FlicenseBqualityDmaintenanceAn MCP server that provides LLMs with access to 95 tools covering the Koios Cardano blockchain REST API, enabling queries for on-chain data like transactions, addresses, assets, and governance.923-