predict_trending — x402 services MCP Tool
predict_trending
(predict trending) is one of 159 tools on the
x402 services
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call predict_trending from your client
- Claude Code x402 services predict_trending run in your project directory
- Claude Desktop x402 services predict_trending ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor x402 services predict_trending ~/.cursor/mcp.json
- VS Code x402 services predict_trending .vscode/mcp.json
- Zed x402 services predict_trending ~/.config/zed/settings.json
- Windsurf x402 services predict_trending ~/.codeium/windsurf/mcp_config.json
- Cline x402 services predict_trending ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI x402 services predict_trending ~/.gemini/settings.json
- Grok x402 services predict_trending .mcp.json (in your project root)
- ChatGPT x402 services predict_trending Settings → Connectors → Advanced → Developer mode
- Claude.ai x402 services predict_trending Settings → Connectors → Add custom connector
- LangChain x402 services predict_trending pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http x402-services https://x402-services-production.up.railway.app/mcpOther tools on this server
- markdown
- extract
- read
- read_structured
- memory_set
- memory_get
- schedule
- schedule_status
- counter
- lock_acquire
- lock_release
- queue_push
- queue_pop
- idempotency
- pubsub_publish
- pubsub_poll
- board_set
- board_get
- ratelimit
- deadman_register
- deadman_ping
- calc
- datetime
- business_days
- regex
- jsonschema
- diff
- cron_explain
- schedule_cron
- links_check
- inbox_create
- inbox_poll
- wallet_reputation
- crypto_price
- crypto_convert
- crypto_balances
- crypto_gas
- crypto_ens
- crypto_tx
- crypto_token
- crypto_yields
- crypto_activity
- crypto_contract
- snipe_newpairs
- snipe_trending
- snipe_safety
- snipe_honeypot
- snipe_holders
- snipe_pair
- snipe_search
- snipe_wallet
- snipe_impact
- snipe_rh
- rh_stock
- rh_stocks
- rh_premium
- rh_arb
- rh_yields
- rh_tvl
- rh_pool
- rh_gainers
- rh_session_clock
- rh_gap_radar
- rh_liquidity_map
- rh_depth
- rh_spread
- rh_new_listings
- rh_perp_funding
- rh_perp_oi
- rh_basis
- rh_funding_arb
- rh_oracle_deviation
- rh_verify
- rh_dislocation
- rh_momentum
- rh_whale_flow
- rh_funding_scan
- rh_catalysts
- sol_launches
- sol_graduating
- sol_rug_check
- perps_funding
- perps_funding_arb
- perps_basis
- perps_markets
- perps_movers
- perps_oi
- catalysts_unlocks
- catalysts_search
- catalysts_calendar
- catalysts_governance
- exec_quote
- exec_slippage
- exec_sandwich
- exec_gas
- options_greeks
- options_price
- options_chain
- options_maxpain
- options_vol
- predict_odds
- predict_market
- predict_arb
- predict_feargreed
- analytics_price_at
- analytics_indicators
- analytics_ohlcv
- compliance_screen
- compliance_risk
- compliance_label
- compliance_taint
- lending_health
- lending_rates
- agent_reputation
- ai_models
- ai_chat
- ai_chat_pro
- rhchain_block
- rhchain_tx
- rhchain_balance
- rhchain_token_transfers
- rhchain_logs
- rhchain_gas
- rhchain_contract
- rhchain_call
- rhchain_nonce
- rhchain_activity
- rhchain_registry
- rhchain_usdg
- rhchain_watch
- ton_block
- ton_account
- ton_balance
- ton_tx
- ton_jetton
- ton_jetton_holders
- ton_transfers
- ton_dns
- ton_price
- ton_gram
- ton_nfts
- ton_agent_wallet
- preflight
- safety_guardrail
- safety_simulate
- safety_approvals
- safety_decode
- portfolio_value
- portfolio_pnl
- portfolio_risk
- escrow_create
- escrow_status
- escrow_resolve
- escrow_list
- lending_liquidations
- portfolio_taxlots
- scout_rankings
- scout_service
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.