Open Corporates

Get Company

get_company

Read-onlyIdempotent

Get full details for a specific company by jurisdiction and company number. Returns registration details, officers, filings, and industry codes. REQUIRES your own OpenCorporates API token via _apiKey — their public API is closed and keyless calls return 401. Example: get_company({jurisdiction:"us_de", number:"4483789", _apiKey:"..."}) for a Delaware company.

Input Schema

TableJSON Schema

Name	Required	Description
`number`	Yes	Company registration number
`_apiKey`	No	Your OpenCorporates API token (required — get one at https://opencorporates.com/api_accounts/new)
`jurisdiction`	Yes	Jurisdiction code (e.g., "us_de" for Delaware, "gb" for UK, "ca_on" for Ontario)

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Company name
`type`	No	Company type
`status`	No	Current company status
`agent_name`	No	Registered agent name
`jurisdiction`	No	Jurisdiction code
`registry_url`	No	URL to official registry
`branch_status`	No	Branch status if applicable
`company_number`	No	Company registration number
`industry_codes`	No	Industry classification codes
`previous_names`	No	Previous company names
`dissolution_date`	No	Date of dissolution if applicable
`incorporation_date`	No	Date of incorporation
`opencorporates_url`	No	OpenCorporates profile URL
`registered_address`	No	Full registered address

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 28, 2026

addedInput schema / properties / _apiKey

Added value: +{
+  "description": "Your OpenCorporates API token (required — get one at https://opencorporates.com/api_accounts/new)",
+  "type": "string"
+}

First observedJun 26, 2026

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds useful context about authentication requirements and the types of data returned, but does not disclose rate limits or other potential behavioral nuances. With annotations providing the safety profile, the description's additional context earns a 3.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences plus an example, conveying all necessary information without redundancy. It is front-loaded with the primary action and clearly structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description appropriately lists returned data types (registration details, officers, filings, industry codes) without duplicating schema content. This is sufficient for the tool's moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter descriptions are already complete. The description provides an example call with specific values and lists jurisdiction examples, but this adds limited new semantic meaning beyond the schema baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('company'), clearly identifying that it retrieves full details for a specific company by jurisdiction and number. It distinguishes from search tools like search_companies by focusing on a single entity lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states the requirement for an OpenCorporates API token and warns that keyless calls return 401, providing clear context for when this tool should be used. It does not, however, explicitly mention when not to use it or name alternatives, but the prerequisite is well-covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Open Corporates tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.