CPG Agent Protocols bronze

cpgagentprotocols.ai

“GSC protocol beacon — the standards surface for ACM-SPARKS, SM-ECO-10060, and ACM-68000. Stateless, deterministic, compiled canon: 7 signals, 6 SPARKS dimensions, 49 sovereign members, the Ghost header canon. Data lives on mcp.cpgknowledgegraph.ai; this surface defines the vocabulary.

https://cpgagentprotocols.ai/.well-known/agent-card.json its card

🇫🇷 FR · Microsoft Corporation Checked 3d ago extensions, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by DigiCert Inc domain-validated
Valid until 19 Jan 2027.

Control of the hostname was checked; nothing about who operates it.
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 2 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “cpgagentprotocols.ai — CPG Agent Protocols” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, EdDSA) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 18 Sep 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: 🇫🇷 FR · Microsoft Corporation (AS8075)
Last checked: 3d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of cpgagentprotocols.ai controls every word below.

CPG Agent Protocols — MCP tools

Live MCP tools on cpgagentprotocols.ai: list_protocols, get_protocol, list_signals, resolve_signal, list_sparks_dimensions, resolve_sparks_dimension, list_members, resolve_member, get_header_canon.

mcpacm-68000

Canonical Network Stats

Serve the canonical GSC statband: 38,350 brands / 15,688 retail banners / 3.29M points of sale / 50 markets — monthly inbound agent transaction number published at https://gsc-radar.ai (source of record).

statscpgnetwork

Human-in-the-Loop Contact

Reach GreenCore Solutions Corp. via GSC Navigator (https://gsc-navigator.ai/); every transactional commit is human-signed.

contacthitl

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

CPG Agent Protocols — the GSC standards beacon (MCP)

mcp-server

The GSC protocol beacon, served live over MCP (streamable-http): ACM-68000 signals, SPARKS dimensions, SM-ECO-10060 members and the Ghost header canon, resolved as fact. Operated by GreenCore Solutions Corp.

https://mcp.cpgagentprotocols.ai/mcp

Protocol broadcast record

json

The beacon's static broadcast set: protocol.json, signals.json, sparks.json, nodes.json and headers.json — the same canon the MCP tools resolve, as plain JSON documents.

https://mcp.cpgagentprotocols.ai/protocol.json

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: GreenCore Solutions Corp. — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.1.3
Auth schemes: bearerJwt entraOAuth2
Extensions: https://gsc-em.com/a2a/ext/scope-of-authority/v1
GSC scope of authority: read, resolve and discovery calls are autonomous; every transactional commit (order, RFQ acceptance, terms) is human-signed at the GSC Navigator HITL boundary.
https://gsc-em.com/a2a/ext/enforcement-posture/v1
These endpoints are open by design. When the buy side's credential standard reaches GA — expected Q4 2026-Q1 2027 — transactional methods migrate to OAuth 2.1 challenge per the MCP 2025-11-25 specification. Read access stays open. That is not pending w

A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so.
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: extensions pushNotifications streaming
Agent card: https://cpgagentprotocols.ai/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.