A
licenseA
qualityB
maintenanceUK due diligence MCP server — Companies House, corporate research, compliance checks
19
3
MIT
qorenext-mcp
Server Details
Company hierarchy analysis and address verification via MCP
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
- QoreNext-IT/QoreNextMCP
- GitHub Stars
- 0
- Server Listing
- QoreNextMCP
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- Added
submit_address_verification - Removed
submit_entities - Added
submit_hierarchy_creation
1 tool update
- Changed
get_request_status2 fields changed- added
Input schema / properties / request_id / descriptionAdded value: +"Integer ID of the request to check (required)" - added
Input schema / properties / screening_typeAdded value: +{ + "default": "Verification", + "description": "Type of screening - \"Verification\", \"Hierarchy\", or \"Dedup\" (default: \"Verification\")", + "type": "string" +}
1 tool update
- Added
submit_duplicates
3 tool updates
- First observed
get_request_status - First observed
health_check - First observed
submit_entities
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
Corporate identity finder and email verification. Map real addresses and users to real people.
B2B data enrichment for 375M+ companies: legal entities, corporate hierarchies, and contacts.
Remote MCP server to enrich company profiles with structured B2B data and confidence scores.
Cadastral investigation of people and companies: location, corporate ties/relationships, participati
Related MCP Servers
- AlicenseAqualityCmaintenanceCompanyLens MCP gives your AI assistant access to real corporate data from official government sources. No web scraping, no hallucinations — verified data from SEC EDGAR, UK Companies House, OpenSanctions, and USAspending.gov.52014MIT
- AlicenseNot gradedqualityCmaintenanceHosted MCP server providing corporate ownership intelligence, enabling AI agents to look up parent companies, PE backing, corporate families, and portfolio siblings via natural language queries.1MIT
- AlicenseNot gradedqualityCmaintenanceMaps corporate affiliations of a Brazilian individual from CPF for anti-money laundering (AML) due diligence. Read-only hosted MCP server with one tool, works with any MCP-compatible client.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
Disambiguation5/5
Each tool addresses a distinct purpose: health check, request status retrieval, and three specific submission types (address verification, duplicates, hierarchy). No two tools overlap in function, making selection unambiguous.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern: get_request_status, health_check, submit_address_verification, submit_duplicates, submit_hierarchy_creation. The 'submit_' prefix uniformly marks submission operations.
Tool Count5/5
With 5 tools, the server is well-scoped for its domain of corporate screening. Each tool covers a distinct operation without redundancy, fitting the typical 3-15 tool range.
Completeness4/5
The server covers the core screening workflow: submit three types of requests and retrieve their status/results. Minor administrative operations like listing or canceling requests are missing, but the main lifecycle is complete.