PrismerCloud (Prismer-AI/PrismerCloud) is an MCP server listed on the M8ven Trust Index. It scores 27 out of 100, grade F. It declares 62 tools. No publisher has claimed this listing.

F
Warning
27/100

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code VerifiedSandbox 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

Prismer-AI

Source: github_topic

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
🚨
Hardcoded credentials detected
3 live-looking API keys in source: 3 OpenAI API key
🔐
You'll be asked for 1 credential: PRISMER_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowtsup@8.0.0GHSA-3mv9-4h5g-vhg3

tsup DOM Clobbering vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configPRISMER_AGENT_USERNAME
🔐 secretPRISMER_API_KEYAPI key (sk-prismer-). Get one at [prismer.cloud](https://prismer.cloud).
configPRISMER_API_KEY_TEST
configPRISMER_BASE_URLAPI base URL.
configPRISMER_DAEMON_PORT
configPRISMER_DAEMON_URL
configPRISMER_IM_AGENT
configPRISMER_LOCAL_DAEMON_URL
configPRISMER_LOCAL_PORT
configPRISMER_MCP_ALLOWLIST
configPRISMER_RUNTIME_PORT
configPRISMER_SCOPE
configPRISMER_WORKSPACE_ID
// 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

62/62 tools missing one or more hints — skill_sync (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); prismer.community.profile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); prismer.task.approve (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +59 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — prismer.skill.uninstall deletes at line 40 (fs.rmSync(c.dir, { recursive: true, force: true }))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

59/61 tool handlers declare input schemas (97%)

Declare an inputSchema with zod/joi/yup on every tool definition.

No hardcoded API keys

3 live-looking API keys in source: 3 OpenAI API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

Only 7/62 tools referenced in tests (11%)

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

Secrets not logged

1 secret value sent to error

Redact or omit secret values from log output.

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 7 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 Verified](https://m8ven.ai/badge/mcp/prismer-ai/prismercloud?variant=verified)](https://m8ven.ai/mcp/prismer-ai/prismercloud)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e263666c231c8782fee9e3cc561a1c6a06b384d3
code hash: ad24e052b24e43e40fd15efa5968a1c09d38c1cb3a8648ce5c5f85780b676a42
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