ComparEdge Price Watch
NPM · @COMPAREDGE/PRICE-WATCH-MCP · SCANNED AUG 3
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 →
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 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @comparedge/price-watch-mcp
claude mcp add imkemit-ops-comparedge-price-watch -- npx -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": {
"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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 +34
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 26 Jul 26 47
First indexed and scored.
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 3 Aug 2026 · Analysed npm/@comparedge/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 0 packages
0 packages in the resolved dependency tree.
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.
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.