Home / MCP registry index / com.onvexia/onvexia
Onvexia: Crypto Fundamentals, Sentiment & Onchain Tracking
com.onvexia/onvexia in the official MCP registry.
Endpoint https://onvexia.com/mcp. Source: github.com/faraz152/onvexia-mcp.
The registry describes it as: Crypto fundamentals, sentiment, whale tracking and influencer call accuracy for traders and agents.
We read its 66 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_asset get_asset_scores get_asset_fundamentals get_asset_technicals get_top_galaxy_scores get_top_altranks get_correlation get_leading_indicators get_social_dominance get_topic_rank get_whale_transactions get_exchange_flows get_aspect_sentiment analyze_sentiment get_influencers get_signal_integrity get_influencer_ledger get_influencer_leaderboard search_assets get_data_coverage get_chain_coverage get_asset_platforms lookup_address list_labelled_addresses list_metrics get_metric_metadata get_metric_timeseries get_entity_flows get_metric_timeseries_multi get_metrics_batch screen_assets screener_fields get_ohlcv get_trending_assets get_entities get_sentiment_trends get_bot_detections get_coordinated_campaigns get_creator_rankings get_asset_revisions get_trending_stories get_narrative_clusters list_research_reports get_research_report resolve_ticker get_social_coverage list_nl_screens get_agent_findings run_sql get_sql_schema get_hodl_waves get_exchange_netflow get_constellation get_social_posts get_similar_posts get_asset_social_signal get_metric_revisions get_emerging_dex_pairs get_exchange_listings get_address_coverage and 6 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-onvexia-onvexia)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |