
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
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.
Installation
In SourceWeft
- Open MCP CPG Human in the Loop (HITL) in the dashboard and add it to a workspace.
- 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.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.
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
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
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
0Version history
2- v1.0.3LatestSep 17, 2026
- 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

TAP
tech.humanOfficial publisher
TAP is a hosted remote MCP endpoint that isolates AI agents' credentials using placeholder secrets, policy checks and optional human approval.
UGC, the Human Ad Network
africa.ugcOfficial publisher
Remote MCP endpoint for UGC, a "Human Ad Network", letting an assistant work with ad campaigns, clipping and Clip Studio from chat.

PromptHuman
Published by GitHub account prompthumanhq
Lets an assistant request paid, asynchronous judgment from a real person — gut checks, how text reads, plausibility, local context — and track the reply.

HITL (Human in the Loop)
Published by GitHub account hitl-sh
Lets an AI assistant run HITL workflows that ask a real person for a decision on their phone and wait for the answer.
Human Use
dev.humanuse
Turns a person into MCP tools: an agent calls tools like photo or errand, a card appears on their phone, and the answer returns as JSON.