Skip to main content
Glama
127,424 tools. Last updated 2026-05-05 16:27

"Systems or platforms that support dynamic registration" matching MCP tools:

  • Check whether a factual claim is supported by a specific set of public evidence URLs that you already have. For each source, the tool performs a case-insensitive keyword match over the fetched page body, then marks that source as supporting the claim when at least half of the supplied keywords appear. Use this for evidence-backed claim checks on known pages, not for open-ended search, semantic reasoning, or contradiction extraction. The aggregate verdict is driven only by the per-page keyword support ratio. Fetched pages are cached for 5 minutes.
    Connector
  • Return the officers of a company - current directors, secretaries, members, partners, board members, procurists / authorised signatories, liquidators, and (by default, where upstream exposes them) historical resignations. Each officer has a unified shape (jurisdiction, officer_id, name, role, appointed_on, resigned_on, is_active) plus a `jurisdiction_data` object carrying the raw upstream fields verbatim. Role labels are passed through in the registry's native language (e.g. Styremedlem, Předseda představenstva, Président, PREZES ZARZĄDU) - translate client-side as needed. Birth-date precision varies by jurisdiction (some registries publish YYYY-MM-DD, some only month + year, some nothing). `officer_id`, when present, can be passed to `get_officer_appointments` to retrieve every other company this person has been appointed to - cross-company tracing is one of the most powerful uses of this tool. Not every jurisdiction issues stable person IDs; corporate officers are usually keyed by the corporate's own company_id, natural persons may be keyed by a synthetic index. Some registries mask officer names under GDPR / privacy rules - that masking is upstream, not server-side. Flags: `include_resigned` (default true) toggles historical entries on jurisdictions that expose both; `group_by_person` deduplicates the same person across consecutive appointments on jurisdictions that support it; `fresh: true` bypasses the cache. Flags are ignored on registries that don't support them. Jurisdictions that don't publish officer data (or that gate it behind paid extracts) return 501. Per-country caveats (role-label vocabulary, birth-date precision, resignation coverage, GDPR masking, 501 gating, delta-vs-snapshot semantics) are available on demand - call `list_jurisdictions({jurisdiction:"<code>"})` for the full schema, or `list_jurisdictions({supports_tool:"get_officers"})` for the country-support matrix. All registries are official government sources.
    Connector
  • Validate a UK VAT registration number against HMRC's official register. Returns whether the VAT number is valid, the registered company name, and registered business address. Use this tool to verify a supplier or customer's VAT registration, confirm trading names match, or check VAT status before issuing invoices. For full company due diligence (officers, filings, distress score), use uk_entity_intelligence instead. Source: HMRC VAT Check API.
    Connector
  • List all 15 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.
    Connector
  • Instant community signal — no registration, no key. Just slug + direction. Use when you want to quickly express trust (up) or distrust (down) on any entity. Community favors are 0.1x weight. For 10x weight, use nanmesh.trust.review instead.
    Connector
  • Set ENS resolver records for a name you own. Returns encoded transaction calldata ready to sign and broadcast. Supports address records (ETH, BTC, SOL, etc.), text records (avatar, description, url, social handles, AI agent metadata), content hash (IPFS/IPNS), ENSIP-25 agent-registration records, and ENSIP-26 agent context and endpoint discovery. Multiple records are batched into a single multicall transaction to save gas. Common text record keys: avatar, description, url, email, com.twitter, com.github, com.discord, ai.agent, ai.purpose, ai.capabilities, ai.category. ENSIP-25 support: Pass agentRegistration with registryAddress and agentId to automatically set the standardized agent-registration text record. This creates a verifiable on-chain binding between your ENS name and your agent identity in an ERC-8004 registry. ENSIP-26 support: Pass agentContext to set the agent-context text record (free-form agent description). Pass agentEndpoints with protocol URLs (mcp, a2a, oasf, web) to set agent-endpoint[protocol] discovery records. The returned transaction can be signed and submitted directly using any wallet framework (Coinbase AgentKit, ethers.js, etc.).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.
    Connector
  • Lists Vocab Voyage's MCP starter prompts (also exposed via the standard MCP prompts/list endpoint). Useful for hosts that don't yet support prompts/list.
    Connector
  • Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.
    Connector
  • Returns information about the supplier network: available destinations, experience categories, booking platforms, and protocol details. Call this before search_slots to understand what regions and activity types are available.
    Connector
  • Submit a support request to the Skala team on behalf of the user. Call this when the user needs human assistance that AI cannot provide, the question is too complex or high-risk, or the user explicitly asks for human support. IMPORTANT: Always confirm with the user before calling — describe what you will submit and ask for their approval. Before calling, compile the issue from conversation context into the description.
    Connector
  • Search the Charity Commission register of England and Wales by name or keyword. Returns matching charities with registration number, status, and registration date. Use charity_profile for full details once you have the charity number. The upstream `searchCharityName` endpoint returns the full list in one shot — pagination is applied client-side via offset/limit.
    Connector
  • Look up a US trademark by serial number. Returns status, owner, filing/registration dates, goods/services, and classification. Requires USPTO API key (free at account.uspto.gov).
    Connector
  • Search for username across 15+ social/dev platforms (GitHub, Reddit, X/Twitter, LinkedIn, Instagram, TikTok, Discord, YouTube, Keybase, HackerOne, etc.). Use for OSINT investigations and identity verification. Free: 100/hr, Pro: 1000/hr. Returns {username, total_found, platforms: [{name, exists, url, status_code}]}.
    Connector
  • Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents
    Connector
  • Render an interactive MCP app mind map when the user needs hierarchical structure shown visually instead of as prose. Use it for breaking down ideas, plans, study material, or systems into a root topic with nested branches; do not use it for tables, flowcharts, Mermaid/Graphviz diagrams, or plain text lists. Input `mindmap_markdown` must be a clean markdown tree with one `#` root heading and 2-space-indented bullet nesting. If the user gives prose, first reshape it into that hierarchy, then call this tool.
    Connector
  • Request a feature or format that Caliper doesn't support yet. Free, no payment required. Use this when you need a capability that Caliper doesn't currently offer — especially unsupported file formats (STEP, IGES) or analysis features not yet available. Requests are logged and used to prioritize development. Privacy policy: https://caliper.fit/privacy
    Connector
  • Validate a UK VAT registration number against HMRC's official register. Returns whether the VAT number is valid, the registered company name, and registered business address. Use this tool to verify a supplier or customer's VAT registration, confirm trading names match, or check VAT status before issuing invoices. For full company due diligence (officers, filings, distress score), use uk_entity_intelligence instead. Source: HMRC VAT Check API.
    Connector
  • Provision a complete ENS identity for an AI agent in one call. Describe your agent's purpose and budget — get back recommended available names, a multi-step registration recipe (commit → register → set agent records), and ready-to-sign transaction data. The registration recipe includes agent identity records (ENSIP-25: ai.agent, ai.purpose, ai.capabilities + ENSIP-26: agent-context) as a mandatory final step — these records make the agent discoverable in the ENS Agents directory. ENSIP-25 agent-registration binding is included when an agentRegistry is provided. IMPORTANT: The calling AI MUST execute all steps in the recipe, including the final set_ens_records step. Agent identity is not complete until the text records are on-chain. Example: "DeFi trading bot, 0.05 ETH budget" → names like swiftswap.eth with full registration + identity setup instructions.
    Connector
  • Validates a Chilean RUT (Rol Único Tributario) — the tax identification number used by individuals and companies in Chile, issued by the SII (Servicio de Impuestos Internos). Applies the official modulo-11 checksum algorithm with check digit 'K' support. Returns { valid: boolean, rut: string, check_digit: string } or { valid: false, reason: string }. Use when processing Chilean DTE electronic invoices, supplier registration, or any Chilean tax compliance workflow. Accepts formats with or without dots and dash.
    Connector