Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / MCP CPG Knowledge Graph

BPC Agentic Commerce Infra

Answered:

4 of 4 checks

Status
responds
Typical response time
440 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 423 ms.
Address
https://mcp.cpgknowledgegraph.ai/mcp
Listed in:
official MCP registry mcp_registry
Registry name
io.github.greencore-solutions/cpg-knowledge-graph
Transport
streamable HTTP streamable-http
Host
mcp.cpgknowledgegraph.ai

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
cpgknowledgegraph-ai
Version:
3.4.7
MCP features it lists:
experimental, logging, prompts, resources, tools, extensions
Tool names:
resolve_gtincheck_eligibilityget_signal_chaincount_gtin_coverageresolve_scopelist_nodesresolve_nodefind_makersfind_retailersnode_marketlist_sku_typeslist_brands_by_node
and 2 moreget_kernelresolve_sparks
Instructions excerpt:
CPGKnowledgeGraph.ai — the skill layer for agentic CPG-to-retail-grocery procurement, operated by GreenCore Solutions Corp. (GSC). A 49-node sovereign graph (SM-ECO-10060): makers (supply) and retail banners (demand) attach to each node; every node carries a GS1-registered GTIN; eligibility resolves under ACM-68000. Retrieval-first: query the live graph in…

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for MCP CPG Knowledge Graph
CheckedStatusTookCheck
responds400 msMCP initialize · 8s limit · HTTP 200
responds676 msMCP initialize · 8s limit · HTTP 200
responds457 msMCP initialize · 8s limit · HTTP 200
responds423 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.