English Français العربية

MCP CPG Human in the Loop (HITL)

Official registry AI and agents

Navigator for BPC Agentic Procurement

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http mcp-cpg-human-in-the-loop-hitl 'https://mcp.cpghumanintheloop.ai/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "mcp-cpg-human-in-the-loop-hitl": {
            "type": "http",
            "url": "https://mcp.cpghumanintheloop.ai/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. MCP CPG Human in the Loop (HITL)
  2. Registry tile text (verbatim)
  3. What it serves
  4. Releases
  5. Data plane and secret hygiene
  6. The four surfaces
  7. Licensing

MCP 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 endpointhttps://mcp.cpghumanintheloop.ai/mcp (streamable-http)
Websitehttps://cpghumanintheloop.ai
Registry listingio.github.greencore-solutions/cpg-human-in-the-loop v1.0.0
OperatorGreenCore Solutions Corp. — Microsoft AI Cloud Partner
ProtocolACM-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

tagsourcedeployed image digest
v1.0.06004ce5sha256: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

surfaceendpoint
datahttps://mcp.cpgknowledgegraph.ai
discoveryhttps://mcp.gsc-fleet.ai
transactionhttps://mcp.cpghumanintheloop.ai
standardshttps://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.

Frequently asked questions

What is MCP CPG Human in the Loop (HITL)?

Navigator for BPC Agentic Procurement

How do I install MCP CPG Human in the Loop (HITL)?

It runs as a remote server. In Claude Code: claude mcp add --transport http mcp-cpg-human-in-the-loop-hitl 'https://mcp.cpghumanintheloop.ai/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does MCP CPG Human in the Loop (HITL) need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is MCP CPG Human in the Loop (HITL) open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains MCP CPG Human in the Loop (HITL)?

It is published by greencore-solutions. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.