Skip to main content
Glama
137,849 tools. Last updated 2026-05-21 01:55

"namespace:bot.402" matching MCP tools:

  • Structured coverage for ANY listed token — price, momentum, extremes, signals, project info, exchange listings, and optional LLM brief. Broader coverage than market_snapshot (which is limited to 26 supported tokens), shallower data (no orderflow, whale, liquidation, or signal fields). Use for tokens outside the BTC/ETH/SOL/etc. core set. Symbol disambiguation is automatic (top-by-volume match). REST equivalent: POST /data/light (0.05 USDC). Rate limit: 10 calls / minute per IP (lower than other tools — this fans out to a paid upstream provider). Cached responses up to 24h are served without refetching; agents needing fresher data should use the paid REST endpoint. Args: symbol: Token ticker — 1 to 10 alphanumeric characters (e.g. PEPE, WIF, FLOKI, BONK). Case-insensitive.
    Connector
  • Compute an expected-value-maximizing Jito tip for a Solana arbitrage bundle. Inputs: pool_depth (USD), expected_profit (USD), slot_probability [0..1]. Returns tip lamports + EV breakdown. Priced at $0.01 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.
    Connector
  • Fetch a Federal Reserve Economic Data (FRED) series by ID — e.g. 'DGS10' (10Y yield), 'WALCL' (Fed balance sheet), 'T10Y2Y' (yield curve). Returns cleaned latest observations. Priced at $0.005 USDC on Base (x402). Pass a signed x402 v2 authorization as the '_payment' argument to unlock the paid response. Without it, the tool returns the 402 accept-list for your wallet to sign.
    Connector
  • Get detailed KDP niche intelligence for a specific keyword. Returns demand score, competition score, Amazon BSR range, estimated monthly revenue, review threshold, average book pricing, and data freshness for the given Kindle publishing niche. Pricing tiers (x402 USDC on Base network): - $0.03 per query for cached/pre-seeded keywords - $0.10 per query for live on-demand research (new keywords) Use the free `list_niches` tool first to see available keywords. Payment options: 1. Set the KDP_X_PAYMENT environment variable on the server for auto-pay. 2. Pass a valid x402 payment header via the x_payment argument. 3. If neither is set, the tool returns structured 402 payment instructions that an x402-capable agent can use to construct and retry payment. Args: keyword: The KDP niche keyword to research (e.g. "romance novels", "keto cookbook") x_payment: Optional base64-encoded x402 payment header. Takes precedence over the KDP_X_PAYMENT environment variable.
    Connector
  • Call when you cannot proceed because the next step requires a real human. USE WHEN you are blocked by: - Terms of Service or legal agreements requiring a natural person - Account creation that needs identity verification or CAPTCHA - Authentication requiring human identity (BankID, SMS 2FA, OAuth) - Forms requiring human verification or a physical-world action - Content behind a login wall you cannot access - Any step requiring legal personhood, physical presence, or human identity DO NOT USE for: sending messages, making HTTP requests, writing code, or any task you can complete with your existing tools. The human is a paid worker (billed per task), not your operator. Never include passwords, card numbers, CVCs, bank account numbers, SSNs, authentication tokens, or API keys in the description. If a task requires payment, tell the human what to pay for and where — they will use their own payment method. Format your description as numbered steps, one instruction per line. Put each URL on its own line. End with "REPLY WITH:" listing expected deliverables. Example: STEPS: 1. Create account at https://example.com/signup 2. Accept the terms of service. REPLY WITH: confirmation URL, account ID Free tier included on registration. Each task costs 1 credit. Returns 402 when credits are exhausted. Fastest during European business hours (CET). Tasks submitted outside these hours may take longer. Typical completion: 2-30 minutes. Use check_task_status to poll. Set demo:true for an instant synthetic response to verify your integration works. No credits consumed.
    Connector
  • Start the purchase flow for a domain using USDC crypto payment (x402 protocol). Autonomous two-step payment flow — no browser required: Step 1: Call this tool to reserve the domain and get a pay_url. Step 2: Pay the pay_url using your x402 wallet: - If you have Coinbase Payments MCP: call its x402 payment tool with the pay_url. - Otherwise: run `curl -L <pay_url>` — your x402-enabled HTTP client will handle the 402 handshake and USDC payment on Base automatically. After payment succeeds, call get_domain_status(order_id) to poll until registration is complete (usually under 60 seconds). The registrant contact details are required because the domain will be registered in the buyer's name (they become the legal owner). WHOIS privacy is enabled by default, so these details are not publicly visible. IMPORTANT: Before calling this tool, you MUST first call check_domain to get the price and confirm it with the user. Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code (e.g. "US", "GB", "DE"). phone: Phone number in format +1.5551234567. org_name: Organization name (optional, leave empty for individuals). Returns: Dict with order_id, pay_url (full URL to pay via x402), price_usdc, price_cents, network, and USDC contract address.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Discover live agent APIs, ranked endpoints, trust, payment telemetry, and x402 surfaces.

  • Physical mail API for AI agents. Send letters, certified mail, postcards from code via MCP.

  • Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.
    Connector
  • Retrieve static game rules, denomination model, pot mechanics, and strategy explanations. Free -- no payment required. Returns: flip cost, randomness source (Chainlink VRF), pot payout rules (2-hour and jackpot), denomination model (pots in ETH, payments in USDC), strategies (match vs beat). Call this first to understand the game before using other tools. [pricing: {"cost":"0","currency":"USDC","type":"free"}]
    Connector
  • Check multiple URLs in a single batch. Returns results for all URLs, handling async processing automatically. Each URL is analysed across seven dimensions: redirect behaviour, brand impersonation, domain intelligence (age, registrar, expiration, status codes, nameservers via RDAP), SSL/TLS validity, parked domain detection, URL structural analysis, and DNS enrichment. Known and cached URLs return results immediately. Unknown URLs are queued for pipeline processing. This tool automatically polls for results until all URLs are complete or the 5-minute timeout is reached. You don't need to manage polling or job tracking. If the timeout is reached before all results are complete, returns whatever is available with a clear message indicating which URLs are still processing. The user can check results later via check_history. Maximum 500 URLs per call. For larger datasets, call this tool multiple times with chunks of up to 500 URLs. Billing: Same as check_url. Known and cached domains are free. Only unknown domains running through the full pipeline cost 1 credit each. The summary shows pipeline_checks_charged (the actual number of credits consumed). If you don't have enough credits for the unknowns in the batch, the entire batch is rejected with a 402 error telling you exactly how many credits are needed. Duplicate URLs in the list are automatically deduplicated (processed once, charged once). Invalid URLs get individual error status without rejecting the batch. Use the "profile" parameter to score all results with custom weights.
    Connector
  • Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.
    Connector
  • Get port congestion metrics — vessel waiting times, berth occupancy, and delay trends for a specific port. Use this to assess port efficiency and anticipate detention risk. High congestion often leads to longer container dwell times and higher D&D costs. For shipping disruption news and alerts (Red Sea, Suez, chokepoints), use shippingrates_congestion_news instead. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { port, congestion_level, avg_waiting_hours, berth_occupancy_pct, vessel_count, trend, period_days }.
    Connector
  • Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.
    Connector
  • Before you transact, know who you're dealing with. Paste any wallet address — EVM or Solana, auto-detected — and get entity label (exchange, protocol, flagged mixer), risk level, account age, transaction history, and top holdings. Flags: new_account, unverified_contract, dormant, high_throughput. REST equivalent: POST /analyze/address (0.25 USDC). Args: address: EVM address (0x...) or Solana address (base58)
    Connector
  • Place a $fomox402 bid on a game round. Wins the round if you're still the head bidder when the deadline hits zero. WHAT IT DOES: handles the full 3-leg x402 micropayment dance internally: leg 1: POST /v1/games/:id/bid → broker returns HTTP 402 with a fee nonce leg 2: POST /v1/x402/pay (broker signs the fee tx from your Privy wallet) leg 3: POST /v1/games/:id/bid with X-Payment header → broker submits the on-chain bid_token instruction Caller sees one atomic action; on success returns the bid tx hash. WHEN TO USE: any time you want to be the head bidder. Pick gameId from list_games, set amountRaw ≥ that game's effective_min (smallest legal bid), and call. FEES: ~0.001 $fomox402 micropayment to the dev wallet (the x402 leg) plus the bid amount itself (which goes to the game vault and ratchets effective_min for the next bidder). Solana network fees ~0.00001 SOL/tx. FAILURE MODES: bid_failed_402_no_nonce — broker returned 402 but no usable nonce (unusual) x402_pay_failed — your wallet couldn't cover the micropayment fee bid_failed_after_pay — fee landed but the bid was racing another bidder and they got there first; effective_min moved up bid_failed — non-402 error (validation, RPC, etc.) RETURNS on success: { tx (Solana sig of the bid_token call), gameId, amountRaw, x402_paid (bool), x402_fee_tx? (sig of fee tx if paid), newDeadline, newEffectiveMin, isHead (true if you're now last bidder), keysIssued (always 1) }. MINTS 1 KEY: every successful bid mints you one key on the round. Keys earn $fomox402 dividends from every later bid; consider holding rather than burning them unless the pot is mature. RELATED: list_games (find target), get_game (verify deadline), claim_winnings, claim_dividend, play (auto-loop wrapper), burn_key (advanced).
    Connector
  • Get detailed gateway status including treasury address, subsystem latencies, and agent count. Use for deeper diagnostics beyond basic health checks. FREE — rate-limited only. [pricing: {"cost":"0","currency":"FREE","type":"free","network":"eip155:8453"}]
    Connector
  • Get schedule reliability metrics for a carrier — on-time performance percentage, average delay in days, and sample size. Use this for carrier selection and benchmarking — answers "how reliable is this carrier on this trade lane?" On-time is defined as arriving within ±1 day of scheduled ETA (industry standard per Sea-Intelligence). PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { line, trade_lane, on_time_pct, avg_delay_days, sample_size, period }.
    Connector
  • Buy a Pro subscription for $10 USDC (30 days). Requires authentication. This endpoint returns HTTP 402 with x402 payment instructions. Your x402-enabled HTTP client will handle the USDC payment automatically. After payment, you get Pro tier: 10 tracks/day, 2 episodes/week, analytics, and more.
    Connector
  • Buy a Studio subscription for $25 USDC (30 days). Requires authentication. This endpoint returns HTTP 402 with x402 payment instructions. Your x402-enabled HTTP client will handle the USDC payment automatically. After payment, you get Studio tier: 20 tracks/day, 5 episodes/week, video, audience insights, and more.
    Connector
  • Start the purchase flow for a domain via Stripe's Machine Payments Protocol (MPP). MPP lets autonomous agents pay with fiat (cards, Link) or stablecoins via Shared Payment Tokens, with no browser checkout. Two-step flow: Step 1: Call this tool to get an order_id and pay_url. Step 2: Make an HTTP GET request to the pay_url with an MPP-enabled HTTP client. The server responds with HTTP 402 + WWW-Authenticate; the client creates a Shared Payment Token and retries with an Authorization header. The server charges the SPT through Stripe and kicks off domain registration. After payment, call get_domain_status(order_id) to poll until complete. Requires: An MPP-compatible client configured to mint SPTs against the server's advertised Stripe Business Network profile. Args: domain: The domain to purchase (e.g. "coolstartup.com"). first_name: Registrant's first name. last_name: Registrant's last name. email: Registrant's email address. address1: Registrant's street address. city: Registrant's city. state: Registrant's state or province. postal_code: Registrant's postal/zip code. country: 2-letter ISO country code. phone: Phone number in format +1.5551234567. org_name: Organization name (optional). Returns: Dict with order_id, pay_url (full URL), price_cents, price_display, network_id, and payment_method_types.
    Connector