MCP CPG Human in the Loop (HITL)

io.github.greencore-solutionsPublished by GitHub account greencore-solutionsv1.0.3Updated Oct 24, 2026

Navigator for BPC Agentic Procurement

The publisher's own server: TAP

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint for agentic procurement that lets an assistant submit RFQs, check their status, request terms, and escalate tickets to a human.

What you can do
Submit a request for quotation (RFQ) as a ticket for procurement follow-up. Check the status of an existing RFQ ticket. Request commercial terms. Escalate an issue, with every ticket routed to a human for confirmation.
When to use it
Use when an assistant is working through a procurement or purchasing workflow and needs to lodge an RFQ, ask for terms, or hand an issue to a person rather than resolve it automatically.
Requirements
A remote streamable-HTTP endpoint; no local runtime, account, API key, or header is declared. The assistant connects to the hosted service over the network.
Before you install
Submitting RFQs, requesting terms, and escalating create tickets that are routed to a human and stored in the operator's database, so treat them as real procurement actions rather than drafts. No authentication is declared, so check how the endpoint is protected before sending commercial details. The README states no license file is committed and terms are pending.

Installation

In SourceWeft

  1. Open MCP CPG Human in the Loop (HITL) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.greencore-solutions%2Fcpg-human-in-the-loop/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cpg-human-in-the-loop-hitl": {
      "type": "http",
      "url": "https://mcp.cpghumanintheloop.ai/mcp"
    }
  }
}

README

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.

Source: README.md at commit ac5a79a

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.3LatestSep 17, 2026
  2. v1.0.0Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Human integrations