CorpusIQ
io.corpusiq/multi-source-mcp · 1.0.0
Authenticated, user-scoped MCP connectors for 30+ business systems.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 20 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp2.corpusiq.io/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 121 tools.
- Protocol
- 2025-03-26
- Calls itself
- multi-source-mcp 1.0.0
- Handshake time
- 213 ms
- HTTP status
- 200
The tools it lists (121, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_connector_statusReturn a pre-formatted Markdown dashboard showing every configured connector's status. IMPORTANT: The output is a complete, ready-to-display Markdown table — show it to the user exactly as returned, do NOT summarize or paraphrase. Each row includes connector name, provider, connection status (with emoji indicators), and a clickable link to authenticate if needed. After displaying the table, offer to help the user connect any unauthorized services and mention they can say 'refresh status' after authenticating.
resolve_connectorDiscover how to answer the user's data question. ALWAYS call this FIRST for any data-related request. For broad questions — business health, performance, growth, financial pulse, recap, 'how are we doing', 'what should I focus on', or any cross-source question — the response returns a CorpusIQ Skill in `skill.skill_body`: a pre-built runbook you should execute step-by-step, honoring any presentation rules it specifies. For narrow single-source questions, the response returns 2-4 ready-to-call tool schemas. The `supporting_actions` list is available as helpers when a skill is attached — do not
ask_corpusiqAnswer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins the best matching runbook before validating connectors and executing its fixed read-only tool allowlist. In required_runbook mode, the caller pins an explicit runbook id. Returns the answer, source evidence, warnings, and a verifiable execution receipt; unsupported runbooks and missing prerequisites fail closed. Use this for supported executive financial-health or financial snapshot workflows even when the user names QuickBooks or another single service. Use
select_runbookUse this FIRST for broad executive/business questions such as 'How healthy is my business?', 'How are we doing?', 'What should I focus on?', or 'Give me an executive summary'. Selects the best CorpusIQ runbook and returns the next step. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequ
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.corpusiq/multi-source-mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 138 days ago. The registry entry