sanction (ericlovold/sanction) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 10 tools. No publisher has claimed this listing.

C
Emerging
74/100

sanction

Agent wallet, credential vault, and governance layer for autonomous AI agents

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

ericlovold

Source: github_repo_search

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
1 flow detected: SANCTION_SLACK_BOT_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 10 credentials: APPLE_CLIENT_SECRET, GITHUB_CLIENT_SECRET, GOOGLE_CLIENT_SECRET, RESEND_API_KEY, SANCTION_API_KEY, SANCTION_CREDENTIAL_ENCRYPTION_KEY, SANCTION_SIGNING_SECRET, SANCTION_SLACK_BOT_TOKEN, SANCTION_SLACK_CLIENT_SECRET, SANCTION_SLACK_SIGNING_SECRET
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.
configAPPLE_CLIENT_ID
🔐 secretAPPLE_CLIENT_SECRET
configBETTER_AUTH_URL
configDATABASE_URL_UNPOOLED
configDIRECT_URL
configEMAIL_FROM
configGITHUB_CLIENT_ID
🔐 secretGITHUB_CLIENT_SECRET
configGOOGLE_CLIENT_ID
🔐 secretGOOGLE_CLIENT_SECRET
configLEADS_NOTIFY_TO
🔐 secretRESEND_API_KEY
🔐 secretSANCTION_API_KEY
configSANCTION_API_URL
🔐 secretSANCTION_CREDENTIAL_ENCRYPTION_KEY
configSANCTION_KMS_KEY_ARN
configSANCTION_PUBLIC_ORIGIN
🔐 secretSANCTION_SIGNING_SECRET
🔐 secretSANCTION_SLACK_BOT_TOKEN
configSANCTION_SLACK_CLIENT_ID
🔐 secretSANCTION_SLACK_CLIENT_SECRET
🔐 secretSANCTION_SLACK_SIGNING_SECRET
configSANCTION_WALLET_ID
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployNEXT_PUBLIC_BETTER_AUTH_URL
deployNEXT_PUBLIC_CALENDLY_URL
deployPOSTGRES_URL_NON_POOLING
// 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

10/10 tools missing one or more hints — sanction_authorize (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); sanction_authorize_provision (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); sanction_authorize_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 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.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

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 3 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/ericlovold/sanction)](https://m8ven.ai/mcp/ericlovold/sanction)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: f96526bf5c4dfd903a69e2517f466c762cc872db
code hash: 253bc9a8b4b5a978839c8a82ee6999536f257988909969710b2fef21847178da
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