Alpaca Trading API integration for Model Context Protocol (MCP)
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Crypto fundamentals, sentiment, whale tracking and influencer call accuracy for traders and agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http onvexia-crypto-fundamentals-sentiment-onchain-mcp https://onvexia.com/mcp
# 2 — ask your agent for something these tools do
# get_asset, get_asset_scores, get_asset_fundamentals and 63 more
Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http onvexia-crypto-fundamentals-sentiment-onchain-mcp https://onvexia.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
66 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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 sec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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 compute
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
| limit | integer | no | — |
The assets with the strongest Galaxy Score right now. Galaxy Score is 0-100 and composite: social volume, engagement, sentiment and market health folded together. A high score is a statement about ATTENTION AND HEALTH, not about valuation — it does not mean an asset is cheap. Call get_asset_scores for the breakdown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
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 separ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | — |
Rank what the market is TALKING ABOUT — themes and narratives, not assets. Ranked by mentions weighted by engagement over the window, so a topic posted about loudly by few accounts does not outrank one discussed widely. Use get_trending_assets for tickers; this is the layer above, where "restaking" and "AI agents" live.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | — |
| limit | integer | no | — |
Recent large on-chain transfers, optionally filtered to one asset. "Whale" is a SIZE threshold, not an identity. A large transfer is very often an exchange moving its own funds between wallets, which is not a market action at all — counterparty labels are included where we hold them, and a null label means WE HAVE NO LABEL, never that the counterparty is un
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| symbol | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
Get an influencer's track record. view picks one of three records: accountability (default) — did their calls precede the move (Predictor) or react to it (Reactor)? Hit rate and track record. accuracy — did their price calls come true? Hit rate over 30/90/180 days at 24h, 7d and 30d, with the Wilson lower bound and excess over BTC. calls — the receipt
| Parameter | Type | Required | Notes |
|---|---|---|---|
| influencer_id | string | yes | — |
| view | string | no | — |
| horizon_hours | integer | no | — |
The influencer leaderboard, ranked by what people actually got RIGHT rather than by how loud they are. rank_by="accountability" (default): scored Predictor vs Reactor — did the call come before the move, or after it. rank_by="accuracy": ranked by how often their price calls came true, by the Wilson lower bound of the hit rate (>= 20 resolved calls to rank),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rank_by | string | no | — |
| window_days | integer | no | — |
| horizon_hours | integer | no | — |
Search the whole asset universe (~1,900 assets) by symbol or name. Use this to resolve a user's loose reference into a real symbol before calling the other tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
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.
No parameter schema on file.
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.
No parameter schema on file.
Every chain an asset is deployed on, with its contract address and token decimals.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
Identify a blockchain address — exchange, bridge, DEX, MEV bot, mining pool, or OFAC-sanctioned — with the source and confidence of each label. IMPORTANT: known: false means no label is held. It does NOT mean the address is clean or unflagged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | — |
Browse labelled addresses, filtered by chain, entity (e.g. Binance) or category (exchange | bridge | dex | mev | staking | mining | sanctioned).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| chain | string | no | — |
| entity | string | no | — |
| category | string | no | — |
| limit | integer | no | — |
List every metric Onvexia knows, with its parity and caveats. parity=exact means we compute it the way Santiment does; approximate means same concept but different coverage or method (read the caveat before relying on the number); unavailable means we do NOT serve it yet. Unavailable metrics are listed on purpose — check here before asserting that Onvexia c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| available_only | boolean | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | yes | — |
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".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | yes | — |
| asset | string | yes | — |
| from_date | string | no | — |
| to_date | string | no | — |
| interval | string | no | — |
| aggregation | string | no | — |
Whale flow per labelled entity over the window. Inflow to an exchange is distribution pressure; outflow is accumulation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hours | integer | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | yes | — |
| assets | string | yes | — |
| from_date | string | no | — |
| to_date | string | no | — |
| interval | string | no | — |
Latest value of MANY metrics for ONE asset in a single call. metrics is comma-separated. The mirror of get_metric_timeseries_multi.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metrics | string | yes | — |
| asset | string | yes | — |
Filter the whole asset universe server-side and return the matches. filter is comma-separated field:op:value terms, e.g. "market_cap:gt:1000000000,funding_rate:lt:0" — assets over $1B whose funding rate is negative. Ops: gt, gte, lt, lte, eq, ne. Call screener_fields() first to see what fields exist and their ranges; guessing a field name gets the whole
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filter | string | no | — |
| sort | string | no | — |
| limit | integer | no | — |
Every field the screener accepts, with type and description. Call this before building a filter rather than guessing field names.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
| limit | integer | no | — |
Assets trending now by social activity, with the hype score that separates a real move from a burst of noise.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| asset | string | yes | — |
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
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
Current narratives, each an LLM summary of a CLUSTER of posts rather than a single document. Read author_count before quoting one: a high post_count with a low author_count is one person repeating themselves, not a narrative. These are machine summaries, not edited articles.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
List the assets that currently have a generated research report available. Returns the index, not the reports — call get_research_report with a symbol for the body. An asset missing from this list has not been written up; that is a statement about our coverage, not about the asset.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
Does a bare ticker actually mean the crypto asset? verdict 'crypto' means mentions are about the asset; 'equity'/'other' means the bare word is dominated by something else (TIA is Spanish 'tia'; GRT collides with 'graph'). A 404 is NOT a clean bill of health — it means nobody has adjudicated that ticker yet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| band | integer | no | — |
Previously compiled natural-language screens: the English somebody wrote and the filter it compiled to, INCLUDING refusals. Useful as worked examples of the screener's filter grammar before you write one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Run a read-only SELECT against the platform's data. One statement, 15s timeout, 10,000-row cap; truncation is always reported. Call get_sql_schema first for the queryable relations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
List every relation and column queryable via run_sql, plus the rules and what is deliberately not exposed.
No parameter schema on file.
Bitcoin supply split by coin age over time — which cohorts are holding and which are moving.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Per-token flow onto and off exchanges. Inflow is distribution pressure, outflow is accumulation. net_usd where the token can be priced.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Asset co-mention graph — which assets are discussed together, with what was filtered out.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Collected social posts, optionally filtered by platform (bluesky, farcaster, reddit, 4chan, bitcointalk, rss).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | — |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| post_id | integer | yes | — |
Per-asset social signal over time. The available field states plainly whether we hold it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | yes | — |
| days | integer | no | — |
Restatements of published numbers — what changed, over which period, and why. A correction is not a market move.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| min_liquidity_usd | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
What we index per chain for watched addresses: what we see, what we miss, and what an empty feed actually means.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| story_id | integer | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| include_legacy | boolean | no | — |
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. Thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
Cross-wrapper spread for tokenized equities: one real company, every issuer that tokenizes it, and how far apart they trade. SpaceX trades under five wrappers and they do not agree. Spreads run roughly 0.1-0.9 percent between programs referencing the same share. This is a CROSS-WRAPPER comparison, deliberately not a comparison against the underlying stock
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
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:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | — |
| limit | integer | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.9.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Onvexia — Crypto Fundamentals, Sentiment & Onchain Tracking can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.