melt-ai/melt-mcp-server (melt-ai/melt-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 3 tools. The publisher has proved control of what we score (Verified Publisher). It is connected through the M8ven GitHub App, so the listing is re-checked on every push.

Back to MCP Trust IndexM8ven
B
Emerging
89/100
13 days ago

melt-ai/melt-mcp-server

Melt MCP server — value-leak discovery and lead capture for Claude, Cursor, and any MCP-compatible agent

→ melt-ai/melt-mcp-server· npm: @themelt/mcp-server

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 VerifiedSandbox Verified⚡ Live Monitored

Monitored 14 days · every push re-verified

Who stands behind it

themelt.ai (@melt-ai) · Verified Publisher

Source: github_app_install · also listed on Glama

Install from

GitHubGlama

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

// key findings
✅
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: MCP_HTTP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
Are you the publisher? Confirm or correct these findings.
// 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.
🔐 secretMCP_HTTP_API_KEYAuth is opt-in via (unset by default): with it unset, the
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

3/3 tools missing one or more hints — melt_analyze_value_vectors (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); melt_estimate_annual_leak (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); melt_request_scan (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

Domain consistency

npm scope @themelt doesn't match GitHub owner melt-ai

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/melt-ai/melt-mcp-server)](https://m8ven.ai/mcp/melt-ai/melt-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: dbfea5474aa12cc0b93c5a7dfd9685c4246c1726
code hash: 864adf6b4f4630958da8ac555220995c079cf1ca6a912f17d5acd1fa690adcfe
verified: 8/27/2026, 8:41:31 PM
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