MCP CPG Human in the Loop (HITL)
RemoteAbout MCP CPG Human in the Loop (HITL)
MCP CPG Human in the Loop is a human-review transaction service for consumer-goods agentic procurement. It handles requests for quotes, terms, and escalations, with every ticket answered by a person to pair machine discovery with human confirmation.
Key features
- 01Submit requests for quotation
- 02Check request status
- 03Request commercial terms
- 04Escalate cases for human handling
Use cases
- 01Request a quote for a purchase order
- 02Track an open request for quotation
- 03Send an unresolved case for human review
MCP support
Its Streamable HTTP MCP server exposes four tools to submit and check requests, request terms, and escalate cases; every ticket is routed to a human.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.cpghumanintheloop.ai/mcpclaude mcp add --transport http greencore-solutions-cpg-human-in-the-loop https://mcp.cpghumanintheloop.ai/mcp{"mcpServers":{"greencore-solutions-cpg-human-in-the-loop":{"type":"http","url":"https://mcp.cpghumanintheloop.ai/mcp"}}}Open in Cursor{"servers":{"greencore-solutions-cpg-human-in-the-loop":{"type":"http","url":"https://mcp.cpghumanintheloop.ai/mcp"}}}Open in VS Code{"mcpServers":{"greencore-solutions-cpg-human-in-the-loop":{"type":"http","url":"https://mcp.cpghumanintheloop.ai/mcp"}}}{"mcpServers":{"greencore-solutions-cpg-human-in-the-loop":{"serverUrl":"https://mcp.cpghumanintheloop.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEMCP CPG Human in the Loop (HITL)
Surface role: TRANSACTION — one of the four GSC surfaces (data · discovery · transaction · standards).
Lodge an RFQ, request terms, or escalate — a human answers every ticket. ACM-451 ESCALATE is served here.
| Canonical endpoint | https://mcp.cpghumanintheloop.ai/mcp (streamable-http) |
| Website | https://cpghumanintheloop.ai |
| Registry listing | io.github.greencore-solutions/cpg-human-in-the-loop v1.0.0 |
| Operator | GreenCore Solutions Corp. — Microsoft AI Cloud Partner |
| Protocol | ACM-68000 · sovereign manifest SM-ECO-10060 |
Registry tile text (verbatim)
Title: MCP CPG Human in the Loop (HITL) Description: Navigator for BPC Agentic Procurement
What it serves
Four MCP tools — submit_rfq, check_rfq_status, request_terms, escalate.
Every ticket routes to a human. Human-in-the-Loop on every purchase order:
machine discovery, human confirmation.
Releases
| tag | source | deployed image digest |
|---|---|---|
v1.0.0 | 6004ce5 | sha256:40893539be16 |
Data plane and secret hygiene
Additive hitl.* schema on the shared Postgres (hitl.tickets); kg.* and
gtins.* are untouched by this service.
The connection string lives ONLY as a Container App secret. It is never
committed, never written into deploy files, never echoed, and never logged.
Application code reads process.env.DATABASE_URL and nothing else — see
server.js and console.js. Deploy docs reference the DSN as a placeholder
only. Verified by a full-history credential scan: zero literal secret values.
The four surfaces
| surface | endpoint |
|---|---|
| data | https://mcp.cpgknowledgegraph.ai |
| discovery | https://mcp.gsc-fleet.ai |
| transaction | https://mcp.cpghumanintheloop.ai |
| standards | https://mcp.cpgagentprotocols.ai |
Licensing
No license file is committed. GSC MCP server code is under a hybrid MIT + Commercial Enterprise arrangement; the counsel-drafted terms are pending. Until they land, absence of a LICENSE file is deliberate — not an oversight.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.