store_samples — Riley Craig x402 Agent Store MCP Tool
store_samples
(store samples) is one of 92 tools on the
Riley Craig x402 Agent Store
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call store_samples from your client
- Claude Code Riley Craig x402 Agent Store store_samples run in your project directory
- Claude Desktop Riley Craig x402 Agent Store store_samples ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Riley Craig x402 Agent Store store_samples ~/.cursor/mcp.json
- VS Code Riley Craig x402 Agent Store store_samples .vscode/mcp.json
- Zed Riley Craig x402 Agent Store store_samples ~/.config/zed/settings.json
- Windsurf Riley Craig x402 Agent Store store_samples ~/.codeium/windsurf/mcp_config.json
- Cline Riley Craig x402 Agent Store store_samples ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Riley Craig x402 Agent Store store_samples ~/.gemini/settings.json
- Grok Riley Craig x402 Agent Store store_samples .mcp.json (in your project root)
- ChatGPT Riley Craig x402 Agent Store store_samples Settings → Connectors → Advanced → Developer mode
- Claude.ai Riley Craig x402 Agent Store store_samples Settings → Connectors → Add custom connector
- LangChain Riley Craig x402 Agent Store store_samples pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http x402-agent-store https://store.agentexchange.work/mcpOther tools on this server
- store_catalog
- market_overview
- market_list_tasks
- market_post_task
- market_bid
- market_award
- market_publish_receipt
- agent_passport
- sales_qualify_lead
- brand_ai_visibility_check
- ai_visibility_index
- ai_visibility_signal
- us_macro_regime
- defi_vs_riskfree_spread
- us_treasury_rates
- defi_yields
- crypto_prices
- prediction_market_odds
- crypto_ai_visibility
- dex_token_data
- whale_transfer_alerts
- smart_money_wallet_activity
- wallet_portfolio
- chain_native_balance
- chain_block_header
- chain_event_logs
- chain_fee_history
- chain_token_identity
- chain_confirmations
- chain_l1_data_fee
- chain_nft_owner
- chain_batch_reads
- chain_heartbeat
- chain_gas_price
- connect_token
- pretrade_full_report
- connect_company
- eu_tender_intelligence
- opportunity_intelligence
- gov_contract_intelligence
- chain_id
- chain_estimate_gas
- chain_storage_slot
- chain_transaction_status
- chain_transaction_explain
- chain_token_supply
- chain_ens_resolve
- token_launches_feed
- base_wave_radar
- crosschain_attention_radar
- token_security_check
- ai_category_ranking
- country_economic_indicators
- github_trending
- npm_downloads
- hn_top_stories
- web_search
- tavily_search
- wikipedia_lookup
- truck_load_profit
- truck_cost_per_mile
- web_scrape
- web_crawl
- agent_enterprise_integration
- social_sentiment_scanner
- b2b_lead_enrichment
- real_estate_property_valuation
- crypto_market_metrics
- markdown_web_scraper
- weather_forecast
- llm_chat_completions
- llm_messages
- api_generate
- agentforce_proxy
- vertex_proxy
- bedrock_proxy
- post_check
- get_agents_lounge
- post_directory_list
- post_directory_index
- post_notary
- get_chain_erc20_balance
- get_chain_code
- get_chain_block_number
- get_chain_allowance
- get_chain_nonce
- get_chain_call
- get_crypto_address_risk
- get_crypto_liquidations
- post_api_v1_chat_completions
- get_buy_credits
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.