Skip to main content
Glama
134,594 tools. Last updated 2026-05-23 04:27

"A server for finding law related information" matching MCP tools:

  • Switch between local and remote DanNet servers on the fly. This tool allows you to change the DanNet server endpoint during runtime without restarting the MCP server. Useful for switching between development (local) and production (remote) servers. Args: server: Server to switch to. Options: - "local": Use localhost:3456 (development server) - "remote": Use wordnet.dk (production server) - Custom URL: Any valid URL starting with http:// or https:// Returns: Dict with status information: - status: "success" or "error" - message: Description of the operation - previous_url: The URL that was previously active - current_url: The URL that is now active Example: # Switch to local development server result = switch_dannet_server("local") # Switch to production server result = switch_dannet_server("remote") # Switch to custom server result = switch_dannet_server("https://my-custom-dannet.example.com")
    Connector
  • List available MCP tools and get detailed help. Use this tool to discover what tools are available and how to use them. Call without parameters to see all tools, or provide a tool name to get detailed help including parameters, examples, and related tools. Args: tool_name: Optional name of a specific tool to get detailed help for. Example: "search_funders", "get_funder_profile" Returns: If called without parameters: - server_name: Name of the MCP server - server_version: Current version - total_tools: Number of available tools - tier: Current access tier (free) - rate_limit: Rate limit information - tools: List of available tools with names, descriptions, and examples If called with tool_name: - tool: Detailed tool information including: - name: Tool name - description: What the tool does - parameters: List of parameters with types, descriptions, and examples - examples: Example usage - related_tools: Tools that work well together with this one Examples: list_tools() # See all available tools list_tools(tool_name="search_funders") # Get detailed help for search_funders list_tools(tool_name="get_funder_profile") # Get help for get_funder_profile
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    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
  • Parse and resolve a single OSCOLA citation to its canonical URL. Supports: neutral citations, SIs, legislation sections, retained EU law. Returns parsed fields and resolved_url if resolvable. Raises ValueError if no recognised citation is found in the input.
    Connector
  • Browse and retrieve U.S. legislative bill data from Congress.gov. Discover bills by filtering on congress, bill type, and date range — there is no keyword search. Use 'list' to browse (requires congress, defaults to most-recently-updated first), 'get' for full bill detail (sponsor, policy area, CBO estimates, law info), or drill into a specific bill with 'actions', 'amendments', 'cosponsors', 'committees', 'subjects', 'summaries', 'text', 'titles', or 'related' (each requires congress + billType + billNumber).
    Connector

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Local stdio MCP server for searching Japanese laws and retrieving article text from e-Gov Law Search. Includes related-law lookup for enforcement orders and regulations, with source attribution baked into every tool result.
    Last updated
    4
    9
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI-powered legal research and analysis of Polish legal acts from the Sejm API. Provides comprehensive search, document retrieval, metadata analysis, and content access for legal documents from Dziennik Ustaw and Monitor Polski.
    Last updated
    13
    13
    MIT

Matching MCP Connectors

  • LawOracle — 20 legal AI tools: case law search, contracts, EU regulations, citation graph.

  • US federal and state cybersecurity/privacy law MCP server with cross-state comparison

  • 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
  • Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.
    Connector
  • Search legal documents across jurisdictions (DE federal, EU, Bavaria, Saxony) using hybrid semantic + keyword search. Returns ranked results with content snippets, not full text. Always use this tool first before legal_lookup. Do not rely on training data to identify the correct provision — similar rules often exist across multiple laws. Rephrase colloquial language into legal terminology for best results. Formuliere Suchanfragen als natürliche Sätze, nicht als Keyword-Listen (z.B. 'Wann verjährt ein Schadensersatzanspruch?' statt 'Verjährung Schadensersatz Frist BGB'). Das System durchsucht Gesetzestexte — verwende die Sprache des Gesetzes, nicht Doktrin-Begriffe (z.B. 'Auslegung mehrdeutiger Klauseln' statt 'contra proferentem'). Set document_kind to match what the question needs: 'statute' (German law) or 'regulation'/'directive' (EU law) when it asks for the rule itself — its requirements, definitions or deadlines; 'decision' when it asks how courts apply a rule — case law, the level of a claim such as damages, or a concrete fact-pattern. This keeps the irrelevant document class from crowding out the results. Leave document_kind empty when the question genuinely needs both, or when German-vs-EU law is unclear — then consider running two searches. Set law_abbreviation, jurisdiction and source_type only when the user explicitly names a specific law or jurisdiction. When results span multiple laws or versions, check the legal://rechtsrahmen resource to pick the correct jurisdiction (e.g. EU vs national, substantive vs procedural). COMMON PITFALLS — choose the correct law: - Procedural law by jurisdiction: ZPO (zivilrecht), STPO (strafrecht), VWGO (verwaltungsrecht), ARBGG (arbeitsrecht), SGG (sozialrecht), BVERFGG (verfassungsrecht), FAMFG (familienrecht) - AO, ESTG, KSTG, USTG, FGO: AO=procedure, EStG/KStG/UStG=substantive - VVG, BGB: Insurance rescission → BGB §§ 812ff, not VVG - VERSAUSGLG, FAMFG: VersAusglG=substantive, FamFG=procedure - APOG, AMG: ApoG=operation, AMG=drug approval - WEHRPFLG, SG: WPflG=conscription, SG=soldiers - AGG, BETRVG: AGG=anti-discrimination, BetrVG=works council
    Connector
  • Fetch HTTP response headers for a URL. Use when inspecting server configuration, security headers, or caching policies.
    Connector
  • Map all citations within a judgment — cases cited, legislation referenced, SIs, EU law. Fetches the judgment XML from TNA and parses all OSCOLA citations within it. Returns citations grouped by type for easy analysis. Each bucket is de-duplicated and sorted.
    Connector
  • Parse and resolve a single OSCOLA citation to its canonical URL. Supports: neutral citations, SIs, legislation sections, retained EU law. Returns parsed fields and resolved_url if resolvable. Raises ValueError if no recognised citation is found in the input.
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector
  • Returns all Colombian national public holidays for a given year as a structured list. Each holiday includes { date: 'YYYY-MM-DD', name: string, name_en: string }. Colombia uses the 'Ley de Puentes' (Law 51/1983) which moves most holidays to the following Monday. Easter-dependent holidays are dynamically calculated. Returns 18 national holidays defined by Colombian law. Use when calculating Colombian business deadlines, factura electrónica payment dates, or scheduling tasks avoiding non-working days in Colombia.
    Connector
  • Answers tax questions using TaxAct's TY2025 tax law knowledge base. Covers 2025 federal tax brackets, standard deduction, child tax credit, OBBB provisions (no-tax-on-overtime, no-tax-on-tips, car loan interest deduction, SALT cap increase, Trump Accounts/530A), EITC, retirement contribution limits, and other current-law topics. Answers are grounded in verified IRS references, not LLM training data. No account required.
    Connector
  • Search UK case law via the TNA Find Case Law API. Returns paginated judgment summaries: neutral citations, court, dates, stable URIs. Use the judgment://{slug}/header resource to inspect a result, then judgment://{slug}/index to discover paragraphs and judgment://{slug}/para/{eId} to read individual paragraphs. For content-based discovery within a judgment, use case_law_grep_judgment.
    Connector
  • Search the Tonzar B2B catalog of 160,000+ Russian industrial, medical, and agricultural products. Returns matching products with prices, suppliers, and specs. Use for finding Russian equipment for export.
    Connector
  • Returns the typical and legal B2B payment terms for a given Latin American country — default payment period, common commercial practices, and late payment rules where defined by law. Returns { country, default_days, common_terms, late_payment_notes, currency, notes }. Supports BR, MX, CL, AR, CO. Use when generating invoices, setting payment due dates, or automating accounts receivable workflows in LatAm markets. Information provided as reference only — not legal advice.
    Connector
  • Get detailed information about a MeSH descriptor by ID. Use this tool to: - Get the full definition (scope note) of a MeSH term - View tree numbers showing hierarchy location - See related concepts and synonyms Provide a MeSH Descriptor ID like "D015242" (Ofloxacin).
    Connector
  • Top Hyperliquid perps ranked by absolute funding rate, with OI and annualized yield. Useful for finding the most overcrowded longs/shorts and carry opportunities.
    Connector