ComparEdge Price Watch
NPM · @COMPAREDGE/PRICE-WATCH-MCP · SCANNED SEP 20
Dated log of SaaS, AI and crypto price changes: recent moves, history, biggest increases.
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1212 tokens (~242/item across 5 items; 5 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 Management90
- Stability observed for 27 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the ComparEdge Price Watch MCP server?
ComparEdge Price Watch runs locally as an npm package, launched with npx -y @comparedge/price-watch-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @comparedge/price-watch-mcp
claude mcp add imkemit-ops-comparedge-price-watch -- npx -y @comparedge/price-watch-mcp
{
"mcpServers": {
"imkemit-ops-comparedge-price-watch": {
"command": "npx",
"args": [
"-y",
"@comparedge/price-watch-mcp"
]
}
}
} {
"servers": {
"imkemit-ops-comparedge-price-watch": {
"command": "npx",
"args": [
"-y",
"@comparedge/price-watch-mcp"
]
}
}
} codex mcp add imkemit-ops-comparedge-price-watch -- npx -y @comparedge/price-watch-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"imkemit-ops-comparedge-price-watch": {
"type": "local",
"command": [
"npx",
"-y",
"@comparedge/price-watch-mcp"
],
"enabled": true
}
}
} openclaw mcp add imkemit-ops-comparedge-price-watch --command npx --arg -y --arg @comparedge/price-watch-mcp
mcp_servers:
imkemit-ops-comparedge-price-watch:
command: "npx"
args: ["-y", "@comparedge/price-watch-mcp"] {
"McpServers": {
"imkemit-ops-comparedge-price-watch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@comparedge/price-watch-mcp"
]
}
}
} assistant mcp add imkemit-ops-comparedge-price-watch -t stdio -c npx -a -y @comparedge/price-watch-mcp
{
"mcpServers": {
"imkemit-ops-comparedge-price-watch": {
"command": "npx",
"args": [
"-y",
"@comparedge/price-watch-mcp"
]
}
}
} 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 +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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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 +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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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/@comparedge/price-watch-mcp@1.0.0
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
biggest_increases ~226
Rank the largest plan price increases across the catalog over a window, by percent, with the dollar change alongside. BEHAVIOR: Looks at plan_price_change entries where the new price is higher than the old, computes the percent and absolute increase, and returns the top movers. Decreases and new-plan additions are excluded. Sorted by percent increase, with the dollar delta in parentheses. USAGE GUIDELINES: - Use when the user asks "who raised prices?", "biggest price hikes lately", or is watching for cost creep in their stack. - Widen days for a broader sweep; narrow it to focus on the most recent moves. - Use product_changes to drill into any single product from the list. EXAMPLE QUERIES: "Which tools raised prices the most this quarter?", "Biggest SaaS price increases recently", "Show me the top 10 price hikes"
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look back this many days (default: 90) |
| limit | number | – | How many increases to return (default: 10, max: 50) |
No output schema declared.
No examples provided.
category_changes ~256
List recent pricing and plan changes within one category, newest first, and name the products that moved most in the window. BEHAVIOR: Filters the changelog to a category slug over the last N days, returns the newest changes, and highlights the most active products. Good for spotting a category-wide pricing trend. USAGE GUIDELINES: - Use when the user scopes to a market: "what is happening with cloud hosting prices?", "recent CRM plan changes". - Category slugs are lowercase and hyphenated, e.g. "cloud-hosting", "llm", "crm", "email-marketing", "crypto-exchanges". - Use recent_changes for a catalog-wide view, or biggest_increases to rank hikes. EXAMPLE QUERIES: "What changed in cloud hosting lately?", "Recent LLM pricing changes", "Any movement in email marketing plans this quarter?"
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category slug (e.g. "cloud-hosting", "llm", "crm", "crypto-exchanges") |
| days | number | – | Look back this many days (default: 90) |
| limit | number | – | Maximum number of changes to list (default: 30, max: 100) |
No output schema declared.
No examples provided.
check_price ~224
Report a product's current pricing (plans, starting price, free plan, token pricing) together with its most recent recorded changes. BEHAVIOR: Reads the live pricing feed for the named product and lists its plans, starting price, billing model, and any per-token pricing, then appends the last few changelog entries for that product and the date it was last verified. One call answers "what does it cost now, and has it moved lately?". USAGE GUIDELINES: - Use when the user wants the current price of one tool, optionally with recent history. - The slug is the ComparEdge url form: lowercase, hyphenated. - Use product_changes when the user wants the full history rather than the current snapshot. EXAMPLE QUERIES: "What does Notion cost right now?", "Current Vercel pricing and any recent changes", "How much is Bluehost and did it go up?"
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Product slug in ComparEdge url form (e.g. "notion", "vercel", "bluehost") |
No output schema declared.
No examples provided.
product_changes ~241
Show the full recorded change history for one product by slug, newest first, including every price move, plan addition, and plan removal on file. BEHAVIOR: Filters the changelog to a single product and lists each dated change. Reports how many of those were price changes. Use this to see how a tool's pricing has drifted over time. USAGE GUIDELINES: - Use when the user names one product: "how has Notion pricing changed?", "has Vercel raised prices?". - The slug is the ComparEdge url form: lowercase, hyphenated (Notion -> "notion", GitHub Copilot -> "github-copilot"). - Use check_price when the user wants the current price rather than the history. EXAMPLE QUERIES: "Has Notion changed its pricing?", "Show me Bluehost price history", "What plan changes has Linear made?"
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of history entries to show (default: 50, max: 200) |
| slug | string | yes | Product slug in ComparEdge url form (e.g. "notion", "github-copilot") |
No output schema declared.
No examples provided.
recent_changes ~265
List the most recent verified pricing and plan changes across the whole ComparEdge catalog, newest first, with a per-type tally of the window. BEHAVIOR: Returns changes from the last N days: price moves, plans added or removed, renames, and billing-model switches. Each line shows the date, product, and what changed. A short tally (plan_price_change: 12, plan_added: 4, ...) summarizes the window so you can gauge activity before reading detail. USAGE GUIDELINES: - Use when the user asks "what changed recently?", "any SaaS price moves this week?", or "what is new in pricing?". - Widen days when the window looks quiet; the catalog does not change every day. - Use category_changes to scope to one category, or product_changes for a single tool. - Use biggest_increases when the user cares specifically about price hikes. EXAMPLE QUERIES: "What pricing changed in the last week?", "Any recent SaaS price changes?", "Show me the 30 most recent plan changes"
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look back this many days (default: 30) |
| limit | number | – | Maximum number of changes to list (default: 20, max: 100) |
No output schema declared.
No examples provided.
What is the ComparEdge Price Watch MCP server?
ComparEdge Price Watch is an MCP server listed in the public MCP registry as io.github.imkemit-ops/comparedge-price-watch. Dated log of SaaS, AI and crypto price changes: recent moves, history, biggest increases. This page covers its npm package (@comparedge/price-watch-mcp).
Is the ComparEdge Price Watch MCP server safe to use?
ComparEdge Price Watch scores 82 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 ComparEdge Price Watch MCP server expose?
ComparEdge Price Watch exposes 5 tools: recent_changes, product_changes, category_changes, biggest_increases, check_price. Their descriptions and schemas cost roughly 1,212 tokens of context every time the server is loaded.
Is the ComparEdge Price Watch MCP server still maintained?
ComparEdge Price Watch 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 ComparEdge Price Watch MCP server under?
ComparEdge Price Watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.