"namespace:co.okahu.mcp-registry" matching MCP tools:

• compare_entities

  Npi Registry

  Compare 2–5 companies (or drugs) side by side in one call. Use when a user says "compare X and Y", "X vs Y", "how do X, Y, Z stack up", "which is bigger", or wants tables/rankings of revenue / net income / cash / debt across companies — or adverse events / approvals / trials across drugs. type="company": pulls revenue, net income, cash, long-term debt from SEC EDGAR/XBRL for tickers like AAPL, MSFT, GOOGL. type="drug": pulls adverse-event report counts (FAERS), FDA approval counts, active trial counts. Returns paired data + pipeworx:// citation URIs. Replaces 8–15 sequential agent calls.

  Connector

• estimate_market

  Ground Truth

  Search npm or PyPI to estimate how crowded a package category is before you claim that a market is empty, niche, or competitive. Use this when you have a category or search phrase such as 'edge orm' and want live result counts plus representative matches. Do not use it to compare exact known package names or to infer adoption from downloads; it reflects search results, not market share. Registry responses are cached for 5 minutes.

  Connector

• search_indicators

  American Default Research

  Search the 96-indicator registry by keyword. Returns ranked matches (up to `limit`, default 10, max 50) with slug, branded name, underlying name, category, and canonical URL. Scoring is substring+prefix over slug, branded_name, name, and category — e.g. query 'savings' returns both The Buffer (personal saving rate) and The Safety Net (emergency savings survey). Use this when you want to discover which slug corresponds to a concept before calling `get_indicator`.

  Connector

• list_pillars

  Bidda Sovereign Intelligence

  List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance domains before searching. Bidda has 5,419 cryptographically-verified nodes across 34 pillars + 203 MITRE nodes across 6 frameworks (ATT&CK Enterprise/Mobile/ICS, D3FEND, ATLAS, CAPEC) including Banking, AI Governance, Cybersecurity, Healthcare, Legal, ESG and more.

  Connector

• search_officers

  openregistry

  Find people holding or who held officer positions (director, secretary, member, partner) in a jurisdiction's registry by name. Returns candidates with officer_id, name, and (where exposed) appointment count. Entry point for person-centric investigations. Use this when only the person's name is known. If you already have the `company_id`, call `get_officers` instead — it returns the authoritative board roster for that company; this tool is a name-search index and may miss officers whose names are redacted, transliterated, or stored under a former spelling upstream. Read-only — no upstream mutation, results briefly cached. Name-matching semantics vary per registry (exact / prefix / token / fuzzy); full names work best, partial names broaden recall. `query` matches against the registry's officer name index only — not a free-text web search — so role keywords, synonyms, or company names won't match. `limit` is an upper bound capped at 100; the registry may return fewer. Unsupported jurisdictions return 501; call `list_jurisdictions({supports_tool:'search_officers'})` for the coverage matrix.

  Connector

• polymarket_arbitrage

  Npi Registry

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• compare_competitors

  Ground Truth

  Compare two or more exact package names side by side using live npm or PyPI metadata. Use this when you already know the candidate packages and need evidence for claims such as 'tool A is newer', 'tool B is still maintained', or 'these packages use different licenses'. It returns per-package registry metadata in input order, with field availability varying by registry. Missing or unpublished packages return found=false. Do not use it to discover unknown alternatives, estimate market size, or compare packages across different registries. Registry responses are cached for 5 minutes.

  Connector

• entity_profile

  Npi Registry

  Get everything about a company in one call. Use when a user asks "tell me about X", "give me a profile of Acme", "what do you know about Apple", "research Microsoft", "brief me on Tesla", or you'd otherwise need to call 10+ pack tools across SEC EDGAR, SEC XBRL, USPTO, news, and GLEIF. Returns recent SEC filings, latest revenue/net income/cash position fundamentals, USPTO patents matched by assignee, recent news mentions, and the LEI (legal entity identifier) — all with pipeworx:// citation URIs. Pass a ticker like "AAPL" or zero-padded CIK like "0000320193".

  Connector

• get_protocol_registry

  MegaChad

  Canonical machine-readable registry of every MEGA Protocol contract: tokens (MEGACHAD, MEGAGOONER), AMM pair (MC/MG), staking (MoggerStaking, JESTERGOONER), governance (Jestermogger, NFTVetoCouncil, Framemogger), emissions (EmissionController), and safety (CircuitBreaker). Includes addresses, proxy/impl, ABIs, known gotchas, and direct links to all agent endpoints. Pull this FIRST for any DeFi interaction.

  Connector

• discover_tools

  Npi Registry

  Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names + descriptions. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

  Connector

• list_skills

  Hatchable

  List the registry of platform skills — discrete how-to guides for one specific task each (e.g. 'gate-an-endpoint', 'add-a-cron-job', 'add-rag-search'). Each entry is a name, one-line purpose, and category. Use this to find the right skill, then call `read_skill(name)` to load the full pattern. When in doubt about how a Hatchable feature works, **list_skills first**. The skills are the canonical, agent-tested patterns. They beat guessing or reading the verbose docs. Filter by `query` (matches name + purpose) or `tag` (auth, data, ai, ops, etc.). Without filters, returns the full registry (~35 entries).

  Connector

• em_get_reputation

  Execution Market

  Get on-chain reputation for an agent from the ERC-8004 Reputation Registry. Provide either agent_id (numeric ERC-8004 token ID) or wallet_address. Args: agent_id: ERC-8004 agent token ID (e.g. 2106) wallet_address: Agent's wallet address (resolved to agent_id) network: ERC-8004 network (default: "base") Returns: Reputation score, rating count, and network info.

  Connector

• validate_counterparty_lite

  Bizfile MCP

  Call this when your agent needs fast company verification without AI scoring — registry check only, low token cost, sub-second response. Returns company status, registration number, registered address, and filing status directly from UK Companies House, Singapore ACRA, or OpenCorporates (130+ jurisdictions). Use for high-volume screening workflows where speed matters more than risk scoring. Machine-readable JSON — no parsing needed.

  Connector

• em_rate_worker

  Execution Market

  Rate a worker after reviewing their submission. Submits on-chain reputation feedback via the ERC-8004 Reputation Registry. If no score is provided, a dynamic score is computed from the submission. Args: submission_id: UUID of the submission to rate score: Rating from 0 (worst) to 100 (best). Optional — auto-scored if omitted. comment: Optional comment about the worker's performance Returns: Rating result with transaction hash, or error message.

  Connector

• dossier_whois

  drwho.me developer tools

  Core dossier check: Look up the registrar, creation date, expiry date, and registry statuses for a domain. Use for ownership/expiry audit. Queries WHOIS over TCP/43 via the `whoiser` library; 15s timeout. Returns a CheckResult; not_applicable when the registry refuses or redacts the query (common on cloud IPs).

  Connector

• mitigation_receipt

  InsureLink

  Verifies a claim_breach_credit transaction by tx hash and returns a canonical mitigation receipt suitable for insurer/registry attestations. Reads from existing on-chain settlement records — no new state. Requires x402 payment ($0.001). Returns payment instructions.

  Connector

• em_rate_agent

  Execution Market

  Rate an AI agent after completing a task (worker -> agent feedback). Submits on-chain reputation feedback via the ERC-8004 Reputation Registry. Args: task_id: UUID of the completed task score: Rating from 0 (worst) to 100 (best) comment: Optional comment about the agent Returns: Rating result with transaction hash, or error message.

  Connector

• thinkneo_bridge_mcp_to_a2a

  ThinkNEO Control Plane

  Bridge MCP tool registry to A2A format. Shows tool-to-skill mappings.

  Connector

• policy_register

  agentguard

  View the central policy registry. Query tiers (T1-T4), tool classifications, escalation rules. Actions: summary (default), lookup (by tool_name), tiers, rules, tools (by tier_id).

  Connector

• reclaim_name

  Name Whisper — ENS Intelligence Layer

  Reclaim ENS Registry ownership of a .eth name. This syncs the ENS Registry owner to match the BaseRegistrar token owner. Used when: - A name was transferred via direct safeTransferFrom (bypassed ENS routing) - ENS Registry ownership is out of sync with token ownership - Recovery after a contract migration or edge case The caller must own the BaseRegistrar ERC-721 token for the name. After reclaiming, you may also need to set the resolver if it was cleared.

  Connector