Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking
REMOTE · ONVEXIA.COM · SCANNED SEP 20
Crypto fundamental analysis, sentiment and whale tracking for traders and AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5868 tokens (~88/item across 66 items; 66 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 66 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 67 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
How do I install the Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server?
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking is a hosted endpoint at https://onvexia.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · onvexia.com
claude mcp add --transport http com-onvexia-onvexia 'https://onvexia.com/mcp'
{
"mcpServers": {
"com-onvexia-onvexia": {
"url": "https://onvexia.com/mcp"
}
}
} {
"servers": {
"com-onvexia-onvexia": {
"type": "http",
"url": "https://onvexia.com/mcp"
}
}
} [mcp_servers.com-onvexia-onvexia] url = "https://onvexia.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-onvexia-onvexia": {
"type": "remote",
"url": "https://onvexia.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-onvexia-onvexia --url 'https://onvexia.com/mcp' --transport streamable-http
mcp_servers:
com-onvexia-onvexia:
url: "https://onvexia.com/mcp" {
"McpServers": {
"com-onvexia-onvexia": {
"Transport": "http",
"Url": "https://onvexia.com/mcp"
}
}
} assistant mcp add com-onvexia-onvexia -t streamable-http -u 'https://onvexia.com/mcp'
{
"mcpServers": {
"com-onvexia-onvexia": {
"type": "http",
"url": "https://onvexia.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 71
First indexed and scored.
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 · Probed https://onvexia.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onvexia.com | CN=WE1,O=Google Trust Services,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | cf6c8888d78d5f141384ab2effcf4603 |
| SANs: onvexia.com, *.onvexia.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of onvexia.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onvexia.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'self'; img-src 'self' data: https://static.alchemyapi.io https://coin-images.coingecko.com https://assets.coingecko.com; connect-src 'self' https://xhhltbldmmksbjiefuay.supabase.co wss://xhhltbldmmksbjiefuay.supabase.co; style-src 'self' 'unsafe-inline' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onvexia.com/mcp | Verified | 200 | |
| http (plaintext) | http://onvexia.com/mcp | HTTPS enforced | 301 | https://onvexia.com/mcp |
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 →
analyze_sentiment Sentiment · Score arbitrary text ~96
Score any text for crypto sentiment, tuned for crypto slang and tickers. Takes arbitrary text you supply — it does not look anything up. General sentiment models read "this is going to zero" and "wagmi" badly; this one is fitted to the register. Returns polarity plus the terms that drove it, so a score can be checked rather than trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
get_address_coverage Coverage · Addresses ~35
What we index per chain for watched addresses: what we see, what we miss, and what an empty feed actually means.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_address_events On-chain · Address events ~46
Events on watched addresses. Check get_address_coverage before reading an empty result as silence — below the observed USD floor, movement is invisible to us.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_agent_findings Agents · Findings ~67
What this platform's own monitoring agents are currently complaining about — dead collectors, stale data streams, coverage drops. Worth checking before relying on a number: a stream flagged stale here is still being served, it is just old.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_ai_substance Signal integrity · AI substance ~189
Does an AI-sector project actually ship code, against how much attention it gets. Four states, and the fourth is not a verdict: ships public repo with development activity in 30 days silent public repo, no activity in 30 days no_public_repo no repository is published for this asset unmapped WE have not checked. This is a gap in OUR coverage and must NEVER be reported as the project failing to ship. RENDER sat in this state with 447 posts while publishing code the whole time. `dev_events_30d` is null rather than 0 for the last two states: there is no repository to have produced a zero. `attention_without_substance` is only ever set where the state was actually measured.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_aspect_sentiment Sentiment · By aspect ~80
Split an asset's sentiment by what people are actually talking about: technology, price, team and community. The aggregate can be flat while the parts disagree sharply — bullish on technology, bearish on team is a different situation from uniformly neutral, and only this tool can tell them apart.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
No output schema declared.
No examples provided.
get_asset Assets · Profile ~90
An asset's core profile by symbol: name, category and cross-system identifiers (CoinGecko id, contract addresses, chains). Start here when you have a ticker and need to be sure which asset it refers to. Tickers collide across chains — if the symbol is ambiguous, resolve_ticker is the tool that says so instead of guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_fundamentals Fundamentals · Full brief ~207
Get the full fundamental brief for an asset: market snapshot, supply and valuation, project, TVL, revenue, treasury, security, governance, unlock schedule, derivatives positioning, competitive rank, valuation ratios and a graded scorecard — in one call. READ THE SECTION STATES, NOT ONLY THE VALUES. Each section is `measured`, `not_held` or `failed`, and sections the asset class cannot have are returned separately in `not_applicable`. "This chain has no DAO treasury" and "we could not read it" are different facts and this response keeps them apart. Revenue is split: `S06` is the entity's own fees, `S06b` is the total earned by protocols deployed on a chain. The two can differ by two orders of magnitude and only the first accrues to the token.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_platforms Assets · Contract addresses ~35
Every chain an asset is deployed on, with its contract address and token decimals.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_revisions Assets · Revision history ~59
Metrics for this asset that CHANGED after they were first published, with the old value, the new one and why. An agent that quoted an earlier number can find out here that it moved.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_scores Scores · Asset breakdown ~105
An asset's Galaxy Score and AltRank, with the components behind each. Galaxy Score is a composite of social and market health on a 0-100 scale; AltRank is relative standing against the rest of the universe, where 1 is best. READ THE COMPONENT BREAKDOWN — a score moved by sentiment and one moved by volume mean different things, and the composite alone cannot tell you which happened.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_social_signal Social · Asset signal ~44
Per-asset social signal over time. The `available` field states plainly whether we hold it.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_asset_technicals Fundamentals · Technical levels ~199
Get support and resistance merged across 1w/1d/4h/1h, per-timeframe indicators, and derived spot/long/short setups for an asset. Each level carries the timeframes that confirmed it and the method on each — a level agreed by four charts is a different claim from one seen on the hourly. `measured_against` names the exchange and pair every distance was computed from, and `price_age_minutes` says how old that price is. Setups are GEOMETRY, not forecasts: an entry is a level cluster, a stop is that level offset by a measured multiple of daily range, and `rr_ratio` is computed from those prices. `status` is derived per request — pending, in_zone or passed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_bot_detections Signal integrity · Bot detections ~154
Accounts flagged as automated or coordinated, with the behavioural evidence. Volume from these should not be read as organic attention. READ `coverage` AND `note` BEFORE YOU READ THE LIST. No scorer is currently running, so `bot_probability` is NULL for every account and this list comes back EMPTY. An empty list here says nothing whatsoever about how clean the corpus is — it means nobody has been scored yet, and the response says so explicitly in `note`. `coverage.accounts_scored` vs `accounts_total` is the honest number: while the first is 0, treat this tool as reporting our coverage, not the market's cleanliness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_chain_coverage Coverage · Chains ~58
Per-chain coverage — tokens mapped, labelled addresses, whale transactions seen, and how many were attributed to a named entity. Attribution is Etherscan-derived, so it is strong on Ethereum and sparse on other chains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_constellation On-chain · Entity graph ~34
Asset co-mention graph — which assets are discussed together, with what was filtered out.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_coordinated_campaigns Signal integrity · Coordinated campaigns ~50
Detected coordinated posting campaigns — the same message pushed by multiple accounts. Matching is exact-text, so this catches copypasta and misses the same campaign reworded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_correlation Analytics · Social-price correlation ~86
How closely an asset's social activity tracks its price, with the lead/lag. Correlation is not causation and this endpoint does not claim it is. A high coefficient says the two series moved together over the window — it does not say which one moved first. Use get_leading_indicators for that question.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_creator_rankings Scores · Creator rankings ~84
Rank social creators across the whole corpus by measured influence. Corpus-wide, unlike get_influencers which is scoped to one asset. Influence is computed from engagement our collectors actually observed, so a creator we do not ingest is absent rather than ranked low — an absence here is a coverage fact, not a judgement.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_data_coverage Coverage · Data ~61
What data this platform actually holds right now: asset count, how many are priced, chains covered, labelled addresses, social corpus size, and freshness timestamps. Call this to check whether an answer is supportable before asserting it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_disclosures Fundamentals · Public disclosures ~235
Public-record documents about issuers we track: SEC filings and federal court dockets. Exists because both RWA failures of 2026 were disclosed in public text before the price moved -- RealT's tax delinquency sat in court filings for a year, Goldfinch's borrower defaults were in governance forums before the vote. TWO THINGS YOU MUST NOT MISREPORT: A null `severity` means the document was FOUND and NOT ASSESSED. It is unjudged, not benign, and must never be summarised as "nothing concerning". `match_confidence: name_unverified` means the document was matched on a NAME and may concern a different company entirely -- searching for 'RealT' returns 'Broadway White Realty'. Do not attribute an unverified filing to an issuer without checking it. An empty result means nothing has been found, which for a subject never searched is not a statement about them at all.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_emerging_dex_pairs Market · Emerging DEX pairs ~98
Newly created DEX pairs above a USD liquidity floor. THE FLOOR IS RETURNED IN THE RESPONSE, and it is load-bearing: this is the long tail where most pairs are rugs or noise, and the floor is the only thing separating a signal from a list of scams. Raising it shrinks the result set and raises its quality.
| Name | Type | Req | Description |
|---|---|---|---|
| min_liquidity_usd | integer | – | – |
No output schema declared.
No examples provided.
get_entities Assets · Entities ~52
Named entities extracted from social documents about an asset — people, organisations, products and other tickers mentioned alongside it. Use it to find what a narrative is actually about.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
No output schema declared.
No examples provided.
get_entity_flows On-chain · Entity flows ~49
Whale flow per labelled entity over the window. Inflow to an exchange is distribution pressure; outflow is accumulation.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_exchange_flows On-chain · Exchange flows ~92
Net movement of an asset into and out of exchange wallets. Inflows are supply arriving somewhere it can be sold; outflows are supply leaving to self-custody. The conventional reading is distribution vs accumulation, but a single large transfer can be an exchange rebalancing its own wallets — check get_entity_flows before attributing intent.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | – | – | – |
No output schema declared.
No examples provided.
get_exchange_listings Market · Exchange listings ~77
Recent exchange listing announcements — an asset being added to a venue. A listing is an ATTENTION event, not a fundamental one: it changes who can buy, not what the project is worth. Use it to explain a volume or social spike, not as a valuation input.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_exchange_netflow On-chain · Exchange netflow ~46
Per-token flow onto and off exchanges. Inflow is distribution pressure, outflow is accumulation. net_usd where the token can be priced.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_hodl_waves On-chain · HODL waves ~37
Bitcoin supply split by coin age over time — which cohorts are holding and which are moving.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_influencer_leaderboard Influencer ledger · Leaderboard ~82
The influencer accountability leaderboard, ranked by what people actually got RIGHT rather than by how loud they are. Each entry is scored Predictor vs Reactor: did the call come before the move, or after it. This is the flagship differentiator — reach and accuracy are different axes, and most rankings only publish the first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_influencer_ledger Influencer ledger · Track record ~55
Get an influencer's accountability record: did their calls precede the move (Predictor) or react to it (Reactor)? Includes hit rate and track record.
| Name | Type | Req | Description |
|---|---|---|---|
| influencer_id | string | yes | – |
No output schema declared.
No examples provided.
get_influencers Social · Influencers by asset ~88
The accounts driving conversation about one asset, by reach and engagement. Ranked by measured activity in our corpus, NOT by follower count, and NOT by whether they were right — see get_influencer_ledger for track record. A large account posting noise ranks here; that is the point of keeping the two tools separate.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
No output schema declared.
No examples provided.
get_leading_indicators Analytics · Leading indicators ~91
Which social and on-chain signals have historically MOVED FIRST for an asset. This is the lead/lag question that get_correlation deliberately does not answer. A lead measured over a past window is not a forecast and the response does not present it as one — it is the observed ordering of two series, and it can break.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_metric_metadata Metrics · Metadata ~91
Describe one metric before you use it: parity, category, minimum interval and any caveat attached to it. CALL THIS BEFORE get_metric_timeseries if the metric is unfamiliar. The minimum interval tells you the finest resolution that is real rather than interpolated, and the caveat is where an approximate metric admits what it approximates.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | – |
No output schema declared.
No examples provided.
get_metric_revisions Metrics · Revisions ~42
Restatements of published numbers — what changed, over which period, and why. A correction is not a market move.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_metric_timeseries Metrics · Timeseries ~131
Timeseries for any available metric on any asset. Accepts Santiment-style relative dates ("utc_now-7d") as well as ISO timestamps. If the metric is not available this returns an error naming it rather than an empty series — an empty result here always means "no data in that range", never "we do not have this metric".
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string | – | – |
| asset | string | yes | – |
| from_date | string | – | – |
| interval | string | – | – |
| metric | string | yes | – |
| to_date | string | – | – |
No output schema declared.
No examples provided.
get_metric_timeseries_multi Metrics · Timeseries (multi-asset) ~113
Timeseries for ONE metric across MANY assets in a single call. `assets` is comma-separated (e.g. "BTC,ETH,SOL"). Prefer this over looping get_metric_timeseries — it is one round trip instead of N, and the values are guaranteed to come from the same read.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | string | yes | – |
| from_date | string | – | – |
| interval | string | – | – |
| metric | string | yes | – |
| to_date | string | – | – |
No output schema declared.
No examples provided.
get_metrics_batch Metrics · Batch ~53
Latest value of MANY metrics for ONE asset in a single call. `metrics` is comma-separated. The mirror of get_metric_timeseries_multi.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| metrics | string | yes | – |
No output schema declared.
No examples provided.
get_narrative_clusters Narrative · Clusters ~64
The raw clusters behind the stories, without the prose — for a model doing its own summarisation. Every cluster has >= 2 distinct authors; near-identical posts from one account are copypasta and excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_narrative_rotation Narrative · Rotation ~234
Which crypto narrative is GAINING or LOSING attention share, with a liquidity confirmation leg. Compares the last `days` against the equally long window immediately before. Covers the 2026 narrative set — RWA, tokenized equities and treasuries, stablecoins, DePIN, perp DEXs, prediction markets, AI agents — as well as DeFi, NFT, Gaming and the L1/L2 split. READ `vocabulary_stale` BEFORE QUOTING ANY DELTA. When true, the corpus spans two keyword vocabularies and a narrative whose keywords were just added will appear to be rising purely because only recent posts were ever tested against them. That is a rotation signal manufactured by a deploy, not by the market. A narrative with `unconfirmed: true` has measured attention and NO liquidity confirmation — the confirmation is absent, not zero, and the row states why.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| include_legacy | boolean | – | – |
No output schema declared.
No examples provided.
get_ohlcv Market · OHLCV ~91
Daily candles (open/high/low/close/volume) for an asset, with the venue they came from. Coverage is bounded by which assets have a USDT pair on Binance or Bybit — an asset absent here has no candle source we collect, which is not the same as having no price.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
get_research_report Research · Report ~66
One asset's generated report. The `unavailable` field lists metrics the report could NOT use — read it, because a report that silently omits funding rate reads as a report about an asset with unremarkable funding.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_sentiment_trends Sentiment · Trends ~85
Sentiment over time for an asset, with sample size and confidence interval. IMPORTANT: sentiment measured on few documents is unreliable — our own bootstrap put the direction wrong 35.6% of the time at n=1 and 9.5% at n=20. Read n before quoting a direction.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
No output schema declared.
No examples provided.
get_signal_integrity Signal integrity · Real-vs-fake score ~59
Get the Signal Integrity score (0-100) — is the move real or exit liquidity? Fuses social authenticity + on-chain reality + fundamental backing, with an Exit Liquidity Radar flag.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | – |
No output schema declared.
No examples provided.
get_similar_posts Social · Similar posts ~56
Posts nearest a given post in embedding space. Read the returned BAND, never the raw cosine — 43% of this corpus sits at 0.80-0.90 by default.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | integer | yes | – |
No output schema declared.
No examples provided.
get_social_coverage Coverage · Social ~80
How many assets actually clear the document floor that makes each social metric computable. Call this BEFORE quoting sentiment for an asset. A large corpus total does not mean sentiment works everywhere: attention is a power law and the documents pile onto BTC, so most assets stay uncomputable.
| Name | Type | Req | Description |
|---|---|---|---|
| band | integer | – | – |
No output schema declared.
No examples provided.
get_social_dominance Social · Share of conversation ~106
Each asset's SHARE of total social attention over a window, with the posts, distinct authors, engagement and sentiment behind the share. Share is relative and sums across the universe, so an asset's dominance can fall while its absolute volume rises — that is the market getting louder, not the asset getting quieter. Distinct authors is the column that separates a real conversation from one account posting 400 times.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
No output schema declared.
No examples provided.
get_social_posts Social · Posts ~53
Collected social posts, optionally filtered by platform (bluesky, farcaster, reddit, 4chan, bitcointalk, rss).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
get_sql_schema SQL · Schema ~30
List every relation and column queryable via run_sql, plus the rules and what is deliberately not exposed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_story_posts Narrative · Story sources ~73
The individual posts a story was assembled from — the receipts. Call this whenever a story matters enough to check. A generated story is a summary over these posts; this is how you verify it says what the sources say rather than taking the summary on trust.
| Name | Type | Req | Description |
|---|---|---|---|
| story_id | integer | yes | – |
No output schema declared.
No examples provided.
get_top_altranks Scores · Top by AltRank ~83
The assets ranked best by AltRank right now — relative standing, not absolute. AltRank is a RANK: 1 is the strongest in the universe. A rising AltRank in a falling market means outperforming the fall, not going up. Pair with get_asset_scores when the distinction matters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server?
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking is an MCP server listed in the public MCP registry as com.onvexia/onvexia. Crypto fundamental analysis, sentiment and whale tracking for traders and AI agents. This page covers its hosted endpoint (https://onvexia.com/mcp).
Is the Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server safe to use?
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking scores 73 out of 100 on VerifyMCP. 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 Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server expose?
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking exposes 66 tools: get_asset, get_asset_scores, get_asset_fundamentals, get_asset_technicals, get_top_galaxy_scores, and 61 more. Their descriptions and schemas cost roughly 5,644 tokens of context every time the server is loaded.
Does the Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server require authentication?
No. We connected to Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking MCP server still maintained?
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking 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.