43
/ 100
24 days ago
npm

Jayden-Siete/Limitrum

MCP server exposing Limitrum policy verification as an agent tool.

Jayden-Siete/Limitrum· npm: @limitrum/mcp-server· listed on npm
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.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: DATABASE_AUTH_TOKEN, GITHUB_TOKEN, LIMITRUM_API_KEY, LIMITRUM_GATEWAY_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
🔐 secretDATABASE_AUTH_TOKEN
configDATABASE_URL
🔐 secretGITHUB_TOKEN
🔐 secretLIMITRUM_API_KEY
configLIMITRUM_API_URLLocal HTTP verification gateway compatible with
configLIMITRUM_DB_PATH
🔐 secretLIMITRUM_GATEWAY_API_KEYSet on the gateway to require X-Limitrum-API-Key or Authorization: Bearer ....
configLIMITRUM_MCP_AGENT_ID"": "agent_local"
configMCP_TRANSPORT
configPORT
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 1 concrete improvement 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/limitrum-mcp-server-43bqpg)](https://m8ven.ai/mcp/limitrum-mcp-server-43bqpg)
commit: f6c352b3fbb266abe4968f7d8f98302d658f5398
code hash: da98981f40a68fcf583acb62f9b96e793c35058057d4f7081236161e5583f7da
verified: 7/7/2026, 10:05:08 AM
view raw JSON →