Add CorpusIQ MCP server

[pengshenghai]

Summary

• add CorpusIQ to the Agent-to-Agent Protocols section as an MCP server for business data APIs
• keep the entry concise and factual, linking to the public CorpusIQ documentation repository

Validation

• git diff --check -- README.md passed
• python %TEMP%\\verify_corpusiq_readme.py passed (CorpusIQ README entry ok)

AI assistance

Implemented with AI assistance from Codex. I inspected the README and contribution guidelines first, kept this to a single awesome-list entry, and did not configure or access any business APIs or credentials.

[daviediao-code]

LGTM! Clean contribution. ✅

[daviediao-code]

LGTM! Clean contribution. ✅

[FakerHideInBush]

Two concerns before merging:

1. CorpusIQ is an MCP server (data integration tool), not an agent communication protocol — the 'Agent Communication Protocols' section is the wrong placement

The 'Agent Communication Protocols' section contains standards for agent-to-agent communication and discovery: Google A2A, MCP (the protocol itself), OpenClaw Beacon, Grazer, Agent Protocol, Agora Protocol, LMOS, ANP. These are protocol specs and SDKs for how agents communicate.

CorpusIQ is described as:

Open-source MCP server that connects AI agents to business data APIs such as Stripe, GA4, Shopify, QuickBooks, and HubSpot.

This is an MCP server (a tool that exposes data through MCP), not a communication protocol. It belongs in an 'MCP Servers', 'Data Connectors', or 'Tools & Integrations' section. Placing it under 'Agent Communication Protocols' alongside protocol definitions and SDKs misrepresents its purpose.

2. The whitespace-only changes (BCOS badge blank line + LMOS trailing space) conflict with open PRs #24 and #26 — all three touch the same 2 lines

PRs #24 (Add Skales) and #26 (Add NotFair) make the identical cosmetic whitespace fix on the same lines. Please coordinate so only one PR carries these whitespace changes — the others should drop them to avoid merge conflicts.

[Scottcjn]

This adds a whole new MCP Servers section for a single docs-repo link. Fold the entry into an existing category instead of opening a new section for one item, and rebase onto main (stale base), then it's mergeable.

[Scottcjn]

Maintainer review: the linked repository is active and documents a real MCP service, but the proposed wording calls CorpusIQ an open-source MCP server. The repository describes itself as the open documentation repository for a hosted commercial MCP platform; the server implementation is not present under an open-source license here. Please revise the entry to say MCP platform or hosted MCP service and avoid the open-source server claim. The new category and link otherwise fit the list.