io.github.omer907/melt-mcp-server
NPM · @THEMELT/MCP-SERVER · SCANNED SEP 20
Melt: value-leak discovery and lead capture for Claude, Cursor, and MCP-compatible agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1047 tokens (~349/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.omer907/melt-mcp-server server?
io.github.omer907/melt-mcp-server runs locally as an npm package, launched with npx -y @themelt/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @themelt/mcp-server
claude mcp add omer907-melt-mcp-server -- npx -y @themelt/mcp-server
{
"mcpServers": {
"omer907-melt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@themelt/mcp-server"
]
}
}
} {
"servers": {
"omer907-melt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@themelt/mcp-server"
]
}
}
} codex mcp add omer907-melt-mcp-server -- npx -y @themelt/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"omer907-melt-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@themelt/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add omer907-melt-mcp-server --command npx --arg -y --arg @themelt/mcp-server
mcp_servers:
omer907-melt-mcp-server:
command: "npx"
args: ["-y", "@themelt/mcp-server"] {
"McpServers": {
"omer907-melt-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@themelt/mcp-server"
]
}
}
} assistant mcp add omer907-melt-mcp-server -t stdio -c npx -a -y @themelt/mcp-server
{
"mcpServers": {
"omer907-melt-mcp-server": {
"command": "npx",
"args": [
"-y",
"@themelt/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.77 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −1
- Stability: pass → 0.90 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@themelt/mcp-server@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
melt_analyze_value_vectors Analyze AI Value Vectors ~399
Estimates where AI/software value is most likely leaking out of a single department, based on headcount, labor cost, and the type of chaotic/unstructured input it processes manually today. Use this when a tech leader asks where value is being lost or where AI would create the most immediate impact in their org, before any real data integration exists — this is Melt's free Stage-1 Sandbox estimate. Output is directional, from synthetic/self-reported inputs, not an audited figure — for a real finding tied to an actual system log, follow up with melt_request_scan. Also answers what earlier Melt materials called 'AI ROI leverage' or 'AI value vectors' — same estimate, older name.
| Name | Type | Req | Description |
|---|---|---|---|
| averageHourlyLaborCost | number | – | Blended fully-loaded hourly labor cost for manual processors in this unit, in USD. Default of 45 is a reasonable US mid-market planning assumption if the caller doesn't know the real figure. |
| departmentType | string | yes | The organizational unit being evaluated. Must be one of: Operations, Finance, Engineering, Legal, GBS, Customer Success. Map loosely-named teams to the closest primitive (e.g. RevOps -> Operations, A… |
| headcount | number | yes | Total operational personnel in the target unit (not the whole company). Must be positive. |
| primaryUnstructuredDataInput | string | yes | The dominant chaotic input the unit processes by hand today. Must be one of: PDF_INVOICES, CUSTOMER_TICKETS, LOGISTICS_DOCUMENTS, MANUAL_EXCEL. Choose the closest match: PDF_INVOICES for document-fir… |
No output schema declared.
No examples provided.
melt_estimate_annual_leak Estimate Annual Value Leak ~391
Quantifies a specific, already-identified value-leak pattern in dollars per year — e.g. reps bypassing a coaching tool's summaries, manual overrides corrupting a forecasting model, a manual handoff between two systems. Use this when a leak pattern and its rough volume/rate are already known or hypothesized. This mirrors Melt's real scan methodology (see the fintech case study: a 29% Gong bypass rate, a 62% Clari override rate, and a 4.2-day manual handoff combined into a $77,235/yr finding) — it is a directional estimate from self-reported numbers, not a scan against real system logs. For an audited figure, follow up with melt_request_scan. Covers what earlier Melt materials called 'Feature Waste Dollar Amount' (money leaking on licensed-but-unused software) and general 'AI ROI leverage' calculations — those are older names for this same value-leak math, not a different tool.
| Name | Type | Req | Description |
|---|---|---|---|
| leakDescription | string | yes | Plain-language description of the leak pattern observed or hypothesized — e.g. 'reps bypassing Gong call summaries and logging notes from memory', 'manual Slack handoff between Sales and Customer Suc… |
| leakRatePct | number | yes | Percentage of that volume exhibiting the leak behavior, between 0 and 100 (e.g. 29 for a 29% bypass rate, 62 for a 62% override rate). |
| totalVolume | number | yes | Total annual volume of the relevant event or transaction — e.g. total call briefs generated, total deals closed, total support tickets, total lead assignments. |
| valuePerEvent | number | yes | Dollar value at risk per leaking event, in USD — e.g. average deal value, loaded hourly cost of manual rework, cost of a delayed handoff day. |
No output schema declared.
No examples provided.
melt_request_scan Request a Melt Scan ~257
Submits a request for a Melt scan — the next step after Melt's free Stage-1 Sandbox estimate, moving to a real, log-verified value-leak finding tied to a dollar figure and a source system. Call this only after the user has explicitly asked to be connected with Melt or to book/request a scan — never submit contact details the user hasn't provided themselves. Earlier Melt materials called this a 'Thermal Scan' — same request, current name is just 'a scan' (no fixed 2-week/pricing claim attached anymore).
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The prospect's company name. Needed to route the request — if omitted, the tool asks for it instead of failing schema validation. |
| contactEmail | string | – | Business email of the requester, for scan scheduling follow-up. Needed to route the request — if omitted, the tool asks for it instead of failing schema validation. |
| contactName | string | – | Name of the requester, if known. |
| departmentsOfInterest | array | – | Departments the requester wants scanned first, if they expressed a preference. |
| notes | string | – | Any free-text context from the conversation that would help a Melt rep prep the call — trigger event, tech stack, urgency. |
No output schema declared.
No examples provided.
What is the io.github.omer907/melt-mcp-server server?
io.github.omer907/melt-mcp-server is listed in the public MCP registry as io.github.omer907/melt-mcp-server. Melt: value-leak discovery and lead capture for Claude, Cursor, and MCP-compatible agents. This page covers its npm package (@themelt/mcp-server).
Is the io.github.omer907/melt-mcp-server server safe to use?
io.github.omer907/melt-mcp-server scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.omer907/melt-mcp-server server expose?
io.github.omer907/melt-mcp-server exposes 3 tools: melt_analyze_value_vectors, melt_estimate_annual_leak, melt_request_scan. Their descriptions and schemas cost roughly 1,047 tokens of context every time the server is loaded.
Is the io.github.omer907/melt-mcp-server server still maintained?
io.github.omer907/melt-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.omer907/melt-mcp-server server under?
io.github.omer907/melt-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.