F
licenseB
qualityC
maintenanceProvides access to UK Companies House public data, enabling search and retrieval of company profiles, officers, filing history, and more through natural language queries.
12
-
SIC Codes UK
Server Details
UK SIC code lookup, GICS/ICB mapping, and Companies House search. 731 codes, 5.6M companies.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jackmmaher/siccodes.co.uk
- GitHub Stars
- 0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
search_companies1 field changed- changed
Input schema / properties / cursor / descriptionPrevious value: -"Pagination cursor from previous response"New value: +"Pagination cursor from previous response. Invalid or expired cursors return an invalid_cursor error - restart pagination without the cursor parameter."
- Changed
search_uk_companies_by_industry1 field changed- changed
Input schema / properties / cursor / descriptionPrevious value: -"Pagination cursor from a previous response's next_cursor field"New value: +"Pagination cursor from a previous response's next_cursor field. Invalid or expired cursors return an invalid_cursor error - restart pagination without the cursor parameter."
3 tool updates
- Changed
browse_classification_hierarchy2 fields changed- changed
Input schema / properties / system / descriptionPrevious value: -"Classification system to browse: sic, gics, or icb"New value: +"Classification system to browse: sic (SIC 2007), sic2026 (SIC 2026 — the new system), gics, or icb" - changed
Input schema / properties / system / enumPrevious value: -[ - "sic", - "gics", - "icb" -]New value: +[ + "sic", + "sic2026", + "gics", + "icb" +]
- Changed
convert_between_classifications3 fields changed- changed
Input schema / properties / code / descriptionPrevious value: -"The classification code to convert (e.g. '6202' for SIC class, '45102030' for GICS sub-industry)"New value: +"The classification code to convert (e.g. '62020' for SIC 2007, '6201' for SIC 2026, '45102030' for GICS sub-industry)" - changed
Input schema / properties / from / enumPrevious value: -[ - "sic", - "gics", - "icb" -]New value: +[ + "sic", + "sic2026", + "gics", + "icb" +] - changed
Input schema / properties / to / enumPrevious value: -[ - "sic", - "gics", - "icb" -]New value: +[ + "sic", + "sic2026", + "gics", + "icb" +]
- Changed
lookup_sic_code3 fields changed- changed
Input schema / properties / code / descriptionPrevious value: -"The classification code to look up (e.g. '62020' for SIC, 'J' for SIC section, '45' for GICS sector, '1010' for ICB supersector)"New value: +"The classification code to look up (e.g. '62020' for SIC 2007, '6201' for SIC 2026, 'J' for section, '45' for GICS sector, '1010' for ICB supersector)" - changed
Input schema / properties / system / descriptionPrevious value: -"Which classification system the code belongs to: sic (UK SIC 2007), gics (MSCI Global Industry Classification Standard), or icb (FTSE Russell Industry Classification Benchmark)"New value: +"Which classification system the code belongs to: sic (UK SIC 2007), sic2026 (UK SIC 2026 — the new classification), gics (MSCI Global Industry Classification Standard), or icb (FTSE Russell Industry Classification Benchmark)" - changed
Input schema / properties / system / enumPrevious value: -[ - "sic", - "gics", - "icb" -]New value: +[ + "sic", + "sic2026", + "gics", + "icb" +]
8 tool updates
- First observed
browse_classification_hierarchy - First observed
convert_between_classifications - First observed
get_industry_profile - First observed
lookup_sic_code - First observed
lookup_uk_company - First observed
search_companies - First observed
search_sic_codes - First observed
search_uk_companies_by_industry
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
UK company data: profiles, iXBRL financials, directors, PSC chains, ECCTA. Hosted, no key.
Search UK companies, land registry prices, charities, OS locations, and traffic data
Singapore business directory. Search companies, UENs, and SSIC industry classifications.
Singapore business directory. Search companies, UENs, and SSIC industry classifications.
Related MCP Servers
- AlicenseAqualityDmaintenanceUnmodified government company data from 27 registries, live. Cross-border UBO chain walker for AI agents. 60+ tools covering GB, IE, NO, FR, DE, NL, PL, BE, CH, LI, MC, IM, IS, CY, AU, NZ, CA, TW, HK, MY, FI, CZ, ES, IT, KR, US — raw upstream fields preserved, no LLM extraction.1017Apache 2.0
companieswiseofficial
AlicenseAqualityBmaintenanceProvides verified UK company lookup and number validation for AI agents using official Companies House data. Enables lookup of registered details by number, validation of company number format, and search by company name.354Apache 2.0- FlicenseNot gradedqualityBmaintenanceProvides instant access to verified, enriched business intelligence for any UK company, including legal identity, financial health, web presence, and hiring activity in a single call.-
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.3/5.0
Disambiguation5/5
Each tool has a distinct purpose: browsing hierarchy, converting classifications, getting industry profiles, looking up codes or companies, and searching. No two tools overlap significantly, making selection unambiguous.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., browse_classification_hierarchy, search_sic_codes). The verbs are appropriate and the naming is predictable.
Tool Count5/5
With 8 tools, the server is well-scoped for its purpose. It covers browsing, searching, converting, and looking up classification codes and company data without being too sparse or bloated.
Completeness4/5
The tools cover essential operations: browsing hierarchy, searching codes by description, converting between systems, looking up codes/companies, and getting industry profiles. Minor gaps like lacking direct retrieval of classification system metadata are acceptable.