MCP CPG Agent Protocols
REMOTE · MCP.CPGAGENTPROTOCOLS.AI
BPC Agentic Commerce Signals
Available components
Last scanned (14 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 15 Oct 2026.
Category E-commerce
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Oct 26 −3
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 12 Oct 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 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 22 Oct 2026 · Probed https://mcp.cpgagentprotocols.ai/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.cpgagentprotocols.ai. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.cpgagentprotocols.ai. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://mcp.cpgagentprotocols.ai/mcp | HTTPS enforced |
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.
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'
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 0 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?
Its publisher declares no required credentials for MCP CPG Agent Protocols. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MCP CPG Agent Protocols server still maintained?
MCP CPG Agent Protocols has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.