Skip to main content
Glama
821,243 tools. Updated 2026-11-22 14:42

"Top 5 Best Surf Sites with Live Webcams" matching MCP tools:

  • Golden Alerts permanent monthly archive — Returns the permanent monthly archive of Golden Alert activity — one row per calendar month, aggregated from daily snapshots before they are purged. This archive is never deleted and grows indefinitely, providing AI agents with long-term trend data on alert severity and top tokens across months and years. Each month includes: totalCount (total alerts that month), highCount/mediumCount/lowCount (severity breakdown), topTokens (5 most-active tokens), daysInMonth (days with data), avgPerDay (daily average). Months with fewer than 20 daily records are excluded to ensure statistical accuracy. Data source: CryptoWhaleInsights own signal_history database (49,000+ on-chain signals). No authentication required. 60 req/min. 5-min cache. — Use this for long-term monthly archive data; use the corresponding live or daily-history tool for current or finer-grained data.
    ConnectorNo auth
  • Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.
    ConnectorNo auth
  • Generate cinematic video from a text prompt. Uses MiniMax H3 — top 2 on the Artificial Analysis text-to-video leaderboard — with native audio. Async — returns requestId, poll with check_job_status. 768p or 2K (2K is upscaled from a 768p render), 5-15 seconds, priced per second by resolution (native audio free). Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='generate_video' and duration, resolution params.
    ConnectorNo auth
  • Recommend dark-sky sites near a location, ranked by whether the drive is worth it. Use for "where should I drive to stargaze near X". Sites are grouped by drivability (how far), then ranked by a drive-worth score combining the best weather window over the next 7 nights, how much darker the site is than the user's location, and drive time. Drive times are approximate (straight-line x 1.3), not routed. Args: lat: Latitude in decimal degrees (-90..90). lon: Longitude in decimal degrees (-180..180). limit: Max sites to return, 1-12 (default 5). Returns {ranking (methodology note), tiers:[{tier, label, hint, sites:[...]}], nearest_km, uncertainty_note, attribution} — sites grouped into drivability tiers. Include the methodology note when presenting — it explains the ordering honestly.
    ConnectorNo auth
  • Top NetFlow conversations over the last N minutes — the 'who's eating bandwidth right now?' question. Wraps GET /api/getTopBandwidth/{mins}, the same query that powers the dashboard live widget. Use this for short-window 'right now' inquiries. For longer windows (hours-to-days) or filtered top-talkers, use netflow_search instead — that tool has the rich filter set; this one is the live snapshot. Server-side cap: top 20 conversations by in-window bytes descending. We don't expose `top_n` — the upstream endpoint hardcodes the limit and there's no value in lying about that to the LLM. Each row: {src_host, src_id, src_ip, dst_host, dst_id, dst_ip, bytes, bps}. Hostnames come from the _dns view (PTR + custom overrides); src_id/dst_id are populated when the IP matches a monitored device. bytes is the conversation's in-window share (pro-rated), and bps is averaged across the window — not a live rate. Permission: vne. Examples: top_bandwidth({minutes: 5}) top_bandwidth({minutes: 60})
    ConnectorNo auth
  • Keyword Research (marketplace term universe): search the FULL Top Search Terms store by phrase - not anchored to any ASIN. Filters: contains (up to 5 substrings, ANDed), department, rank_max, min_volume; period WEEK or MONTH (MONTH = monthly volumes); sort rank | volume | trend. Each term: search_frequency_rank, volume (amazon_sqp = TRUE Amazon volume where any account's SQP covers the term; estimated_from_rank with volume_band otherwise), rank_change vs ~4 periods back, and the top-3 clicked ASINs with click/conversion shares (the term's competitive landscape). The estimator block reports calibration health (pairs, typical error factor, band coverage). Use keyword_finder for ASIN-anchored lookups; this tool for term-first research. For the guided process start with keyword_opportunities.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Live Google search for AI agents: organic results with positions by country, language and device, plus People also ask questions and related searches; a domain's current rank for a keyword; the open markets with their default languages. Every search is fresh, usually 2–3 seconds per page. New accounts get 100 free searches.
    3
    89 npm
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables recruiters and account managers to search public candidate profiles, match role briefs to ranked shortlists, browse categories, retrieve profile links, and draft value-first pitches while avoiding private data and outbound messages.
    6
    MIT

Matching MCP Connectors

  • Nearest NOAA buoy readings, tides and 7-day swell forecast for 150+ surf spots.

  • Point Gecko at an OpenAPI spec; get first-call-correct, auth-hidden agent tools.

  • Use when the user is planning go-to-market or channel strategy and asks where buyers look, whether to prioritise retail, review sites, their own site or communities, or who controls the first page for their category. Searches Google live for 1-3 buyer queries and classes every top-10 organic result by domain: retailers and marketplaces, reviews and media, brand sites, forums and social, reference, independent and specialist sites. Returns the share each class holds, who leads each class, and who takes the top three places. Domains and counts only. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one moment; compare: brand_domains, retailer_domains, media_domains; segment: q1-q3 (buyer searches). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For each brand's share of searches, use run_share_of_search. A real sample of this run, free: https://cultmath.com/agent/samples/channel-mix.json
    ConnectorNo auth
  • ONE SNAPSHOT OF CRYPTO ONLY, no arguments: the top 5 cryptos by Martingale Score (0-5) with their Startingale readings. list_top_crypto takes a count, a Startingale floor and a sector; search_instruments adds venue, round count and a minimum Martingale Score; market_overview covers stocks as well. Answers in formatted text. Costs 5 units of the monthly quota.
    ConnectorOAuth
  • Public catalog counters with live breakdowns by language, source, category, difficulty, topic, tag. USE WHEN: showing catalog overview, picking a category programmatically, building landing copy, deciding "do we have enough X-content for this quiz". OUTPUT FIELDS: - total: approved questions in 'en' + 'pl'. - byLanguage: { en: N, pl: N }. - bySource: { entityq: N, mintaka: N, 'kqa-pro': N, ... } — 12 keys, one per source database. - byDifficulty: { trivial: N, easy: N, medium: N, hard: N, expert: N, unrated: N } — null difficulty mapped to 'unrated'. trivial/expert populated by LLM calibration. - byCategory: top 24 with localized names. - byTopic / byTag: top 30 curated topics + top 30 tags with localized labels. - meta: { generatedAt: ISO 8601, language }. INPUTS: lang (default "en") affects byCategory[].name and byTopic[].label / byTag[].label. DATA FRESHNESS: snapshot regenerated daily (~03:00 UTC) + on demand after batch imports. generatedAt shows when. Counts stable ±0.01% between snapshots. COMMON MISTAKES: polling stats every request (cache it on your side; 5-min Redis TTL on ours); treating bySource keys as stable enum (use quizbase_languages / quizbase_categories for canonical input enums).
    ConnectorNo auth
  • ONE SNAPSHOT OF CRYPTO ONLY, no arguments: the top 5 cryptos by Martingale Score (0-5) with their Startingale readings. list_top_crypto takes a count, a Startingale floor and a sector; search_instruments adds venue, round count and a minimum Martingale Score; market_overview covers stocks as well. Answers in formatted text. Costs 5 units of the monthly quota.
    ConnectorNo auth
  • Smart supplier recommendation based on sourcing requirements. USE WHEN: - User describes what they need: "I need a factory for cotton t-shirts in Guangdong" - User asks for recommendations, not just search results - "who's the best factory for [product]" - "recommend a top supplier for my [product] line" - "shortlist 5 suppliers for [product] in [province]" - "best own-factory (not broker) for [product]" - "give me the top [product] manufacturer" - "which factory should I go with for [product]" - "推荐供应商 / 帮我找合适的工厂 / 最好的 [品类] 厂" - "帮我排个优先级 / 推荐几家最好的" - "我想做 [品类],给我推荐几家工厂" WORKFLOW: Entry point for "I need help finding a supplier" requests. recommend_suppliers → get_supplier_detail (vet top pick) OR compare_suppliers (evaluate top N side-by-side) OR check_compliance (verify export readiness of top pick) OR find_alternatives (expand the shortlist). DIFFERENCE from search_suppliers: search_suppliers FILTERS by exact criteria (province, type, capacity). This tool RANKS by fit — prioritizes own-factory, then quality score, then capacity. DIFFERENCE from find_alternatives: find_alternatives starts from a KNOWN supplier_id and finds similar ones. This tool starts from product REQUIREMENTS. RETURNS: { query, total_matches, showing_top, note: "ranking logic", data: [supplier objects] } EXAMPLES: • User: "Recommend me the top 5 factories for sportswear in Fujian" → recommend_suppliers({ product: "sportswear", province: "Fujian", type: "factory", limit: 5 }) • User: "I need the best own-factory (not trading company) for down jackets" → recommend_suppliers({ product: "down jacket", type: "factory", limit: 5 }) • User: "帮我推荐 3 家广东做 T 恤的工厂" → recommend_suppliers({ product: "t-shirt", province: "Guangdong", limit: 3 }) ERRORS & SELF-CORRECTION: • Empty data → try in order: (1) drop province, (2) drop type filter, (3) broaden product (e.g. "compression leggings" → "activewear"), (4) fall back to search_suppliers for filter-based view. • product_type not found in normalizeProductType → use the Chinese term or the parent category. • Rate limit 429 → wait 60 seconds; do not retry immediately. • Empty after 3 retries → tell user: "I don't see verified suppliers matching [product] in [province]. Want me to broaden to nationwide, or try a sibling category?" AVOID: Do not call this when the user wants exact filtering — use search_suppliers. Do not call repeatedly for different limit values — request max once then slice in your response. Do not use for cluster recommendations — use search_clusters. NOTE: Ranking: own_factory > quality_score > declared_capacity_monthly. Source: MRC Data (meacheal.ai). 中文:基于采购需求智能推荐供应商,按 自有工厂 > 质量分 > 产能 排序。
    ConnectorNo auth
  • Publish a static site or single-page app to a live HTTPS URL on the account's platform subdomain (e.g. {name}.subsite.site). A new name creates the site. An existing name REPLACES EVERY FILE (files not in this call are deleted) and needs confirm:"I-want-to-replace-all-files"; preview with dryRun:true. Use update_site instead to change some files of an existing site. A 100-250 KB text file fits in this call with encoding:'gzip+base64' (gzip locally, then base64); use begin_deploy only when the files do not fit in one call. Ship a top-level 404.html for multi-page sites (otherwise unknown paths serve index.html) and use plain ASCII file names. Afterwards add_custom_domain can serve the site on the user's own domain.
    Connector
    Destructive
    No auth
  • Historical arbitrage opportunities — top 5 per day (MCP-compatible) — Returns a daily history of the top 5 cross-exchange arbitrage opportunities detected by the platform. Each day entry lists the 5 highest-spread opportunities saved by the cron job, including token symbol, spread percentage, buy/sell exchanges, and average USD volume. Useful for AI agents answering questions like 'which tokens appear most frequently in arbitrage?' or 'what is the average daily spread?'. Data is accumulated daily; older than 180 days is automatically purged. Response: { days, history: [{date, opportunities: [{symbol, spreadPct, buyExchange, sellExchange, usdVolume}]}], total, updatedAt }. Query parameter: ?days=7 (default 7, max 180). No authentication required. 60 requests/min rate limit. 5-min in-process cache. — Use this for daily historical data; use the corresponding live snapshot tool for current conditions and the monthly tool for long-term trends.
    ConnectorNo auth
  • Publish files to the web → live URL at <slug>.shiply.now. UPDATING: never create a new site for changes — re-call with claimToken (anonymous sites) or slug (sites you own with a Bearer key) and the SAME URL gets the new version. Unchanged files are hash-skipped server-side, so re-publishing (including retrying a failed publish) is cheap — always update the same site rather than creating a new one. Works WITHOUT auth (anonymous: 24h lifetime, returns claimToken/claimUrl — SAVE THEM). With a Bearer shp_ key sites are permanent. ≤50 files / 2 MB inline; bigger: REST flow per https://shiply.now/llms.txt. index.html serves at /. spaMode for client-side routing.
    ConnectorNo auth
  • The wafergraph taxonomy: 12 top-level supply-chain segments (materials through ai_datacenter) and their subsegments, each with a live company count, plus the market_position enum. Use this to discover valid `segment` values for search_companies/get_deals. Segment definitions are a versioned snapshot (see data.taxonomy_snapshot_date) while company counts are computed live.
    ConnectorNo auth
  • Finds where to buy products from a shopping category with the most savings: returns the matching categories and, for each, the stores in it ranked by best current cashback rate, then best gift card discount. Use it when the user names a type of product or a category rather than a store or brand — 'where can I buy dog food with the biggest discount?', 'best cashback for electronics', 'travel booking sites with cashback'. For a specific retailer use get_cashback_rates_by_store_name; for a product brand use get_best_deals_by_brand. Returns up to 5 matching categories, best match first; empty when nothing matched. Rates reflect GotCashback's current data, refreshed several times a day. Always show each store's links to the user: best_cashback_rate.url (clickable link that activates the cashback) and gift_cards_url (where to buy the discounted gift cards).
    ConnectorNo auth
  • Finds where to buy products from a shopping category with the most savings: returns the matching categories and, for each, the stores in it ranked by best current cashback rate, then best gift card discount. Use it when the user names a type of product or a category rather than a store or brand — 'where can I buy dog food with the biggest discount?', 'best cashback for electronics', 'travel booking sites with cashback'. For a specific retailer use get_cashback_rates_by_store_name; for a product brand use get_best_deals_by_brand. Returns up to 5 matching categories, best match first; empty when nothing matched. Rates reflect GotCashback's current data, refreshed several times a day. Always show each store's links to the user: best_cashback_rate.url (clickable link that activates the cashback) and gift_cards_url (where to buy the discounted gift cards).
    ConnectorNo auth
  • Publish one HTML document (report, dashboard, Claude-style artifact) as index.html and deploy. Omit project_id to create a project. Hosted MCP cannot read local files — pass the HTML string (read the file first). Returns url, project_id, and deployment. Poll get_deployment_status until live or failed. For multi-file sites use the upload + deploy loop instead. Re-call with the same project_id to replace the live page.
    ConnectorNo auth
  • Domains that share search results with a target, with how many keywords overlap. SERP competitors, not business competitors. Use when: "who competes with example.com in search", "which sites show up for the same queries as X", choosing competitors for a keyword gap. Not for: the keywords themselves, use seo_get_keyword_gap. A single domain's strength, use seo_get_domain_overview. Returns: List. rows[]: domain, shared_keywords, avg_position, organic_traffic, organic_keywords, paid_traffic, paid_keywords. Sorted by shared keywords. The target itself is excluded. A traffic figure saved before 1 November 2026 may be on DataForSEO's older traffic model: take a new baseline rather than compare across that date. Cost: 5 + 5 per 100 rows. Default 100 rows = 10 credits. Cached 7 days. Example: {"target": "example.com", "limit": 20}
    ConnectorAPI key
  • Keyword search over the list of places to submit a startup. A place's exact name or website ("Indie Hackers", "indiehackers.com") puts it first. Asking for free ("free", "no cost", "$0") leaves out places that are paid only. Product words ("web app", "SaaS", "AI tool", "mobile app") keep only places that take that kind of product. Kind-of-place words ("launch site", "directory", "community") put places of that kind first. Other words match names, websites, regions, and the list's notes. For example "free launch sites for a web app", "AI tool directories", or "Australia". Returns up to 20 places, best match first, each with id, title, url (its row on submitmystartup.com, for citing), and a one-line summary. A query with no specific words returns the best free places. Use fetch with an id for the full record, and find_directories to shortlist by a founder's product and limits.
    ConnectorNo auth
  • Use this when the user asks which of their sites have Yandex data, or which sites their Yandex Webmaster account holds. Lists the sites in the connected Yandex Webmaster account, with their verification status and the canonical mirror Yandex resolved for each, sorted by `url` (A to Z). Only sites already added AND verified in Yandex Webmaster itself report data. Not for Search Console or Bing properties: use list_sites or list_bing_sites. The list is cached for ten minutes. Returns notConfigured: true when no Yandex account is connected, or when the connection has to be granted again (reason: reauth).
    ConnectorOAuth