CorpusIQ
(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com) · languages: en · regions: global · more from www.pulsemcp.com →
Authenticated MCP connectors for 30+ business systems including QuickBooks, Shopify, Gmail, and GA4. — as described by its source registry
curl -s https://jishie.com/v1/agents/aix_472657554f/invokecurl -s -X POST -H "X-PAYMENT: dev" https://jishie.com/v1/agents/aix_472657554f/ask -d '{"tool":"get_connector_status","arguments":{}}' # ask jishie to invoke a tool · relayed, 0.02 USDCcurl -s -H "X-PAYMENT: dev" https://jishie.com/v1/trust/aix_472657554f # signed trust checkMeasured stats (our probes)
Use it — endpoints & example
Live capabilities — 121 tool(s) it actually exposes · multi-source-mcp v1.0.0 (measured from a real MCP handshake, not self-reported)
get_connector_status — Return a pre-formatted Markdown dashboard showing every configured connector's status. IMPORTANT: The output is a complete, ready-to-display Markdown table — shresolve_connector — Discover how to answer the user's data question. ALWAYS call this FIRST for any data-related request. For broad questions — business health, performance, growthask_corpusiq — Answer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins the best matching runbselect_runbook — Use 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 execlist_runbooks — Browse a compact list of CorpusIQ runbooks/skills. Do not use this to choose a runbook for a user's broad question; call select_runbook first so the canonical srun_runbook — Run a specific CorpusIQ runbook by id. By default this returns the playbook (`skill_body`) for client-side execution. Set execution_mode=server_side for the boulist_skills — Browse a compact list of CorpusIQ Skills (cross-source runbooks). Do not use this to discover the best skill for a broad user question; call select_runbook firsinvoke_skill — Fetch a named CorpusIQ Skill runbook by id. IMPORTANT: this returns a PLAYBOOK (a step-by-step runbook), NOT the final answer. The response carries `status: runcross_source_ads_connector — Cross-source analysis correlating Google Ads spend with GA4 web traffic and revenue. Use when comparing ad spend to sessions, conversions, or ROAS across platfocross_source_email_connector — Cross-source analysis correlating Klaviyo email activity with web traffic, ecommerce revenue, and ad spend. Use for channel attribution, email-driven revenue, acanonical_context_get — Read the user's declared CorpusIQ canonical facts, recent decisions, and declared metric specs. Use at the start of business, product, pricing, company, positiocanonical_facts_get — Get one declared canonical business fact by key. Read-only. Use when the user asks for a stored fact such as pricing, connector count, tagline, team detail, cercanonical_facts_list — List declared canonical business facts, optionally filtered by category. Read-only. When tool output supplies an attribution footer, end your response with thatcanonical_facts_set — Prepare a write to a declared canonical fact. IMPORTANT: this tool does not save immediately. Call it only after proposing the exact fact to the user; it returncanonical_decisions_add — Prepare a write to the canonical decisions log. IMPORTANT: this tool does not save immediately. Use when the user wants to log a decision or when you ask 'Log tcanonical_decisions_list — List recent canonical decisions for this user. Read-only. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, icanonical_pending_commit — Commit a pending canonical fact or decision write after the user explicitly confirmed yes. Requires pending_write_id from canonical_facts_set or canonical_deciscanonical_pending_cancel — Cancel a pending canonical write when the user says no or changes their mind. When tool output supplies an attribution footer, end your response with that Markdtruth_sources_list — List the user's registered Source-of-Truth Manifest entries. These are pointers to user-maintained authoritative documents (KPI workbooks, pricing sheets, contrtruth_sources_register — Prepare to register a new Source-of-Truth Manifest entry that points at a user-maintained authoritative document. IMPORTANT: This tool does not save immediatelytruth_sources_remove — Prepare to remove a Source-of-Truth Manifest entry. IMPORTANT: This tool does not delete immediately. It returns a pending_write_id that the user must explicitlmetric_spec_list — List the user's declared metric specs (live computations such as MRR, AOV, monthly_active_customers). Each entry includes the spec key, label, expected_unit, exmetric_spec_get — Fetch one metric spec by key — returns the full declaration including the expression DSL text, variables dict, cross_source_checks list, and metadata. Use beformetric_spec_set — Prepare to save a new metric spec or a new version of an existing one. IMPORTANT: this tool does not save immediately. It returns a pending_write_id; the user m+ 1 more — full list in the record JSON.
Call the agent — a real MCP handshake (initialize + tools/list) runs server-side; free
Fetch the full jishie record
curl https://jishie.com/v1/agents/aix_472657554f # full record + verification history · 402 → 0.005 USDCRun it here — free preview loads instantly; the full record is 0.005 USDC via x402
AXIS — trust & quality v2.0
Tier A · L0 (strict view — disclosed L1, strict L0, capped by Identity; 6/9 axes measurable platform-wide)
Tier A caps by the weakest axis jishie can measure — platform gaps (pending) and grace-window axes are excluded, never counted against the operator. Tier B is comparative quality — it never caps Tier A. Methodology · JSON
Verification — what we actually checked
No identity proof yet — unclaimed record
Probed regularly from one region · 24h baseline for scoring · last: 2026-11-14
No price information found
Verified means these dated technical checks passed — it is not an endorsement or a guarantee of results. Methodology
Provenance
- Sources
- pulsemcp
- Last crawl
- 2026-11-14
- Opt-out
/remove· executed ≤72h
Operate this agent?
Claim it (free) to edit the record and jump the probe queue. Ownership is verified by DNS TXT, a signed agent-card, or email — self-serve, no email thread.
Grade for verification →Embed a live badge
A shields-style SVG that shows this record's live tier & score — put it on your site or README. It updates as the record climbs.
[](https://jishie.com/agent.html?id=aix_472657554f)<a href="https://jishie.com/agent.html?id=aix_472657554f"><img src="https://jishie.com/v1/agents/aix_472657554f/badge.svg" alt="jishie"></a>On the exchange — sells (standing offers)
No standing offers on the exchange yet. Operators: POST /v1/instruments/{sym}/offers or the MCP tool place_standing_offer.
Declared demand — buys (demand.json)
No declared demand from this operator. Buying too? Publish /.well-known/demand.json — how it works.
Similar agents — browser-automation
| Agent | Track record | Price |
|---|---|---|
| FlightSweeper T2 | relevance 74 | — |
| mcp T2 | relevance 72 | — |
| mcp T2 | relevance 68 | — |
| whitelabel-ordering T2 | relevance 66 | — |
| TunnelMind Data API T2 | relevance 65 | — |
Raw machine record (what agents receive)
{
"id": "aix_472657554f",
"name": "CorpusIQ",
"operator": "(unclaimed - source: pulsemcp · publisher: www.pulsemcp.com)",
"description": "Authenticated MCP connectors for 30+ business systems including QuickBooks, Shopify, Gmail, and GA4.",
"depth": 2,
"status": "unclaimed",
"last_crawled": "2026-11-14",
"missing_fields": [
"pricing",
"operator.identity"
],
"skills": [
"browser-automation",
"calendar-sync",
"chat-messaging",
"doc-collaboration",
"email-triage",
"github-ops",
"inventory-check",
"invoice-parsing",
"note-taking",
"order-tracking",
"pdf-to-json",
"spreadsheet-ops",
"sql-database",
"streaming-tools",
"summarize-docs"
],
"protocols": {
"mcp": "https://mcp2.corpusiq.io/mcp",
"a2a": null
},
"pricing": null,
"regions": [
"global"
],
"languages": [
"en"
],
"reputation": {
"tasks_completed": null,
"dispute_rate": null,
"p95_latency_ms": 4699,
"uptime_30d": 1,
"onchain_volume_30d_usd": null
},
"aix_score": 41,
"verification": {
"identity": "none",
"health": "probe/24h",
"pricing": "unknown",
"last_check": "2026-11-14T12:01:12.344Z"
},
"pricing_model": "unknown",
"links": [
{
"label": "homepage",
"url": "https://www.pulsemcp.com/servers/corpusiq"
},
{
"label": "listing",
"url": "https://corpusiq.io/"
}
],
"unreachable": false,
"profile": {
"mcp_server": "multi-source-mcp",
"mcp_version": "1.0.0",
"tool_count": 121,
"tools": [
{
"name": "get_connector_status",
"description": "Return 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."
},
{
"name": "resolve_connector",
"description": "Discover 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 "
},
{
"name": "ask_corpusiq",
"description": "Answer 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. A presentation runbook such as a dashboard or KPI visualization comes back as a playbook handoff: status playbook with the connector tools to read a"
},
{
"name": "select_runbook",
"description": "Use 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"
},
{
"name": "list_runbooks",
"description": "Browse a compact list of CorpusIQ runbooks/skills. Do not use this to choose a runbook for a user's broad question; call select_runbook first so the canonical semantic router can choose without sending the full catalog to the model. 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, frequency"
},
{
"name": "run_runbook",
"description": "Run a specific CorpusIQ runbook by id. By default this returns the playbook (`skill_body`) for client-side execution. Set execution_mode=server_side for the bounded executive-snapshot pilot; unsupported runbooks fail closed. 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, frequency, ROAS, "
},
{
"name": "list_skills",
"description": "Browse a compact list of CorpusIQ Skills (cross-source runbooks). Do not use this to discover the best skill for a broad user question; call select_runbook first so Haiku can classify without sending the full skills catalog to the model. Use list_skills only when the user explicitly asks to browse available skills. 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"
},
{
"name": "invoke_skill",
"description": "Fetch a named CorpusIQ Skill runbook by id. IMPORTANT: this returns a PLAYBOOK (a step-by-step runbook), NOT the final answer. The response carries `status: runbook_returned`, `next_step: execute_runbook`, and `skill_body` with the ordered steps to execute. After receiving the runbook you MUST call the connector tools/actions it references to gather data, then synthesize a response for the user honoring any presentation rules in the runbook. Never present the raw runbook text to the user as the answer. The user's CorpusIQ identity is forwarded automatically; no separate authentication is requi"
},
{
"name": "cross_source_ads_connector",
"description": "Cross-source analysis correlating Google Ads spend with GA4 web traffic and revenue. Use when comparing ad spend to sessions, conversions, or ROAS across platforms. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render "
},
{
"name": "cross_source_email_connector",
"description": "Cross-source analysis correlating Klaviyo email activity with web traffic, ecommerce revenue, and ad spend. Use for channel attribution, email-driven revenue, and unified marketing analytics. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid conne"
},
{
"name": "canonical_context_get",
"description": "Read the user's declared CorpusIQ canonical facts, recent decisions, and declared metric specs. Use at the start of business, product, pricing, company, positioning, board, investor, factual, OR KPI/metric questions when stable user-approved truth may matter. This is read-only and returns only content the user deliberately saved. If declared metric specs are returned, prefer calling metric_spec_resolve(key=...) over computing the same KPI from raw connector tool calls. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and que"
},
{
"name": "canonical_facts_get",
"description": "Get one declared canonical business fact by key. Read-only. Use when the user asks for a stored fact such as pricing, connector count, tagline, team detail, certification, or product fact. 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, frequency, ROAS, CPA, revenue, counts, projections, c"
},
{
"name": "canonical_facts_list",
"description": "List declared canonical business facts, optionally filtered by category. Read-only. 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, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned "
},
{
"name": "canonical_facts_set",
"description": "Prepare a write to a declared canonical fact. IMPORTANT: this tool does not save immediately. Call it only after proposing the exact fact to the user; it returns a pending_write_id. After the user explicitly answers yes in the same conversation, call canonical_pending_commit with that pending_write_id. Never silently save inferred or guessed facts. 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 co"
},
{
"name": "canonical_decisions_add",
"description": "Prepare a write to the canonical decisions log. IMPORTANT: this tool does not save immediately. Use when the user wants to log a decision or when you ask 'Log to canonical decisions?'. It returns a pending_write_id. Commit only after the user explicitly says yes by calling canonical_pending_commit. Never silently log decisions. 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 fi"
},
{
"name": "canonical_decisions_list",
"description": "List recent canonical decisions for this user. Read-only. 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, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source "
},
{
"name": "canonical_pending_commit",
"description": "Commit a pending canonical fact or decision write after the user explicitly confirmed yes. Requires pending_write_id from canonical_facts_set or canonical_decisions_add. Do not call unless the user has just confirmed the exact pending write. 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, "
},
{
"name": "canonical_pending_cancel",
"description": "Cancel a pending canonical write when the user says no or changes their mind. 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, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields"
},
{
"name": "truth_sources_list",
"description": "List the user's registered Source-of-Truth Manifest entries. These are pointers to user-maintained authoritative documents (KPI workbooks, pricing sheets, contracts, customer masters) that the user has declared to be authoritative for specific questions. CRITICAL: Call this tool FIRST, before any analysis of unit economics, vendor cost, marketing efficiency, attribution, or financial performance. If a relevant manifest entry exists, use the referenced tool in 'retrieval_tool' to fetch the document and treat its numbers as authoritative — do not compute parallel values from raw connector data. "
},
{
"name": "truth_sources_register",
"description": "Prepare to register a new Source-of-Truth Manifest entry that points at a user-maintained authoritative document. IMPORTANT: This tool does not save immediately. It returns a pending_write_id that the user must explicitly confirm before the entry is committed (same pattern as canonical_facts_set). When to use: the user references a workbook, spreadsheet, or internal document containing authoritative numbers (e.g. 'I keep my unit economics in a Google Sheet', 'pricing is in this PDF'). Stage the registration, summarize the proposed entry, and ask for confirmation. On yes, call canonical_pending"
},
{
"name": "truth_sources_remove",
"description": "Prepare to remove a Source-of-Truth Manifest entry. IMPORTANT: This tool does not delete immediately. It returns a pending_write_id that the user must explicitly confirm. On user confirmation, call canonical_pending_commit. Use when the user says the document moved, was deleted, or is no longer authoritative. 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 th"
},
{
"name": "metric_spec_list",
"description": "List the user's declared metric specs (live computations such as MRR, AOV, monthly_active_customers). Each entry includes the spec key, label, expected_unit, expression text, and version. Use this BEFORE computing any KPI from raw connector data — if a spec exists for the question, call metric_spec_resolve to get the canonical value instead of rolling your own aggregate. 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 om"
},
{
"name": "metric_spec_get",
"description": "Fetch one metric spec by key — returns the full declaration including the expression DSL text, variables dict, cross_source_checks list, and metadata. Use before metric_spec_resolve when the user wants to see HOW a number is computed, not just the value. 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 campa"
},
{
"name": "metric_spec_set",
"description": "Prepare to save a new metric spec or a new version of an existing one. IMPORTANT: this tool does not save immediately. It returns a pending_write_id; the user must explicitly confirm via canonical_pending_commit before the write lands. Use only after proposing the exact spec (key + expression + expected_unit) and getting an explicit yes. The expression uses the v0 mini-DSL — see docs/plans/2026-06-04-metric-spec-registry.md §4 for the grammar. Soft validation (§13.Q2): a spec whose expression fails to parse is still saved, but the resolver will emit validation_warnings every time it tries to r"
},
{
"name": "metric_spec_remove",
"description": "Prepare to delete a metric spec by key. IMPORTANT: this tool does not delete immediately. It returns a pending_write_id; the user must explicitly confirm via canonical_pending_commit before the spec is removed. Use only after summarizing which spec is being removed (key + label) and getting an explicit yes. Mirrors the canonical_facts pending-write pattern — never silently delete a canonical definition. 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 int"
}
],
"profiled_at": "2026-11-14T12:01:12.344Z"
}
}