registry-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPANIES_HOUSE_API_KEY | No | Required for the United Kingdom (GB). A key is free and instant. Unset means GB lookups return upstream_error with a hint naming this variable — every other country keeps working. | |
| REGISTRY_MCP_CACHE_PATH | No | Path to the local SQLite response cache (24 h TTL). Defaults to ./data/cache.sqlite3. | ./data/cache.sqlite3 |
| REGISTRY_MCP_CONTACT_EMAIL | No | Contact address sent in the User-Agent to the national registry, as Brønnøysundregistrene asks of API clients. Unset means an anonymous client, which may be throttled or blocked upstream. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_companyA | Look up a company by its national identifier and get the full CompanyReport — legal form, status, address, VAT registration where the register publishes it, board and accounts duties, employees, and more.
Use it once you have the identifier — from the user, an invoice, a contract, or a
On error, this tool raises with the error text |
| search_companyA | Search a national company register by name, when you have a name rather than an identifier.
Use it when a user gives you a company name, then call On error, this tool raises with the error text |
| company_deadlinesA | Give the next occurrence of each statutory filing deadline a company faces.
Pass On error, this tool raises with the error text |
| validate_company_idA | Check whether a national company identifier is well-formed — no network call.
Use it on user input or a spreadsheet column before spending a real Returns a ValidationResult and never raises for a malformed identifier: The only real error here is |
| list_countriesA | List every national company registry this service can answer for right now, plus
each one's identifier scheme ( Call this before your first lookup in a country you have not used here before, or whenever a user names a country you are unsure is supported — never hard-code a country list of your own, since it grows as registry modules are added with no change to any other tool's shape. Stub/example modules are hidden; only registries that actually answer are listed. This tool has no error mode; a failure here is a bug, not something to retry differently. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explain_company | Explain one company for a non-expert reader: call lookup + deadlines and summarise. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct role: search by name, lookup by identifier, validate identifiers locally, list supported countries, and retrieve filing deadlines. There is no ambiguity between them, and the descriptions reinforce when to use which.
Most tools follow a clear verb_noun pattern: lookup_company, search_company, validate_company_id, list_countries. company_deadlines breaks the pattern slightly by leading with the noun rather than a verb, but the set remains highly readable and predictable.
Five tools is well-scoped for a company registry MCP server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The tool surface covers the full user journey: discover supported countries, validate an identifier, search by name, fetch the full company report, and retrieve statutory deadlines. There are no obvious dead ends or missing operations for the stated registry-lookup domain.