io.github.QoreNext-IT/qorenext-mcp
REMOTE · MCP.QORENEXT.COM · SCANNED SEP 20
Company hierarchy analysis and address verification via MCP
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.QoreNext-IT/qorenext-mcp server?
io.github.QoreNext-IT/qorenext-mcp is a hosted endpoint at https://mcp.qorenext.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.qorenext.com
claude mcp add --transport http qorenext-it-qorenext-mcp 'https://mcp.qorenext.com/mcp/'
{
"mcpServers": {
"qorenext-it-qorenext-mcp": {
"url": "https://mcp.qorenext.com/mcp/"
}
}
} {
"servers": {
"qorenext-it-qorenext-mcp": {
"type": "http",
"url": "https://mcp.qorenext.com/mcp/"
}
}
} [mcp_servers.qorenext-it-qorenext-mcp] url = "https://mcp.qorenext.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qorenext-it-qorenext-mcp": {
"type": "remote",
"url": "https://mcp.qorenext.com/mcp/",
"enabled": true
}
}
} openclaw mcp add qorenext-it-qorenext-mcp --url 'https://mcp.qorenext.com/mcp/' --transport streamable-http
mcp_servers:
qorenext-it-qorenext-mcp:
url: "https://mcp.qorenext.com/mcp/" {
"McpServers": {
"qorenext-it-qorenext-mcp": {
"Transport": "http",
"Url": "https://mcp.qorenext.com/mcp/"
}
}
} assistant mcp add qorenext-it-qorenext-mcp -t streamable-http -u 'https://mcp.qorenext.com/mcp/'
{
"mcpServers": {
"qorenext-it-qorenext-mcp": {
"type": "http",
"url": "https://mcp.qorenext.com/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Aug 26 20
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 3 Aug 26 0
- Stability: 0.23 → fail ▼ security
- A breaking change shipped without a version bump: still 3.0.0 ▼ security
- Tool “submit_entities” was removed ▼ security
- Schema quality: 65 → 105 ▼ functional
- Tool coverage: 83% → 100% ▲ functional
- New tool “submit_address_verification” functional
- New tool “submit_hierarchy_creation” functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Tool “get_request_status” rewrote its description, which is the text the model reads security
- Schema quality: 58 → 65 ▼ functional
- Tool coverage: 60% → 83% ▲ functional
- Schema quality: fair → good functional
- “get_request_status” added an optional parameter “screening_type” cosmetic
- “get_request_status” reworded the description of “request_id” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.qorenext.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.qorenext.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 22 Aug 2026 | 22 Feb 2027 | RSA 2048 | SHA256-RSA | be219b3cd1faf9cb57ab742c9954be0 |
| SANs: mcp.qorenext.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.qorenext.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| qorenext.com. | present | 8468, 25079 | 13, 13 | Verified |
| mcp.qorenext.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.qorenext.com/mcp/ | HTTP error | 404 | |
| http (plaintext) | http://mcp.qorenext.com/mcp/ | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_request_status ~96
Get screening request status and results. Check if request is complete (PENDING/PROCESSING/COMPLETE/FAILED) and retrieve results. Returns organizational hierarchy, company verification, or deduplication screening data.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | integer | yes | Integer ID of the request to check (required) |
| screening_type | string | – | Type of screening - "Verification", "Hierarchy", or "Dedup" (default: "Verification") |
Structured output declared, but exposes no named fields.
No examples provided.
health_check ~43
Check MCP server health status. Verify this server is operational and get basic server information (name, version, auth method). Use for connectivity testing and diagnostics. No authentication required.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
submit_address_verification ~159
Submit companies for address verification. Validate company addresses and verify organization legitimacy. Returns entity IDs for tracking verification results.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | List of company objects with: - companyName: Company name (required) Aliases: "name", "entityName" Example: "Acme Corp", "Apple Inc" - country: Country name (required)… |
Structured output declared, but exposes no named fields.
No examples provided.
submit_duplicates ~81
Submit duplicate entities from file. Upload JSON, CSV, or Excel files containing duplicate account records for deduplication detection.
| Name | Type | Req | Description |
|---|---|---|---|
| file_content | string | yes | File content as base64 or raw text |
| file_name | string | – | Original filename for reference |
| file_type | string | yes | File format: "json" | "csv" | "excel" |
Structured output declared, but exposes no named fields.
No examples provided.
submit_hierarchy_creation ~146
Submit companies for organizational hierarchy creation. Identify parent-subsidiary relationships and organizational structure. Returns entity IDs for tracking hierarchy results.
| Name | Type | Req | Description |
|---|---|---|---|
| entities | array | yes | List of company objects with: - companyName: Company name (required) Aliases: "name", "entityName" Example: "Acme Corp", "Apple Inc" - country: Country name (required)… |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.QoreNext-IT/qorenext-mcp server?
io.github.QoreNext-IT/qorenext-mcp is listed in the public MCP registry as io.github.QoreNext-IT/qorenext-mcp. Company hierarchy analysis and address verification via MCP. This page covers its hosted endpoint (https://mcp.qorenext.com/mcp/).
Is the io.github.QoreNext-IT/qorenext-mcp server safe to use?
io.github.QoreNext-IT/qorenext-mcp scores 20 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.QoreNext-IT/qorenext-mcp server expose?
io.github.QoreNext-IT/qorenext-mcp exposes 5 tools: health_check, submit_address_verification, submit_hierarchy_creation, get_request_status, submit_duplicates. Their descriptions and schemas cost roughly 525 tokens of context every time the server is loaded.
Does the io.github.QoreNext-IT/qorenext-mcp server require authentication?
No. We connected to io.github.QoreNext-IT/qorenext-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.QoreNext-IT/qorenext-mcp server still maintained?
io.github.QoreNext-IT/qorenext-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.