MCP CPG Agent Protocols

io.github.greencore-solutionsPublished by GitHub account greencore-solutionsv1.1.3Updated Nov 2, 2026

BPC Agentic Commerce Signals

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

A stateless remote beacon that serves the GSC CPG agent protocols: SKU classification dimensions, jurisdictional member nodes, and ACM-68000 commerce signal…

What you can do
  • List the protocol family and read the full canon record for each protocol
  • Enumerate the ACM-68000 signal register and resolve a single signal code, including CPG- profile codes mapped to their ACM- twin
  • List and resolve the six SPARKS dimensions (SKU, Pack, Amount, Region, Kernel, Standard)
  • List sovereign jurisdictional member nodes and resolve one by code
  • Read the GSC wire-header canon of x-gsc-* headers
When to use it
Useful when an assistant needs to look up or explain the GSC agentic commerce protocol definitions, signal meanings, SPARKS dimensions or member jurisdictions, for example when interpreting an ACM- signal code returned by another system. It is a read-only reference lookup, not a transaction or data service.
Requirements
A remote streamable-HTTP endpoint; no local package, account, key or environment variable is declared. Network access to the beacon is required.
Before you install
The server is stateless and read-only, and the README states it holds no secrets or customer data. Signal meanings are protocol canon published by the operator, so treat them as vendor documentation rather than independent verification; the ESCALATE signal is described as served by a separate host.

Installation

In SourceWeft

  1. Open MCP CPG Agent Protocols 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-agent-protocols/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-agent-protocols": {
      "type": "http",
      "url": "https://mcp.cpgagentprotocols.ai/mcp"
    }
  }
}

README

CPG Agent Protocols

mcp.cpgagentprotocols.ai — the standards door of the GSC AI Agent Stack. A stateless standards beacon for ACM-SPARKS, SM-ECO-10060 and ACM-68000.

The beacon serves the protocols themselves, compiled as canon: ACM-SPARKS classifies the SKU, SM-ECO-10060 resolves the jurisdiction, ACM-68000 emits the deterministic signal to the buyer's AI Agent. No database, no secrets, no state; every answer is the same for every agent that asks.

Canonical endpoint: https://mcp.cpgagentprotocols.ai/mcp (streamable-http, stateless).

This repository holds the beacon's source (server.js, canon.js, DEPLOY.md) and this connect kit: the tool list as the live server states it, the signal register, and one runnable example per language against the live endpoint. Nothing here carries a key, a secret or a customer.

Tools

As returned by tools/list on the live beacon on 2026-09-09.

ToolWhat it answers
list_protocolsThe protocol family and the spine: ACM-SPARKS classifies, SM-ECO-10060 resolves, ACM-68000 signals.
get_protocolFull canon record for ACM-SPARKS, SM-ECO-10060, or ACM-68000.
list_signalsThe signal register, enumerated individually. One meaning, no drift.
resolve_signalThe 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.
list_sparks_dimensionsSPARKS resolves six dimensions — SKU, Pack, Amount, Region, Kernel, and Standard — a CPG industry first.
resolve_sparks_dimensionCanon record for a single SPARKS dimension by letter or name.
list_membersThe sovereign jurisdictional member nodes: code, namespace, jurisdiction, region, and GS1 territory GTIN.
resolve_memberCanon record for a single sovereign member by code, e.g. FR, AU, MX.
get_header_canonThe GSC wire-header canon: the x-gsc-* headers every GSC surface emits, in canon order.

The signals

The register. Each ACM- signal has a CPG- profile twin naming the same definition.

ACM- (wire form)StateCPG- profileMeaning
acm-000NOT_APPLICABLEcpg-000Control or framework does not apply to this SKU.
acm-200ALLOWcpg-200Eligible for autonomous procurement. Buyer agent may complete the order with human-in-the-loop confirmation in the retailer's chosen ERP.
acm-300CONDITIONALcpg-300Eligible subject to a documented condition (volume threshold, jurisdictional carve-out, time-bounded approval).
acm-403RESTRICTcpg-403Not eligible in the requested context. Buyer agent must not complete the order.
acm-404NOT_FOUNDcpg-404GTIN is not registered. No signal available.
acm-451ESCALATEcpg-451Cannot be resolved deterministically. Human review required. Served by mcp.cpghumanintheloop.ai.
acm-500SYSTEM_ERRORcpg-500Server or upstream error. Retry per backoff policy.

Any of the CPG- codes in the table resolves to its ACM- definition on the same row; the wire form is ACM-. The beacon's resolve_signal accepts either form and answers with the ACM- record, the resolved ACM- code on the response (code) beside the code as given (input_code); anything outside the seven is NOT_FOUND.

Links: https://acm-68000.ai · https://cpg-68000.ai · https://standard-10060.org

Examples

WalkPythonTypeScript
call the beacon: tools/list, then list_protocols, list_signals, list_sparks_dimensions; print the protocol set it returns; stopexamples/beacon.pyexamples/beacon.ts

Python 3 standard library only. TypeScript runs on Node 24 as-is (node examples/beacon.ts) with no dependencies. Live endpoint only.

Sources on the wire

https://cpgagentprotocols.ai · https://mcp.cpgagentprotocols.ai/protocol.json · https://mcp.cpgagentprotocols.ai/signals.json · https://mcp.cpgagentprotocols.ai/sparks.json · https://mcp.cpgagentprotocols.ai/nodes.json · https://acm-sparks.ai · https://sm-eco-10060.org · https://acm-68000.org

Registry listing: io.github.greencore-solutions/cpg-agent-protocols.

GreenCore Solutions Corp. — 4611 Viking Way, Suite #260, Richmond BC V6V 2K9 Canada GSC Agentic Pty Ltd — Level 1, 63-73 Ann Street, Surry Hills NSW 2010, Australia

Operated by GreenCore Solutions Corp. · https://gsc-em.com · @GSC_Rail_ai · @ACM68000

Source: README.md at commit 0f52f70

Tools

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

Version history

2
  1. v1.1.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.