MCP CPG Agent Protocols
REMOTE · MCP.CPGAGENTPROTOCOLS.AI · SCANNED SEP 20
BPC Agentic Commerce Signals
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 455 tokens (~50/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MCP CPG Agent Protocols server?
MCP CPG Agent Protocols is a hosted endpoint at https://mcp.cpgagentprotocols.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.cpgagentprotocols.ai
claude mcp add --transport http greencore-solutions-cpg-agent-protocols 'https://mcp.cpgagentprotocols.ai/mcp'
{
"mcpServers": {
"greencore-solutions-cpg-agent-protocols": {
"url": "https://mcp.cpgagentprotocols.ai/mcp"
}
}
} {
"servers": {
"greencore-solutions-cpg-agent-protocols": {
"type": "http",
"url": "https://mcp.cpgagentprotocols.ai/mcp"
}
}
} [mcp_servers.greencore-solutions-cpg-agent-protocols] url = "https://mcp.cpgagentprotocols.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"greencore-solutions-cpg-agent-protocols": {
"type": "remote",
"url": "https://mcp.cpgagentprotocols.ai/mcp",
"enabled": true
}
}
} openclaw mcp add greencore-solutions-cpg-agent-protocols --url 'https://mcp.cpgagentprotocols.ai/mcp' --transport streamable-http
mcp_servers:
greencore-solutions-cpg-agent-protocols:
url: "https://mcp.cpgagentprotocols.ai/mcp" {
"McpServers": {
"greencore-solutions-cpg-agent-protocols": {
"Transport": "http",
"Url": "https://mcp.cpgagentprotocols.ai/mcp"
}
}
} assistant mcp add greencore-solutions-cpg-agent-protocols -t streamable-http -u 'https://mcp.cpgagentprotocols.ai/mcp'
{
"mcpServers": {
"greencore-solutions-cpg-agent-protocols": {
"type": "http",
"url": "https://mcp.cpgagentprotocols.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 0
- Server version: 1.1.2 → 1.1.3 functional
- 10 Sept 26 0
- Tool “resolve_signal” rewrote its description, which is the text the model reads security
- Server version: 1.1.1 → 1.1.2 functional
- “resolve_signal” reworded the description of “code” cosmetic
- 31 Aug 26 0
- Stability: 0.97 → pass security
- 30 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- Server version: 1.0.0 → 1.1.1 functional
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.cpgagentprotocols.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cpgagentprotocols.ai | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3b510bd9970e39480e92907898252ab9 |
| SANs: cpgagentprotocols.ai, *.cpgagentprotocols.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cpgagentprotocols.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| cpgagentprotocols.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cpgagentprotocols.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cpgagentprotocols.ai/mcp | HTTPS enforced | 301 | https://mcp.cpgagentprotocols.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_header_canon Get the Ghost Headers canon ~65
The GSC wire-header canon (v3.2 — The Ghost Eighteen (locked July 18 2026)) — the eighteen x-gsc-* headers every GSC surface emits, in canon order. Curl-auditable against any live GSC surface.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_protocol Get one protocol ~39
Full canon record for ACM-SPARKS, SM-ECO-10060, or ACM-68000.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Protocol name |
No output schema declared.
No examples provided.
list_members List SM-ECO-10060 members ~48
The 49 sovereign jurisdictional member nodes — code, namespace, jurisdiction, region, and GS1 territory GTIN. Live supply/demand data per member is the CPG Knowledge Graph's job.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_protocols List the three GSC protocols ~40
The protocol family and the resolve-once spine: ACM-SPARKS classifies, SM-ECO-10060 resolves, ACM-68000 signals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_signals List the 7 ACM-68000 signals ~51
All seven signals, enumerated individually: ACM-000, ACM-200, ACM-300, ACM-403, ACM-404, ACM-451, ACM-500. One meaning, no drift.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sparks_dimensions List the six SPARKS dimensions ~36
SPARKS resolves six dimensions — SKU, Pack, Amount, Region, Kernel, and Standard — a CPG industry first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_member Resolve one SM-ECO-10060 member ~43
Canon record for a single sovereign member by ISO-style code, e.g. FR, AU, MX.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Member code, e.g. FR |
No output schema declared.
No examples provided.
resolve_signal Resolve one signal code ~65
The state and meaning of a single ACM-68000 signal code. A CPG- profile code resolves to its ACM- twin; the response carries the resolved ACM- code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Signal code, e.g. ACM-451 or CPG-451 |
No output schema declared.
No examples provided.
resolve_sparks_dimension Resolve one SPARKS dimension ~68
Canon record for a single SPARKS dimension by letter (S, P, A, R, K, S2) or name.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | Letter (S, P, A, R, K, S2) or name (e.g. Pack-format) |
No output schema declared.
No examples provided.
What is the MCP CPG Agent Protocols server?
MCP CPG Agent Protocols is listed in the public MCP registry as io.github.greencore-solutions/cpg-agent-protocols. BPC Agentic Commerce Signals. This page covers its hosted endpoint (https://mcp.cpgagentprotocols.ai/mcp).
Is the MCP CPG Agent Protocols server safe to use?
MCP CPG Agent Protocols scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP CPG Agent Protocols server expose?
MCP CPG Agent Protocols exposes 9 tools: list_protocols, get_protocol, list_signals, resolve_signal, list_sparks_dimensions, and 4 more. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.
Does the MCP CPG Agent Protocols server require authentication?
No. We connected to MCP CPG Agent Protocols without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP CPG Agent Protocols server still maintained?
MCP CPG Agent Protocols is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.