MCP CPG Agent Protocols
BPC Agentic Commerce Signals
Should I use this
Quality & Safety
Findings (4)
- LOWTool 'list_protocols' description lacks action verbin list_protocols
- LOWTool 'list_signals' description lacks action verbin list_signals
- LOWTool 'resolve_signal' description lacks action verbin resolve_signal
- LOWTool 'list_members' description lacks action verbin list_members
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"cpg-agent-protocols": {
"url": "https://mcp.cpgagentprotocols.ai/mcp"
}
}
}Remote endpoints
https://mcp.cpgagentprotocols.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (9)
🟢list_protocols
The protocol family and the resolve-once spine: ACM-SPARKS classifies, SM-ECO-10060 resolves, ACM-68000 signals.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_protocol(name)
Full canon record for ACM-SPARKS, SM-ECO-10060, or ACM-68000.
Input Schema
{
"type": "object",
"properties": {
"name": {
"type": "string",
"enum": [
"ACM-SPARKS",
"SM-ECO-10060",
"ACM-68000"
],
"description": "Protocol name"
}
},
"required": [
"name"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_signals
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
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪resolve_signal(code)
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.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "Signal code, e.g. ACM-451 or CPG-451"
}
},
"required": [
"code"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_sparks_dimensions
SPARKS resolves six dimensions — SKU, Pack, Amount, Region, Kernel, and Standard — a CPG industry first.
Input Schema
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪resolve_sparks_dimension(dimension)
Canon record for a single SPARKS dimension by letter (S, P, A, R, K, S2) or name.
Input Schema
{
"type": "object",
"properties": {
"dimension": {
"type": "string",
"description": "Letter (S, P, A, R, K, S2) or name (e.g. Pack-format)"
}
},
"required": [
"dimension"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢list_members
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
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}⚪resolve_member(code)
Canon record for a single sovereign member by ISO-style code, e.g. FR, AU, MX.
Input Schema
{
"type": "object",
"properties": {
"code": {
"type": "string",
"maxLength": 4,
"description": "Member code, e.g. FR"
}
},
"required": [
"code"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_header_canon
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
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence