corporate_registry_lookup

SERVERMcp Knowledge SOURCEhttps://mcp.gapup.io

Low RISK CLASS

Category Read

Parameters 41 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-getgapup-mcp-knowledge/corporate-registry-lookup.md

WHAT IT DOES

What corporate_registry_lookup does on Mcp Knowledge

AI agents call corporate_registry_lookup to retrieve information from Mcp Knowledge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`async`	boolean	—	If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti
`country`	string	—	ISO 3166-1 alpha-2 country code (e.g. 'FR', 'GB', 'NL', 'DE', 'SG', 'AU', 'US'). If omitted, inferred from legal suffix in company name, then falls back to glob
`identifier`	string	—	Optional registry identifier for a fast direct lookup: SIREN (FR, 9 digits), Companies House number (GB, 8 chars), KvK number (NL, 8 digits), etc.
`company_name`	string	Yes	Company name or trading name to look up (e.g. 'Sanofi', 'Tesco PLC', 'Notion Labs Inc')

Parameters from the server's own tool schema.

RISK

Why corporate_registry_lookup is rated Low

This tool purely retrieves and aggregates publicly available corporate registry data. There are no write, execute, destructive, or financial operations. It queries multiple data sources and normalizes results but does not modify, delete, or trigger external actions. The low severity reflects that misuse (e.g., gathering competitor intelligence) is a business concern but not a technical risk vector.

From the tool's definition Tool description states it 'Resolve[s] legal information about a company from its national corporate registry' and 'Returns a normalised, sourced company profile' including 'legal status, registration number, directors, shareholders, recent filings,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs corporate_registry_lookup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For corporate_registry_lookup, this is the rule to start with:

corporate_registry_lookup Allowed

corporate_registry_lookup is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "corporate_registry_lookup": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Knowledge, apply this rule, and every corporate_registry_lookup call is checked against it from then on.

FAQ

Questions about corporate_registry_lookup

What does the corporate_registry_lookup tool do? +

Resolve legal information about a company from its national corporate registry. Returns a normalised, sourced company profile: legal status, registration number, directors, shareholders, recent filings, registered address, share capital, and a quality score (0–100). Coverage: France (INPI, keyless — full SIREN/SIRET with directors), 3M+ entities worldwide via GLEIF LEI (keyless, large companies), UK (Companies House, optional key), Netherlands (KvK, optional key), and OpenCorporates (token required since 2026). Sources are tried in cascade; quality_score increases with each source that succeeds. When to use: due-diligence, KYC screening, supplier verification, M&A research, or any workflow needing verified company identity and legal status. Optional env vars: COMPANIES_HOUSE_API_KEY (UK), KVK_API_KEY (NL), OPENCORPORATES_API_TOKEN (OpenCorporates token). It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.

What parameters does corporate_registry_lookup accept? +

corporate_registry_lookup accepts 4 parameters: async, country, identifier, company_name. Required: company_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on corporate_registry_lookup? +

Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for corporate_registry_lookup: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Knowledge. Nothing to install.

What risk level is corporate_registry_lookup? +

corporate_registry_lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit corporate_registry_lookup? +

Yes. Add a rate_limit block to the corporate_registry_lookup rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block corporate_registry_lookup completely? +

Set action: deny in the PolicyLayer policy for corporate_registry_lookup. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides corporate_registry_lookup? +

corporate_registry_lookup is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Knowledge, and thousands of servers like it.

This server

All 271 Mcp Knowledge tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →