Skip to main content
Glama
306,549 tools. Last updated 2026-07-25 13:02

"A search for regulations and regulatory information" matching MCP tools:

  • Answer a research question from live web sources in one call — returns a synthesized answer with numbered [N] citation markers and a citations array of {url, title, index}. Supports recency and domain filters. Use for questions needing current, sourced information (news about a company, market state, comparisons). For raw search result links use web.search; mode='deep' runs minutes-long exhaustive research — only when explicitly requested.
    Connector
  • Returns a 0-100 EU legislative output velocity score (90-day adopted-act count from EUR-Lex/CELLAR — regulations, directives, decisions — vs 8 trailing windows) with trend, z_score, recent_window_count, baseline_window_mean, and per_variant_w0 breakdown. Call when the user asks about EU regulatory activity, rule-making pace, or compliance-burden build-up, or when timing EU compliance staffing, budget, or market-entry decisions. Updates: daily.
    Connector
  • Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Search the ShippingRates database by keyword — matches against carrier names, port names, country names, and charge types. Use this for exploratory queries when you don't know exact codes. For example, search "mumbai" to find port codes, or "hapag" to find Hapag-Lloyd data coverage. Returns matching trade lanes, local charges, and shipping line information. FREE — no payment required. Returns: { trade_lanes: [...], local_charges: [...], lines: [...] } matching the keyword. Related tools: Use shippingrates_port for structured port lookup by UN/LOCODE, shippingrates_lines for full carrier listing.
    Connector
  • Search the regulatory corpus using keyword / trigram matching. Uses PostgreSQL trigram similarity on document titles and summaries. Returns documents ranked by relevance with summaries and classification tags. Prefer list_documents with filters (regulation, entity_type, source) first. Only use this for free-text keyword search when structured filters aren't sufficient. Args: query: Search terms (e.g. 'strong customer authentication', 'ICT risk', 'AML reporting'). per_page: Number of results (default 20, max 100).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • FAA Regulations MCP — US Federal Aviation Regulations (14 CFR, 'FARs').

  • Tax Regulations MCP — US Treasury / IRS regulations (26 CFR, 'Treas. Reg.').

  • Get available actor roles per regulation with obligation counts. Actor roles define WHO an obligation applies to within a specific regulation (e.g. 'credit_institution', 'significant_institution' for CRD/CRR, or 'ai_provider', 'high_risk_deployer' for AI Act). Use this to discover which roles exist before filtering obligations with get_obligations(actor_role=...). Returns roles grouped by regulation, sorted by obligation count. Each role includes a human-readable label and description. Args: regulation: Filter to a specific regulation code (e.g. 'dora', 'ai_act'). If omitted, returns roles for all regulations.
    Connector
  • The Mirabello Wealth-Protection Atlas — OBJECTIVE per-pillar sub-indices (0-100) for each jurisdiction: tax efficiency, structure strength, residence clarity, crypto clarity, succession certainty, regulatory transparency (international compliance alignment — NOT a secrecy score) and institutional stability (World Bank WGI, where sourced). No composite ranking — weightings depend on client facts; use get_wealth_index for a client-weighted composite. Pass cc for one jurisdiction, omit for all. Includes methodology + a de-risk note. INFORMATION, NOT ADVICE.
    Connector
  • Return detailed information for a single port — identity, country, UN/LOCODE, classification, coordinates, maritime area, and the list of terminals (name, operating company, coordinates, address, website). Look up the port by its Datalastic uuid or its UN/LOCODE (exactly one). To search for a port by name or location, or when you don't have an exact identifier, use find_ports first.
    Connector
  • Get the full text of one EPA regulation — a US Environmental Protection Agency rule codified in 40 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 40 CFR 261 say", "what is the EPA regulation for X", "does the EPA require X", "read 40 CFR 60.1", "the RCRA hazardous waste rule", "the Clean Air Act / Clean Water Act regulation for X". Forgiving citation input: "261.4", "40 CFR 261.4", "§60.1", even "261.4(a)" (paragraph stripped to the section). Covers 40 CFR part 60 new source performance standards (emission standards / Clean Air Act), part 261 identification & listing of hazardous waste (RCRA), part 262 hazardous waste generators, part 122 NPDES permits (Clean Water Act), part 141 national primary drinking water regulations, part 63 NESHAP air toxics, TSCA parts (700s) toxic substances — the whole of Title 40 (air, water, waste, chemicals). This is EPA REGULATIONS (the rules/regulatory text); for EPA DATA (facility enforcement, ECHO compliance, GHG emissions) use the epa-echo / epa-emissions tools. Pass a whole part (e.g. "261" or "60") to get that part's section list. Example: epa_regulation({ citation: "261.4" }) -> exclusions from hazardous waste; epa_regulation({ citation: "40 CFR 60.1" }) -> applicability of emission standards. Keyless.
    Connector
  • Get the full text of one FDA regulation — a US Food & Drug Administration rule codified in 21 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 21 CFR 211 require", "what is the FDA regulation for X", "does the FDA require X", "read 21 CFR 211.100", "the FDA good manufacturing practice rule". Forgiving citation input: "211.100", "21 CFR 211.100", "§211.100", even "211.100(a)" (paragraph stripped to the section). Covers 21 CFR part 211 current good manufacturing practice (cGMP / GMP) for finished drugs, part 210 cGMP general, part 820 quality system regulation / QMSR for medical devices, part 801 medical device labeling, part 101 food labeling / nutrition facts, part 314 new drug applications (NDA/ANDA), part 807 device establishment registration, part 111 dietary supplement cGMP, part 1308 controlled substance schedules — the whole of Title 21 (food, drugs, devices, cosmetics, biologics). This is FDA REGULATIONS (the rules/regulatory text); for FDA DATA (drug labels, adverse events, recalls) use the openfda tools. Pass a whole part (e.g. "211" or "820") to get that part's section list. Example: fda_regulation({ citation: "211.100" }) -> written procedures / process control; fda_regulation({ citation: "21 CFR 101.9" }) -> nutrition labeling. Keyless.
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • List available laws, regulations, and court decisions in the database. Returns abbreviation, title, source type, jurisdiction, document kind, and version date for each entry. Unfiltered listings can contain thousands of entries; pass a search term or source_type to keep responses focused. Useful for discovering valid law abbreviations to use as filters in legal_search. Found a relevant law? Use legal_get_toc to browse its structure. NOT an existence check for a specific law: EUR-Lex entries store the official long title, so searching by common name or number can miss laws that ARE in the corpus. To verify a law exists, use legal_lookup with a citation or legal_search with a topic instead.
    Connector
  • Multi-source web research with citations. Returns a synthesized answer with numbered [^1] markers and a citations array of {url, title, snippet, index}. Use for evidence-backed synthesis (competitive analysis, regulatory summary, whitepaper section). For quick fact lookups use web.search instead.
    Connector
  • Multi-source web research with citations. Returns a synthesized answer with numbered [^1] markers and a citations array of {url, title, snippet, index}. Use for evidence-backed synthesis (competitive analysis, regulatory summary, whitepaper section). For quick fact lookups use web.search instead.
    Connector
  • Answer a research question from live web sources in one call — returns a synthesized answer with numbered [N] citation markers and a citations array of {url, title, index}. Supports recency and domain filters. Use for questions needing current, sourced information (news about a company, market state, comparisons). For raw search result links use web.search; mode='deep' runs minutes-long exhaustive research — only when explicitly requested.
    Connector
  • Real-time web search via Tavily. Use for current events, fact-checking, and research. Set search_depth='advanced' for complex research queries (higher quality, higher cost). Set topic='news' for recent headlines or 'finance' for market information.
    Connector
  • Search regulatory updates and final rules from the Federal Register, openFDA, and CPSC by industry, agency, type, keyword, or severity — regulatory compliance and compliance monitoring intelligence, newest first. PAID: $0.01 per query after a daily free allowance (25/day). On a 402, settle the returned payment challenge and re-call with the SAME args plus payment_tx=<reference>. agent_id scopes your allowance; an Authorization: Bearer fnet_ key bypasses it.
    Connector
  • Fetch full details for a single FDA 510(k) clearance by K number. Use this after `search_device510k` when you need the complete record for a specific clearance, including the full `summaryText` (the complete 510(k) summary statement, often very long), full `applicant` details (address, contact, country), `registration` info (FEI and registration numbers), and the complete `decision` object (code, description, committee, review flags). The search tool returns a brief highlighted snippet of the summary text; call this tool for a specific K number when you need the full text or detailed applicant/registration information. **Parameters:** - id: K number identifier (e.g. `K210674`). **Returns:** A compact detail record with full summary text, complete applicant information, registration details, and decision metadata.
    Connector
  • Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Connector