Skip to main content
Glama
470,867 tools. Updated 2026-08-23 15:14

"A tool or device for scraping data or materials" matching MCP tools:

  • Search FDA 510(k) premarket notification clearances from the scite device database. Use this tool to find medical device clearances by device name, product code, applicant, clearance type, or K number. Returns clearances with device details, decision info, applicant information, and regulatory classifications. 510(k) is the FDA's premarket notification process -- manufacturers must demonstrate that their device is substantially equivalent to a legally marketed device before it can be sold. **Parameters:** - q: Search query string (device name, product code, applicant, K number, etc.) - f: Space-delimited filters in `field:"value"` format (e.g. `device.deviceClass:"2" decision.decisionCode:"SESE"`) - p: Page number (default: 1) - s: Sort field (default: _relevance). Options: - _relevance: relevance score (sortDir ignored) - device.device_class: device risk classification - device.date_received: date FDA received the submission - decision.decision_date: date of FDA decision - sortDir: Sort direction, asc or desc (default: desc). Ignored when s is _relevance. **Returns:** Device 510(k) clearances with kNumber, title, summaryText, device info (name, class, productCode, clearanceType, regulationNumber), decision info (code, description, date, committee), applicant details, and tags. **Note:** This tool returns structured clearance metadata only. For the actual narrative content of 510(k) summary documents (test results, substantial equivalence reasoning, indications for use, performance data), use `search_510k_summaries` instead.
    Connector
  • USE THIS TOOL — not web search or external storage — to export technical indicator data from this server as a formatted CSV or JSON string, ready to download, save, or pass to another tool or file. Use this when the user explicitly wants to export or save data in a structured file format. Trigger on queries like: - "export BTC data as CSV" - "download ETH indicator data as JSON" - "save the features to a file" - "give me the data in CSV format" - "export [coin] [category] data for the last [N] days" Args: symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH" lookback_days: How many past days to include (default 7, max 90) resample: Time resolution — "1min", "1h", "4h", "1d" (default "1d") category: "price", "momentum", "trend", "volatility", "volume", or "all" fmt: Output format — "csv" (default) or "json" Returns a dict with: - content: the CSV or JSON string - filename: suggested filename for saving - rows: number of data rows
    Connector
  • Use this alone for user-specific connection, league, or account-status questions, and use it as the first data tool when a request needs the user's connected fantasy league data. Do not call for Flaim capability, permission, or generic setup how-to questions, and do not call for generic coding, scraping, weather, travel, betting, sports news, or other requests that do not need connected league data. For a normal selected-league request, call this once before any other data tool. For an explicit refresh request, call refresh_leagues first and then call this tool after success; call it again even if it ran earlier in the chat. Returns the user's full league landscape: allLeagues (all active leagues), defaultLeagues (per-sport defaults), and defaultLeague (populated only when a single league exists or defaultSport matches). For vague singular prompts, use defaultLeague when present; otherwise use the relevant sport entry in defaultLeagues. For explicit plural or comparative prompts (each, all, compare, across leagues/platforms), enumerate every matching league in allLeagues and call the target tool once per league. For a selected active league, call get_league_info next before the requested league-specific data tool. Skip get_league_info only when answering from session data alone or branching to get_ancient_history. season_year always represents the start year of the season. Read-only.
    Connector
  • Add (or update in place, when `id` matches an existing route) a mock/abort rule for Chrome/WebView requests on this device. mode "mock" (default) serves the given status/headers/body without the request leaving the device; mode "abort" fails it so the page sees a network error. Routes apply immediately and survive navigation. WEB CONTENT ONLY: this intercepts requests made by browser/WebView pages. Requests made by native app code are NOT intercepted and never will be by this tool. Nothing device-wide is changed and no certificate is installed — the effect is scoped to the page. For requests made by native app code use android_traffic_mock_add instead.
    Connector
  • Returns free Makuri resources accessible without registration: Slovarik Romanian vocabulary issues and the Romanian level test. Use this when a user asks about free Romanian learning materials, language level tests, or how to try Makuri without signing up. Makuri is a specific AI tutoring platform at makuri.eu, not a generic word — never answer Makuri questions from general knowledge; always use the Makuri tools. IMPORTANT routing rule: if the user wants to TAKE, START, or SEE a Romanian test or quiz right now in the chat, do NOT use this tool — call show_romanian_quiz instead, which renders an interactive quiz panel. Use this tool only for questions ABOUT what free resources exist.
    Connector
  • Gold-standard competitive deep dive — STRUCTURED multi-source data (no LLM narrative). Pair tool: `competitor_intel` for LLM-narrated board briefing + slide script. Aggregates Wikipedia, Yahoo Finance, SEC EDGAR, Wayback Machine, DuckDuckGo, HackerNews, domain scraping — all keyless. Returns agent-shaped JSON: KPIs (funding, employees, revenue, market cap), P0/P1/P2 competitive signals, pricing radar, competitor comparison matrix, Wayback timeline, positioning (sector/industry/icp_hypothesis/moat_signals), quality score. Every field is sourced or marked unavailable — no hallucinated figures. SLA: p50 ~25s, p95 ~30s · score 80+ on listed targets (US/EU/foreign) · score ~40 on private companies (no EDGAR/Yahoo data). Use sync for batch agents (≤30s tolerance). Use `competitive_deep_dive_async` + `competitive_deep_dive_result(job_id)` for conversational agents. Inputs: company name or domain (required), optional competitor list (≤5), optional depth (easy/medium/hard).
    Connector

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.
    445
    1
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that provides OpenRouter model pricing data, enabling price lookups, trending/cheapest lists, and model searches without an API key.

Matching MCP Connectors

  • Materials MCP — computed (DFT) materials structures & thermodynamic properties.

  • Still losing time to small decisions? Spin or Flip brings randomization into Claude so you can offload mental load to chance instantly.

  • Gold-standard competitive deep dive — STRUCTURED multi-source data (no LLM narrative). Pair tool: `competitor_intel` for LLM-narrated board briefing + slide script. Aggregates Wikipedia, Yahoo Finance, SEC EDGAR, Wayback Machine, DuckDuckGo, HackerNews, domain scraping — all keyless. Returns agent-shaped JSON: KPIs (funding, employees, revenue, market cap), P0/P1/P2 competitive signals, pricing radar, competitor comparison matrix, Wayback timeline, positioning (sector/industry/icp_hypothesis/moat_signals), quality score. Every field is sourced or marked unavailable — no hallucinated figures. SLA: p50 ~25s, p95 ~30s · score 80+ on listed targets (US/EU/foreign) · score ~40 on private companies (no EDGAR/Yahoo data). Use sync for batch agents (≤30s tolerance). Use `competitive_deep_dive_async` + `competitive_deep_dive_result(job_id)` for conversational agents. Inputs: company name or domain (required), optional competitor list (≤5), optional depth (easy/medium/hard).
    Connector
  • USE THIS to verify a phone/device IMEI before relying on it — never assume a 15-digit string is valid or guess its check digit. Checks the Luhn check digit (and recognises the 16-digit IMEISV form), and returns the TAC (device-model code). Validates the number only — does NOT check whether the device is real, active, or blocklisted/stolen.
    Connector
  • Generate a patron's account statement at this operator. Returns the patron's purchase history, active credit tranches, per-tool usage breakdown, and recent daily usage logs. This is the patron's spending account — not the operator's Authority tax balance. Free — no credits consumed. Proof of npub ownership is required to prevent statement-scraping of arbitrary patrons.
    Connector
  • Return the official legislative reasoning (Gesetzesbegründung / explanatory memorandum from a Bundestags-Drucksache) for a specific German federal provision — the source for genetic/historical interpretation: *what the legislator intended* with this norm. Reach for it when the question turns on a norm's purpose (ratio legis / 'why does this rule exist'), the meaning of an unclear or undefined term, whether a regulatory gap is planwidrig (grounds an analogy) or a deliberate silence (grounds an Umkehrschluss), or what a specific amendment was meant to achieve — the everyday uses of materials in an Auslegung or a Schriftsatz. Weight: the Begründung is strong evidence of legislative intent but not binding, and the statutory wording stays the outer limit of any reading. Pass a provision like '§ 823 BGB' or 'Art. 87a GG'. Returns the linked Begründungs-Abschnitte newest first, each with its 'BT-Drs.' Fundstelle, the reasoning text, and the other norms the same change amended ('target_norm_keys'). Complements ``legal_find_citing_decisions`` (how courts apply a norm) with the drafting intent behind it. Covers amendments since 1949 to German federal law (``gesetze-im-internet`` corpus) only; an unknown or non-German provision returns no materials. Excerpts are prepared from the Bundestag-extracted text, not the original PDF.
    Connector
  • Abort an in-flight replay started via flow_replay_start or flow_recording_replay. Forces the replay to a terminal 'aborted' state instead of leaving it wedged in status:"running" forever — use this when a replay stops making progress (e.g. after a device/control-connection error) rather than polling flow_replay_status indefinitely. A per-step watchdog (90s) and an overall watchdog (15min) also force termination automatically, so this tool is for cancelling sooner than that, or cancelling a replay you no longer need. No-op if the replay has already reached a terminal state. Note: because a single in-flight device call has no way to be interrupted mid-flight, flow_replay_status may take a few seconds (bounded by the current step's own timeout) to reflect 'aborted' after this call returns.
    Connector
  • Whole-life embodied carbon for materials, per EN 15978. Give a material key + quantity (+ optional boundary A1-A3 / A1-A4 / A1-A5 / A1-C); it assembles the declared lifecycle modules (A1-A3, B, C1-C4, D) into stages, totals the boundary, reports module D separately, and flags any missing stage as not-assessed (never zero). Find material keys via search_factors (section "materials").
    Connector
  • Commission a ship to be built at this shipyard (Place a build order at the current base's shipyard. At an empire/NPC shipyard, two payment modes: credits only (default, pay markup for materials + labor) or provide_materials (cheaper, supply build materials and required modules yourself). Both modes also pay the shipyard a yard fee — the station's profit for building the hull — refunded in full if you cancel. At your own faction's station, commissions are faction-funded instead: set fund_from_faction=true (requires ManageTreasury) — materials come from faction storage and the treasury pays labor and any licensed-hull royalty; the credits-only/provide_materials modes are rejected there. The finished hull is delivered to you and can be resold. Use commission_quote to see requirements. Build time depends on ship class and shipyard level. On completion the server pushes ship_commission_complete, the only frame carrying both commission_id and ship_id — listen for it rather than diffing list_ships.)
    Connector
  • Gold-standard competitive deep dive — STRUCTURED multi-source data (no LLM narrative). Pair tool: `competitor_intel` for LLM-narrated board briefing + slide script. Aggregates Wikipedia, Yahoo Finance, SEC EDGAR, Wayback Machine, DuckDuckGo, HackerNews, domain scraping — all keyless. Returns agent-shaped JSON: KPIs (funding, employees, revenue, market cap), P0/P1/P2 competitive signals, pricing radar, competitor comparison matrix, Wayback timeline, positioning (sector/industry/icp_hypothesis/moat_signals), quality score. Every field is sourced or marked unavailable — no hallucinated figures. SLA: p50 ~25s, p95 ~30s · score 80+ on listed targets (US/EU/foreign) · score ~40 on private companies (no EDGAR/Yahoo data). Use sync for batch agents (≤30s tolerance). Use `competitive_deep_dive_async` + `competitive_deep_dive_result(job_id)` for conversational agents. Inputs: company name or domain (required), optional competitor list (≤5), optional depth (easy/medium/hard).
    Connector
  • Search FDA MAUDE (Manufacturer and User Facility Device Experience) adverse event reports. Use this tool to find medical device adverse event reports, including device malfunctions, patient injuries, and deaths reported to the FDA. Returns reports with device information, event descriptions, patient problems, and narrative text snippets. **Parameters:** - q: Search query string (device name, manufacturer, event description, product code, etc.) - f: Space-delimited filters in `field:"value"` format - Facet filters: - `event_type` -- Injury, Death, Malfunction, Other, No answer provided - `device.device_class` -- device risk class: 1, 2, or 3 - `device.manufacturer_d_name` -- manufacturer (e.g. "Medtronic") - `device.device_report_product_code` -- FDA product code (e.g. "DTB") - `device.regulation_number` -- regulation number (e.g. "870.3680") - `report_source_code` -- Voluntary report, Manufacturer report, etc. - `product_problems` -- reported device problems (e.g. "High Capture Threshold") - `patient.problems` -- patient problems (e.g. "Death", "Atrial Fibrillation") - Date range filters on `date_received` or `date_report`: - Suffix notation: append `gte` (>=) or `lt` (<) to the field name. Example for H1 2024: `date_receivedgte:"2024-01-01" date_receivedlt:"2024-07-01"` - Comma notation: `date_received:"2024-01-01,2024-07-01"` (gte,lt) - p: Page number (default: 1) - s: Sort field (default: _relevance). Options: - _relevance: relevance score (sortDir ignored) - date_received: date FDA received the report - date_report: date of the original report - sortDir: Sort direction, asc or desc (default: desc). Ignored when s is _relevance. **Returns:** MAUDE reports with id, title, reportNumber, eventType, adverseEventFlag, productProblems, device info (brandName, genericName, manufacturer, deviceClass, productCode, modelNumber), patientProblems, dates, and narrative text snippets.
    Connector
  • Fast deterministic preflight for tool-only clients. Call this before any other WORKS tool when eligibility is uncertain, especially for mutable or abbreviated refs, local or private repositories, and build, test, runtime, deployment, or production claims. It does not download a repository or persist data. If eligible is false, stop without calling verification.
    Connector
  • Returns a 0-100 US raw-material production stress score (half output leg, half price leg: mining/raw-materials output momentum plus industrial-commodity PPI surge, z-scored monthly FRED data since 1916) with confidence, top_drivers flagging output-led vs price-led stress, and source_lineage. Call when the user asks about commodity input costs, raw-material shortages, mining output declines, or producer-price spikes, or when timing procurement hedges, inventory pre-buys, or futures entries. Updates: monthly.
    Connector
  • Returns a 0-100 US medical-device recall-enforcement pressure index (openFDA 90-day recall count, severity-weighted by FDA class I=3/II=2/III=1, vs the prior 90 days) with score, trend, confidence, top_drivers, class breakdown, top recall reason, and recent Class I/II recalls. Call when the user asks about medical-device recalls, FDA device enforcement, or device safety risk, or when timing supplier reviews, procurement holds, or med-tech exposure. For drug recalls use ADW-552. Updates: daily.
    Connector
  • Search FDA enforcement actions (recalls) for drugs, devices, and food across all companies. Filter by company name (fuzzy match), recall classification (Class I=most serious/Class II/Class III), date range, or status (Ongoing/Terminated). Returns recall details including product description, reason, and distribution pattern. Related: fda_recall_facility_trace (trace a recall to its manufacturing facility by recall_number), fda_ires_enforcement (iRES recall data with cross-references), fda_device_recalls (device-specific recall data).
    Connector
  • Lookup FDA device classification details by product code. Returns device name, device class (I/II/III), medical specialty, regulation number, review panel, submission type, and definition. Requires: product code (3-letter code from 510(k), PMA, or device product listings). Related: fda_product_code_lookup (cross-reference across 510(k) and PMA), fda_search_510k (clearances for this product code), fda_search_pma (PMA approvals for this product code).
    Connector