Fan Token Intel MCP server
io.github.BrunoPessoa22/fan-token-intelBrunoPessoa22streamable-httpv1.0.0Scanned
Fan-token intelligence for Chiliz Chain: prices, whale flows, match event impact. 22 read tools.
25 tools: 15 change things and 10 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
15 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Fan Token Intel MCP server can do
The Fan Token Intel MCP server is published by the GitHub account BrunoPessoa22. It has 25 tools. It can create or change data (15 tools: tokenintel_discover, tokenintel_invoke, tokenintel_briefing, tokenintel_token_context and 11 more), but cannot delete data. 10 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
25 tools
Changes things 15Claude Code: ask
tokenintel_briefingAll-in-one ECOSYSTEM briefing: market regime, active signals, anomalies, health matrix, sports calendar, and whale activity in one response.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it All-in-one ECOSYSTEM briefing: market regime, active signals, anomalies, health matrix, sports calendar, and whale activity in one response. Use instead of calling 6+ tools sequentially. USE THIS for a market-wide overview. USE tokenintel_token_context for a SINGLE-TOKEN deep dive (price, signals, health, whale flow, sports catalyst, news — all for one symbol). Returns data, not recommendations -- interpret results yourself.
tokenintel_capital_rotationCross-token capital flow analysis.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Cross-token capital flow analysis. Shows which fan tokens are gaining vs losing volume relative to their recent average. Detects rotation: when whales exit one token, where does the capital go?
tokenintel_discoverDiscover available tools on the Fan Token Intel MCP server.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Discover available tools on the Fan Token Intel MCP server. Returns tool names and one-line descriptions, organized by category. Call with no arguments for all categories, or specify a category to filter. Categories: market_data, signals, sports, social, defi, agent, portfolio, volume, chain_info. Tip: connect with ?modules=market_data,signals to load only specific categories.
tokenintel_event_reaction_profileEvent-conditioned, market-adjusted (vs CHZ) token reaction profiles for football events — by event_type x event_side(for/against) x minute x scoreline_state x importance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Event-conditioned, market-adjusted (vs CHZ) token reaction profiles for football events — by event_type x event_side(for/against) x minute x scoreline_state x importance. Returns mean/median abnormal return, match-clustered t-stat, bootstrap 95% CI, hit rate, decay/persistence, n_events, n_matches, FDR. Omit a dimension to pool. Every cell carries its sample size — descriptive history, not advice.
tokenintel_goal_direction_asymmetryTHE event-impact moat: how a fan token reacts when its team SCORES vs CONCEDES a goal, market-adjusted vs CHZ at +15/+30/+60m.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it THE event-impact moat: how a fan token reacts when its team SCORES vs CONCEDES a goal, market-adjusted vs CHZ at +15/+30/+60m. The blended 'all goals' number hides the real signal — scoring is ~priced-in, conceding moves price. Returns the scored-vs-conceded decomposition with sample sizes and directional hit rates. Only computable here (needs the token<->team map). Descriptive history, not advice.
tokenintel_invokeInvoke any tool on the Fan Token Intel MCP server by name.No findings
Why it is in this group
- The name "tokenintel_invoke" says "invoke": a word for a change.
Description, as the server wrote it Invoke any tool on the Fan Token Intel MCP server by name. Pass the tool_name and its arguments. The result is identical to calling the tool directly. Auth and rate limits apply as normal. Use tokenintel_describe to get the required arguments first.
tokenintel_late_game_redcard_profileRed-card reaction profile (market-adjusted vs CHZ).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Red-card reaction profile (market-adjusted vs CHZ). Rare and high-impact: returns abnormal return at +15/+30/+60m with honest wide confidence intervals and sample size; flags cells with n<15. Descriptive history, not advice.
tokenintel_match_correlationHistorical match-to-price correlation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Historical match-to-price correlation. Ask 'what happens to BAR after Champions League wins?' and get backtested data with price impact percentages. Returns individual match records with price at kickoff, fulltime, +1h, +24h and aggregate stats (avg impact, win rate, best/worst).
tokenintel_match_event_replayEvent-by-event reaction tape for a single match: each goal/red card with its minute, running score, scoreline state, and the market-adjusted token reaction at +15/+30/+60m (plus pr…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Event-by-event reaction tape for a single match: each goal/red card with its minute, running score, scoreline state, and the market-adjusted token reaction at +15/+30/+60m (plus pre-event drift). The non-reconstructable moat artifact. match_id selects that fixture; token (+ optional date) resolves ONE fixture (the date-selected or most recent) and returns its tape, match metadata, and an other_matches index. Events are never merged across fixtures.
tokenintel_match_impact_historyHistorical match price impact data for a fan token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Historical match price impact data for a fan token. Returns price snapshots at -24h, kickoff, fulltime, +1h, +24h with returns for each match. Filter by result (win/loss/draw), competition, venue. WINDOWS: return_total_pct is measured price_24h_before -> price_24h_after (it includes the pregame move, so it can differ in sign from a kickoff-anchored return); return_ko_to_24h_pct is kickoff -> +24h. See the 'semantics' block in the response. Use for backtesting sports-driven strategies.
tokenintel_match_oddsPrediction-market odds curve for a single match from the in-play odds tape (odds_ticks): per-market (home/draw/away) implied-probability series with source labels (polymarket = CLO…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Prediction-market odds curve for a single match from the in-play odds tape (odds_ticks): per-market (home/draw/away) implied-probability series with source labels (polymarket = CLOB midpoint, apifootball = de-vigged bookmaker odds), pre-match vs in-play segmentation against kickoff, and open/close/min/max summary stats per market. Settlement wind-down artifacts (ticks after a market first prints prob >= 0.99, or after full-time +15min) are excluded by default and counted via excluded_settlement_ticks. Curves are downsampled to <=300 points per market (labeled). match_id selects a fixture directly; token (+ optional date) resolves the most recent covered fixture. Use tokenintel_odds_coverage to discover which matches have odds data.
tokenintel_odds_coverageDiscover which matches have prediction-market odds coverage in the in-play odds tape (odds_ticks): per-match tick counts by source (polymarket = CLOB midpoint, apifootball = de-vig…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Discover which matches have prediction-market odds coverage in the in-play odds tape (odds_ticks): per-match tick counts by source (polymarket = CLOB midpoint, apifootball = de-vigged bookmaker odds), in-play tick counts vs kickoff, capture span, live dataset totals (computed from the table, never hardcoded), and upcoming fixtures already mapped for capture. In-play odds are unbackfillable — a match that passed uncaptured stays uncovered. Use tokenintel_match_odds to fetch a covered match's probability curves.
tokenintel_price_candlesHistorical OHLCV price candles for any fan token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Historical OHLCV price candles for any fan token. Intervals: 1h, 4h, 1d. Up to 180 days lookback. Returns open, high, low, close, volume for each period. Use for backtesting, charting, trend analysis, or building your own signals.
tokenintel_social_sentimentSocial sentiment for a fan token.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Social sentiment for a fan token. The only live social source is the LunarCrush aggregated feed, and on the current plan it provides galaxy_score and alt_rank ONLY — sentiment and social_volume come back null (see lunarcrush.fields_unavailable); they are unavailable, not zero. Native X/Twitter ingestion was retired 2026-03-01 and native Reddit/YouTube ingestion has never run in production, so those blocks read 0 — data_sources labels each pipeline (active / no_recent_data / inactive_since_<date> / never_active). overall_sentiment is computed only from sources that actually reported activity and is null when none did. Descriptive community-mood data, not a recommendation.
tokenintel_token_contextSINGLE-TOKEN deep dive: realtime price, CEX whale flow, on-chain Chiliz Chain (FanX) liquidity with slippage at 1%/5% of reserves, and upcoming matches for one symbol.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it SINGLE-TOKEN deep dive: realtime price, CEX whale flow, on-chain Chiliz Chain (FanX) liquidity with slippage at 1%/5% of reserves, and upcoming matches for one symbol. The default tool to call before evaluating a trading decision on a specific token. USE THIS when you have a target token in mind. USE tokenintel_briefing when you want the market-wide overview instead.
Only reads 10Show 10 read-only tools
tokenintel_describeGet the full input schema for a specific tool.No findings
Why it is in this group
- The name "tokenintel_describe" says "describe": a word for reading.
Description, as the server wrote it Get the full input schema for a specific tool. Returns the JSON Schema (parameters, types, required fields, descriptions) needed to call the tool via tokenintel_invoke. Use tokenintel_discover first to find tool names.
tokenintel_dex_depthGet DEX depth and slippage curves for fan token pools on Chiliz Chain.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get DEX depth and slippage curves for fan token pools on Chiliz Chain. Computes constant-product (x*y=k) price impact at trade sizes [1%, 5%, 10%, 25%] of pool reserves. Useful for agents evaluating execution costs before trading. Data from latest on-chain liquidity snapshots.
tokenintel_dex_liquidityGet on-chain DEX liquidity data for fan tokens on Chiliz Chain.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get on-chain DEX liquidity data for fan tokens on Chiliz Chain. Returns pool TVL, depth, token reserves, and estimated slippage. Critical for agents that want to understand execution costs before trading on-chain.
tokenintel_governance_validatorsList active validators on Chiliz Chain governance.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it List active validators on Chiliz Chain governance. Shows validator addresses and total CHZ delegated to each. Use this to find the best validator before staking.
tokenintel_health_matrixGet health grades (A-F) for all tracked fan tokens.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get health grades (A-F) for all tracked fan tokens. Each token is scored across trading volume, order-book liquidity, spread, holder distribution and price stability -- 5-pillar weighted: volume(25%) + liquidity(25%) + spread(20%) + holders(15%) + price_stability(15%). The grade is the token's percentile standing WITHIN the fan-token universe (A=top 10%, B=next 20%, C=middle 40%, D=next 20%, F=bottom 10%); health_score stays the absolute 0-100 pillar score. A pillar whose collector delivered no data is excluded and the remaining weights are renormalized (see missing_pillars), never scored as 0. Use this to quickly filter which tokens deserve attention relative to their peers. Detailed mode (default) includes the per-pillar sub-scores; pass response_format='concise' to get just symbol/grade/score/change (~70% smaller) when you don't need team/league/volume/age detail.
tokenintel_macro_contextGet current crypto macro context: BTC dominance, CHZ price, funding rates, fear & greed index, and risk environment assessment.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get current crypto macro context: BTC dominance, CHZ price, funding rates, fear & greed index, and risk environment assessment.
tokenintel_market_regimeGet current market conditions — BTC trend, CHZ momentum, fear/greed index, and the platform's market regime classification.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get current market conditions — BTC trend, CHZ momentum, fear/greed index, and the platform's market regime classification. Useful for filtering or adjusting signal confidence based on macro conditions.
tokenintel_realtime_pricesGet the freshest available prices with staleness metadata.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get the freshest available prices with staleness metadata. Returns price_age_seconds so agents know exactly how stale each price is. Lightweight and fast -- call this before any trade decision to get current prices. Supports multiple tokens in a single call.
tokenintel_registerGet a free Fan Token Intel API key, self-serve — no human in the loop.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get a free Fan Token Intel API key, self-serve — no human in the loop. Provide a name, an email, and terms_accepted=true; the key (ti_live_...) comes back in the response along with your tier and rate limits. Free-tier keys unlock the whole read-only data layer, event-impact tools included (60 req/min). Pass the key as 'Authorization: Bearer ti_live_xxx' (HTTP) or the TOKENINTEL_API_KEY env var (stdio). Rate-limited to one registration per 10 minutes per caller.
tokenintel_whale_flowsGet real-time whale distribution data for a fan token.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get real-time whale distribution data for a fan token. Shows the ratio of whale sells to total whale activity on CEX exchanges. sell_ratio = whale sell volume / total whale volume; the payload labels >0.65 'distribution' and <0.35 'accumulation' (descriptive labels, not a signal). Data aggregated from CEX exchanges in real-time. USE THIS for aggregate buy/sell pressure on CEX. USE tokenintel_whale_trades for individual trade rows. USE tokenintel_dex_whales for on-chain (Chiliz Chain) swap whales.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp-production-f681.up.railway.app/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp-production-f681.up.railway.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp-production-f681.up.railway.app/mcp: tools/list returned 25 tools to an anonymous client, including tokenintel_discover (write), tokenintel_invoke (write), tokenintel_briefing (write), tokenintel_token_context (write), tokenintel_price_candles (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fan-token-intel https://mcp-production-f681.up.railway.app/mcpclaude mcp add --transport http fan-token-intel https://mcp-production-f681.up.railway.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__fan-token-intel__tokenintel_describe",
"mcp__fan-token-intel__tokenintel_register",
"mcp__fan-token-intel__tokenintel_health_matrix",
"mcp__fan-token-intel__tokenintel_market_regime",
"mcp__fan-token-intel__tokenintel_macro_context",
"mcp__fan-token-intel__tokenintel_realtime_prices",
"mcp__fan-token-intel__tokenintel_whale_flows",
"mcp__fan-token-intel__tokenintel_governance_validators",
"mcp__fan-token-intel__tokenintel_dex_depth",
"mcp__fan-token-intel__tokenintel_dex_liquidity"
],
"ask": [
"mcp__fan-token-intel__tokenintel_discover",
"mcp__fan-token-intel__tokenintel_invoke",
"mcp__fan-token-intel__tokenintel_briefing",
"mcp__fan-token-intel__tokenintel_token_context",
"mcp__fan-token-intel__tokenintel_price_candles",
"mcp__fan-token-intel__tokenintel_social_sentiment",
"mcp__fan-token-intel__tokenintel_capital_rotation",
"mcp__fan-token-intel__tokenintel_match_impact_history",
"mcp__fan-token-intel__tokenintel_match_correlation",
"mcp__fan-token-intel__tokenintel_goal_direction_asymmetry",
"mcp__fan-token-intel__tokenintel_event_reaction_profile",
"mcp__fan-token-intel__tokenintel_late_game_redcard_profile",
"mcp__fan-token-intel__tokenintel_match_event_replay",
"mcp__fan-token-intel__tokenintel_match_odds",
"mcp__fan-token-intel__tokenintel_odds_coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as fan-token-intel. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.BrunoPessoa22/fan-token-intel/verify?hash=598d6d9dc2149dac6db6d120ec8bd6a430cff17d835b046e548152fd2e9ce1a0" | jq -e '.changed == false'Pinned hash 598d6d9dc214, from Nov 15, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.BrunoPessoa22/fan-token-intel/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.BrunoPessoa22/fan-token-intel)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:14 UTC.
Fan Token Intel MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fan Token Intel MCP server safe?
- No scan can promise that. What its definitions show: 25 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Fan Token Intel MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fan Token Intel MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Fan Token Intel MCP server have?
- 25 tools: 15 write, 10 read. tokenintel_discover, tokenintel_invoke, tokenintel_briefing, tokenintel_token_context, tokenintel_price_candles, tokenintel_social_sentiment, tokenintel_capital_rotation, tokenintel_match_impact_history and 17 more.
Does the Fan Token Intel MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fan Token Intel MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fan Token Intel MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.