mcp-server-creem (Selenium39/mcp-server-creem) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 19 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

mcp-server-creem

MCP server for Creem.io providing tools to manage subscriptions, products, payments, license keys, and more through the Creem API.

→ Selenium39/mcp-server-creem· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

Selenium39

Source: Glama

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
⚠️
Known vulnerabilities in dependencies: 15 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: CREEM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes19 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

create_product

Create a new product in Creem. Products can be one-time payments or recurring subscriptions.

get_product

Retrieve details of a specific product by ID

search_products

Search and list all products

create_checkout

Create a checkout session for a product. Returns a checkout URL to redirect customers to.

get_checkout

Retrieve checkout session details by ID

get_customer

Retrieve customer details by email or customer ID

list_customers

List all customers

create_customer_portal_link

Generate a customer portal login link for a customer to manage their subscriptions

get_subscription

Retrieve subscription details by ID

cancel_subscription

Cancel an active subscription

update_subscription

Update subscription (e.g., change number of seats/units)

upgrade_subscription

Upgrade or downgrade a subscription to a different product

activate_license

Activate a license key for a specific instance/device

deactivate_license

Deactivate a license key instance

validate_license

Validate if a license key is active and valid

create_discount

Create a discount code

get_discount

Retrieve discount code details

delete_discount

Delete a discount code

search_transactions

Search and list transactions

// known CVEs in dependencies15 high5 medium10 low

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

high@modelcontextprotocol/sdk@1.0.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.7.2GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.7.2GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.7.2GHSA-43fc-jf86-j433

Axios is Vulnerable to Denial of Service via __proto__ Key in mergeConfig

highaxios@1.7.2GHSA-4hjh-wcwx-xvwj

Axios is vulnerable to DoS attack through lack of data size check

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.
🔐 secretCREEM_API_KEY(required): Your Creem API key
configCREEM_TEST_MODE(optional): Set to true to use test mode (default: false)
// 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

19/19 tools missing one or more hints — create_product (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_product (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_products (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +16 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.0.4 (high), axios@1.7.2 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

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 4 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/selenium39/mcp-server-creem?variant=verified)](https://m8ven.ai/mcp/selenium39/mcp-server-creem)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 1c104b780e35bbb0e84d797da86e63fe4aecf868
code hash: 8e73f4bf46a98dd9b2bf0291d16b9df9308cc31e49547794de5c1f70da79c778
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