sovereign-stack (templetwo/sovereign-stack) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 128 tools. No publisher has claimed this listing.

C
Emerging
74/100

sovereign-stack

MCP server for AI memory, governance, and continuity across session-death. A self-verifying chronicle: honest on write, on read, on reach, and about itself — a failed write can't report success, a partial answer can't pass as complete, and the capability surface is generated from the live registry, not typed. 100% local.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

templetwo

Source: Glama · also listed on github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
8 flows detected: BRIDGE_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: BRIDGE_TOKEN, SOVEREIGN_BRIDGE_TOKEN, STACK_TOKEN, ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSOVEREIGN_ROOT
configSOVEREIGN_MEMORY
configSOVEREIGN_CHRONICLE
configPROBE_TIMEOUT_SECONDS
configPROBE_ON_CONNECT
configSOVEREIGN_BRIDGE_URL
🔐 secretBRIDGE_TOKEN
configGROK_BRIDGE_SCHEMA_TTL_SECONDS
configOPENAI_BRIDGE_SCHEMA_TTL_SECONDS
configGUARDIAN_ROOT
configGUARDIAN_ISOLATE_ROOTS
configPOST_FIX_HTTP_ALLOW
configSSE_CONNECT_BURST
configSSE_CONNECT_PER_MIN
configCLAUDE_MCP_BURST
configCLAUDE_MCP_PER_MIN
configCLAUDE_OAUTH_BURST
configCLAUDE_OAUTH_PER_MIN
configSSE_ALLOW_UNAUTHENTICATED
configSSE_BINDING_MAX_SESSIONS
configSOVEREIGN_BIN
configSOVEREIGN_SOURCE_INSTANCE
configCLAUDE_DOOR_BASE_URL
configCLAUDE_ELEVATION_TTL
configCLAUDE_ACCESS_TOKEN_TTL
configCLAUDE_REFRESH_TOKEN_TTL
configCLAUDE_MAX_REGISTERED_CLIENTS
configCLAUDE_MAX_OAUTH_BODY_BYTES
configCLAUDE_BRIDGE_ISSUER
configCLAUDE_ALLOW_LOOPBACK_REDIRECT
configSOVEREIGN_LOG_LEVEL
🔐 secretSOVEREIGN_BRIDGE_TOKEN
configPYTEST_CURRENT_TEST
🔐 secretSTACK_TOKEN
configSTACK_URL
configOLLAMA_API_URL
🔐 secretANTHROPIC_API_KEY
configSYNTHESIS_MODEL
configSYNTHESIS_FOCUS
configSYNTHESIS_HOURS
configSYNTHESIS_MAX
configSYNTHESIS_SAMPLE_MODE
configSYNTHESIS_SPAN_WEEKS
configSYNTHESIS_ENTRIES_PER_WEEK
configSCRIBE_BOOT_INJECTPer-instance Haiku 4.5 scribe spawned on every where_did_i_leave_off. Read-only, redaction-gated, ephemeral per session. Reads the chronicle alongside the arriving instance and answers ask_scribe with a cited response + stats footer. redactor.py strips credentials before anything reaches Haiku; encounter.py writes notes attributed to scribe-haiku-4-5. Injects the SCRIBE — OPTIONAL boot block (kill switch SCRIBE_BOOT_INJECT=off).
configSCRIBE_BOOT_GREETING
configSCRIBE_MODEL
configSCRIBE_GREETING_MAX_TOKENS
configSCRIBE_MAX_TOKENS
configANTHROPIC_API_KEY_SCRIBE
configSCRIBE_CONTEXT_TTL_MINUTES
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

128/128 tools missing one or more hints — route (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); derive (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); scan_thresholds (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +125 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

94/128 tools referenced in tests (73%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

8 secrets sent to a request target we could not resolve (BRIDGE_TOKEN → dynamic, BRIDGE_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets never reach shell commands

1 secret value passed to a subprocess as an argument — no shell is invoked, so there is nothing to inject into

Never pass secrets through shell commands. Use library APIs that accept credentials as arguments.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/templetwo/sovereign-stack)](https://m8ven.ai/mcp/templetwo/sovereign-stack)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5b330297d9f8f23ff3cea90e9e8a279736ee3f34
code hash: a82a28cef65256268bacc1039e77b1df4686f16278df64a63b02b93fe9574310
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client