Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Crypto News Sentiment (x402)

PYPI · CRYPTO-SENTIMENT-X402-MCP

Crypto news sentiment for 24 coins: label, score and headlines behind it, paid per call via x402

−11 this week 58 Trust /100

Last scanned (9 hours ago)

Scores higher than 53% of PyPI servers

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security49
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 9 of 83 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1670 tokens (~238/item across 7 items; 7 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 Management25
  • Stability check failed: the tool surface changed between 0.1.2 and 0.2.0: 3 tool removals, 0 breaking changes, 6 additions. See how to fix → Fail
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +19
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 13 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Package version: 0.1.2 → 0.2.0 functional
  • 11 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 10 Nov 26 −12
    • Stability: 0.83 → fail ▼ security
    • Schema quality: 1247 → 1670 ▼ functional
    • Package version: 0.1.7 → 0.2.0 functional
Diagnostics

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 21 Nov 2026 · Analysed pypi/crypto-sentiment-x402-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 83 packages
Packages resolved 83
Stale 7
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,670 tokens

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 →

Tool Tokens
get_archive_coverage ~140

Free: what the hourly sentiment archive holds (GET /archive). No wallet needed. Per symbol: first and latest reading, row counts, missing hours, and coverage_7d_pct, the share of the last 7 days' logged hours that had at least one matching headline (with hours_with_headlines_7d and hours_logged_7d). Check it before get_sentiment_history to pick a symbol and range with data: low-coverage coins often get no_headlines_in_range from get_sentiment_history or "insufficient recent news" from get_sentiment, both refused and not charged.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_call_price ~236

Free: the live x402 price of one get_sentiment call, read from an unpaid request's 402 response. Nothing is signed; no wallet needed. When not to use it: prices are fixed at $0.01 per get_sentiment call, $0.05 per get_sentiment_history call and $0.02 per get_movers call, so there's no need to call this before every paid call. Use it to confirm the live price and payment requirements, e.g. before funding a wallet. It quotes get_sentiment only. symbol must be exactly one of the 24 uppercase tickers from list_supported_coins; lowercase or any other symbol is rejected by the input schema before a request is sent. A low-coverage coin still gets a quote; a get_sentiment call for it may then be refused with "insufficient recent news" (not charged).

NameTypeReqDescription
symbolstringyesUppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged.

Structured output declared, but exposes no named fields.

No examples provided.

get_market_sentiment ~143

Crypto market sentiment index: one news-sentiment score and bullish/bearish/neutral label for the whole crypto market, aggregated from the 24 supported coins and weighted by how much recent news each has, with the contributing coins listed. Free: no wallet needed. Use when an agent needs the overall crypto news mood rather than one coin's; use get_sentiment for a single coin and get_movers for which coins are shifting. Refreshed at most hourly: cached, computed_at and next_refresh_at in the response say how fresh it is, and a call before next_refresh_at returns the same index.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_movers ~283

Crypto sentiment movers: the coins whose news sentiment rose or fell the most over the last ~24 hours, ranked across all 24 supported coins in one call. Paid: $0.02 in USDC on Base per call, from this MCP server's own CDP wallet. Use when an agent wants to know which coins' news mood is shifting without calling get_sentiment for every coin. Compares each coin's current reading (refreshed at most hourly; computed_at says when) with its archived reading closest to 24 hours earlier. Returns movers_up (rises, largest first) and movers_down (falls, largest first) with each coin's current score, previous score and delta. limit is sent as the ?limit= query parameter and caps movers_up and movers_down each; omit it for 10. Coins without enough recent news, now or ~24 hours ago, are left out. A call that can rank no coin is refused with HTTP 422, returned as an error with charged: false. Without CDP keys or past the session spend cap, it pays nothing and says why.

NameTypeReqDescription
limit––Max coins in movers_up and in movers_down, 1 to 24, e.g. 5. Omit for the API's default of 10.

Structured output declared, but exposes no named fields.

No examples provided.

get_sentiment ~296

Crypto news sentiment for one coin right now: a bullish/bearish/neutral label, a score from -1 to 1, sample sizes, the Fear & Greed value and up to 5 headlines that moved the score. Paid: $0.01 in USDC on Base per call, from this MCP server's own CDP wallet. Use when an agent needs the current news mood for a crypto ticker. Scores headlines from the last 72 hours across 9 crypto news RSS outlets, newest weighted most. Each call fetches and scores the feeds live (no cache), so repeat calls can differ as news arrives. For past readings use get_sentiment_history; for the coins shifting most use get_movers. symbol picks the coin and goes into the request path: one of the 24 uppercase tickers from list_supported_coins. Any other symbol is rejected by the input schema, so nothing is charged. Too few recent headlines: HTTP 422 "insufficient recent news", returned with charged: false (get_archive_coverage shows coverage_7d_pct). Without CDP keys or past the session spend cap, it pays nothing and says why.

NameTypeReqDescription
symbolstringyesUppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged.

Structured output declared, but exposes no named fields.

No examples provided.

get_sentiment_history ~463

Historical crypto news sentiment for one coin: hourly readings (score, sample size, Fear & Greed and the top headlines for each hour), oldest first. Paid: $0.05 in USDC on Base per call, from this MCP server's own CDP wallet. Use when an agent needs how a coin's news sentiment moved over past hours or days, e.g. to line it up with price. For the current reading use get_sentiment. symbol goes into the request path (/history/{symbol}) and start/end are sent as query parameters, so together they pick one coin and one time range. Omit both for the 7 days up to now; with only end the range starts 7 days before it, with only start it runs to now. A reading is included when start <= observed_at < end; at most 30 days per call. Readings are recorded live at the top of each UTC hour and never backfilled. Refused and not charged (an error with charged: false): 400 for a malformed symbol or time, start not before end, or over 30 days; 404 for a symbol not in the archive, no_readings_in_range (gives first_reading) or no_headlines_in_range (no hour had headlines). For low-coverage coins, check get_archive_coverage first. Without CDP keys or past the session spend cap, it pays nothing and says why.

NameTypeReqDescription
end––ISO 8601 timestamp, e.g. 2026-10-13T00:00:00Z (UTC if no offset). start defaults to end minus 7 days; end is exclusive and defaults to now. At most 30 days per call.
start––ISO 8601 timestamp, e.g. 2026-10-13T00:00:00Z (UTC if no offset). start defaults to end minus 7 days; end is exclusive and defaults to now. At most 30 days per call.
symbolstringyesCrypto ticker, e.g. BTC; uppercased and trimmed before the request. get_archive_coverage lists the logged symbols.

Structured output declared, but exposes no named fields.

No examples provided.

list_supported_coins ~109

The 24 crypto tickers (symbol and name) that get_sentiment and get_call_price accept. Free: no wallet needed and no network call. Use when choosing a symbol before calling get_sentiment or get_call_price. The coin list is fixed per release: new coins come with a new version of this package, never while the server runs. Any other symbol is rejected by those tools' input schema before a request is sent, so nothing is charged.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Crypto News Sentiment (x402) MCP server?

Crypto News Sentiment (x402) runs locally as a PyPI package, launched with uvx crypto-sentiment-x402-mcp. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · crypto-sentiment-x402-mcp

# add to Claude Code
claude mcp add whatevercat-creator-crypto-sentiment-x402 -- uvx crypto-sentiment-x402-mcp

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

Common questions

What is the Crypto News Sentiment (x402) MCP server?

Crypto News Sentiment (x402) is an MCP server listed in the public MCP registry as io.github.whatevercat-creator/crypto-sentiment-x402. Crypto news sentiment for 24 coins: label, score and headlines behind it, paid per call via x402. This page covers its PyPI package (crypto-sentiment-x402-mcp).

Is the Crypto News Sentiment (x402) MCP server safe to use?

Crypto News Sentiment (x402) scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Crypto News Sentiment (x402) MCP server expose?

Crypto News Sentiment (x402) exposes 7 tools: get_sentiment, get_sentiment_history, get_movers, list_supported_coins, get_archive_coverage, and 2 more. Their descriptions and schemas cost roughly 1,670 tokens of context every time the server is loaded.

Is the Crypto News Sentiment (x402) MCP server still maintained?

Crypto News Sentiment (x402) is still listed as active in the MCP registry. We last reached this channel on 21 November 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 Crypto News Sentiment (x402) MCP server under?

Crypto News Sentiment (x402) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Crypto News Sentiment (x402) MCP server?

VerifyMCP ran 15 checks on Crypto News Sentiment (x402), covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Crypto News Sentiment (x402): Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.