CorpusIQ
REMOTE · MCP2.CORPUSIQ.IO · SCANNED SEP 20
Authenticated, user-scoped MCP connectors for 30+ business systems.
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 50359 tokens (~307/item across 164 items; 121 tools + 43 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability check failed: schema churn in the 30 days we've observed: 16 tool removals, 0 breaking changes, 0 auth/transport breaks, 11 additions. See how to fix → Fail
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
- Structured output schemas are declared (9% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 123 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the CorpusIQ MCP server?
CorpusIQ is a hosted endpoint at https://mcp2.corpusiq.io/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 · mcp2.corpusiq.io
claude mcp add --transport http io-corpusiq-multi-source-mcp 'https://mcp2.corpusiq.io/mcp'
{
"mcpServers": {
"io-corpusiq-multi-source-mcp": {
"url": "https://mcp2.corpusiq.io/mcp"
}
}
} {
"servers": {
"io-corpusiq-multi-source-mcp": {
"type": "http",
"url": "https://mcp2.corpusiq.io/mcp"
}
}
} [mcp_servers.io-corpusiq-multi-source-mcp] url = "https://mcp2.corpusiq.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-corpusiq-multi-source-mcp": {
"type": "remote",
"url": "https://mcp2.corpusiq.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-corpusiq-multi-source-mcp --url 'https://mcp2.corpusiq.io/mcp' --transport streamable-http
mcp_servers:
io-corpusiq-multi-source-mcp:
url: "https://mcp2.corpusiq.io/mcp" {
"McpServers": {
"io-corpusiq-multi-source-mcp": {
"Transport": "http",
"Url": "https://mcp2.corpusiq.io/mcp"
}
}
} assistant mcp add io-corpusiq-multi-source-mcp -t streamable-http -u 'https://mcp2.corpusiq.io/mcp'
{
"mcpServers": {
"io-corpusiq-multi-source-mcp": {
"type": "http",
"url": "https://mcp2.corpusiq.io/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.
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- Schema quality: good → excellent functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 −1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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://mcp2.corpusiq.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp2.corpusiq.io | CN=YE1,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 632f683c9e9f983a7f6edc69ae4293e7e99 |
| SANs: mcp2.corpusiq.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp2.corpusiq.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| corpusiq.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp2.corpusiq.io/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp2.corpusiq.io/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=() |
Protected resource metadata
| Document | https://mcp2.corpusiq.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp2.corpusiq.io/mcp |
| Authorisation server | https://mcp2.corpusiq.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp2.corpusiq.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp2.corpusiq.io/mcp | HTTPS enforced | 301 | https://mcp2.corpusiq.io/mcp |
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 →
reset_connector_token ~180
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_id | string | yes | – |
No output schema declared.
No examples provided.
resolve_connector ~345
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_hint | string | – | – |
| intent | string | yes | – |
| multi | boolean | – | – |
No output schema declared.
No examples provided.
run_runbook ~313
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | – |
| content_hash | string | – | – |
| date_range | string | – | – |
| execution_mode | string | – | – |
| mode | string | – | – |
| runbook_id | string | yes | – |
| user_question | string | – | – |
| version | string | – | – |
No output schema declared.
No examples provided.
salesforce_connector ~708
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
search_console_connector ~362
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
search_gunbroker_items ~212
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | – |
| condition | integer | – | – |
| keywords | string | – | – |
| max_price | number | – | – |
| min_price | number | – | – |
| page_index | integer | – | – |
| page_size | integer | – | – |
No output schema declared.
No examples provided.
search_youtube ~130
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
select_runbook ~201
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| connected_sources | array | – | – |
| preferred_scope | string | – | – |
| user_question | string | yes | – |
No output schema declared.
No examples provided.
semrush_connector ~516
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
semrush_dashboard ~162
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | – |
| domain | string | yes | – |
| months | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
set_my_primary_youtube_channel ~184
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | – |
No output schema declared.
No examples provided.
shopify_dashboard ~185
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| start_date | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
shopline_connector ~1,002
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
slack_connector ~371
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
stripe_connector ~737
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
stripe_dashboard ~192
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | – |
| start_date | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
tiktok_connector ~365
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
truth_sources_list ~261
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
truth_sources_register ~591
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | yes | – |
| key | string | yes | – |
| label | string | yes | – |
| location | string | yes | – |
| notes | string | – | – |
| refresh_cadence | string | – | – |
| retrieval_tool | string | yes | – |
No output schema declared.
No examples provided.
truth_sources_remove ~180
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
web_fetch_connector ~336
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| params | object | – | – |
No output schema declared.
No examples provided.
What is the CorpusIQ MCP server?
CorpusIQ is an MCP server listed in the public MCP registry as io.corpusiq/multi-source-mcp. Authenticated, user-scoped MCP connectors for 30+ business systems. This page covers its hosted endpoint (https://mcp2.corpusiq.io/mcp).
Is the CorpusIQ MCP server safe to use?
CorpusIQ scores 90 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.
Does the CorpusIQ MCP server require authentication?
Yes. CorpusIQ asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the CorpusIQ MCP server still maintained?
CorpusIQ 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.