New Company Registrations Feed MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. Required to call the server's tool. | |
| COMPANIES_HOUSE_API_KEY | No | Optional free UK Companies House REST API key. When set, the UK Companies House register is read; without it the UK register is skipped. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_new_company_registrationsA | Find companies newly registered in official business registers: UK Companies House (when the server has a COMPANIES_HOUSE_API_KEY), Norway Brreg, Finland PRH, and France BODACC company creation notices. Filter by registered_within_days, industry_codes (NACE based prefixes such as 62 or 70.2, which work across UK SIC 2007, Norway SN2007, and Finland TOL 2008; France has no codes and is skipped when they are set), activity_keywords (register activity text, France and Norway), name_keywords, and locations. Returns one row per company: register, country, company_number, company_name, registration_date, company_type, company_status, industry_codes, industry_description, activity_description, address, postal_code, city, region, website and domain when listed, share_capital, and register_url. Sole traders are never returned. When nothing matches, one free no_results row says why. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per company row returned plus a run start. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose — finding newly registered companies from specific official registers — is stated unambiguously in the name and description.
The single tool follows a clear snake_case verb_noun convention (find_new_company_registrations) that precisely describes its action and resource. There are no competing or mixed conventions to create inconsistency.
The server wraps a narrowly scoped data feed, so one comprehensive tool is defensible rather than a design flaw. Still, a single-tool surface is thin by the rubric's standards and leaves no room for companion operations such as pagination or detail lookup.
The tool covers multiple registers, rich filtering (date window, industry codes, keywords, location), and a detailed per-company output schema with graceful no-results and error handling. Minor gaps remain: no pagination or result-limit controls, no sorting options, and no way to retrieve a specific company by number or fetch details beyond the feed row.