AI Orderability (AIO) Agents CPG with x402: Retail & Marketplace Sourcing
REMOTE · MCP.GSC-MARKETPLACE.AI
CPG sourcing for AI Agents with x402: BPC brands, agent IM, Trading Desk. GreenCore Solutions Corp.
Available components
Last scanned (15 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 6 Nov 2026.
Category E-commerce
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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 check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. 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.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 29 Oct 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: 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
- 21 Oct 26 0
- Tool “get_cpg_knowledge_graph” rewrote its description, which is the text the model reads security
- Tool “search_brands” rewrote its description, which is the text the model reads security
- 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
- 25 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
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 0
- Server version: 1.4.0 → 1.4.1 functional
- 1 Sept 26 0
- Server version: 1.3.0 → 1.4.0 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 6 Nov 2026 · Probed https://mcp.gsc-marketplace.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gsc-marketplace.ai | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 947f54b2b62cd4a90ecfbe066269b2f3 |
| SANs: gsc-marketplace.ai, *.gsc-marketplace.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.gsc-marketplace.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| gsc-marketplace.ai. | DS published | 2371 | 13 | Verified |
| mcp.gsc-marketplace.ai. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 301 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.gsc-marketplace.ai/mcp | Redirected | 301 | https://gtinfetch.ai/ |
| http (plaintext) | http://mcp.gsc-marketplace.ai/mcp | HTTPS enforced | 301 | https://gtinfetch.ai/ |
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 →
contact_trading_desk GSC Trading Desk — the humans' door ~54
The human channel. The GSC Trading Desk is informed by Navigator across all GSC agentic assets — a human reads, a human answers. Use it for anything a person should decide; agents use Instant Messaging.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_acm_68000 ACM-68000 — the seven procurement signals ~69
The deterministic signal protocol every GSC surface speaks: seven signals, GS1-anchored, append-only, non-substitutable. Canon resolves on acm-68000.ai / .org and the standards beacon; the gen-2 door is cpg-68000.ai.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_aio_agent_fleet AI Orderability (AIO) Agents — the gen-2 fleet ~64
The AIO Agent class and its regional hosts: signed, resident, addressable resolvers with market × category remits — the NextGen identity register is the signed Card, verifiable against each host's jwks. Status is only what the wire says.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_brand Verify one brand in a market — found, verified, answerable ~131
Step 2 — VERIFIED: is the brand on the CPG Knowledge Graph for this market, and at what SPARKS completeness tier (100 = resolvable pack/size record held · 8 = registered, pending · floor = STANDARD default). Returns the market's supply/demand context and both doors to act. No prices, no stock, no terms — those go through the doors.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name as spelled on the graph |
| market | string | yes | SM-ECO-10060 member code or namespace, e.g. BR or BR-ECO-10060 |
No output schema declared.
No examples provided.
get_brand_identifiers Brand identifier policy — what the marketplace publishes and how to resolve what you hold ~139
Step 3 — ANSWERABLE: GSC publishes ONLY its own GS1-registered identifiers (the 990832300xxx block) on any surface; third-party GTINs are never stored on the graph's entity universe and never appear here. A GTIN the caller already holds resolves live on the CPG Knowledge Graph (resolve_gtin, resolve_sparks, check_eligibility). The demo brand carries GSC's rail GTIN.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name |
| market | string | – | SM-ECO-10060 member code or namespace, e.g. BR or BR-ECO-10060 |
No output schema declared.
No examples provided.
get_cpg_knowledge_graph The CPG Knowledge Graph — data surface ~81
353,532 makers · 8,619 retail banners · 25 markets (statement of record, read live: https://gsc-radar.ai/statement.json). The Beauty & Personal Care source of truth for AI agents, classified on SPARKS; 14 read tools over MCP; the data surface every marketplace answer resolves against.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_marketplace_operators Neutral marketplace operator map, sorted by agentic posture ~101
The demand side per market as the CPG Knowledge Graph publishes it (retail banners — public registry data), each carrying an agentic-posture field from a fixed taxonomy and sorted by it. Neutral by design: no tiers, no pursuit language, no relationship claims, no named individuals. Posture is wire evidence only; 'unassessed' means none collected yet.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | – | Omit for the 50-market summary |
No output schema declared.
No examples provided.
get_radar GSC Radar — the network numbers bulletin ~27
The public network figures as GSC Radar publishes them (live JSON), macro numbers only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_x402_rail x402 capability declaration ~80
What GSC-Marketplace declares about x402: header, network, asset, status — and where the single paid endpoint lives (https://gsc-marketplace.ai/api; its terms are stated in its 402 payload only, never here). Door: https://gsc-marketplace.ai/x402 · skill: x402-settlement.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
instant_message_agents Instant Messaging for agents — the agents' door ~71
How an agent lodges an RFQ, a terms request, or an escalation with GreenCore Solutions Corp. — typed, identified, ticketed, human-signed (IA-MESSAGE). Points at the existing door: the x-gsc-inbound address and the transaction MCP. No new write path here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_brands Search Beauty & Personal Care brands in a market ~214
When a marketplace or retail sourcing agent calls, it leaves with a brand it can act on — found, verified, and answerable — with Instant Messaging for agents or the human-in-the-loop GSC Trading Desk as next steps. Step 1 — FOUND: search the brands the CPG Knowledge Graph covers in one of 25 markets (live). Returns brand names from the graph's SPARKS depth surface; then call get_brand to verify, get_brand_identifiers for the identifier policy. Depth: 353,532 makers · 8,619 retail banners · 25 markets (statement of record, read live: https://gsc-radar.ai/statement.json). Brands, makers and banners are separate registries — never summed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 50 |
| market | string | yes | SM-ECO-10060 member code or namespace, e.g. BR or BR-ECO-10060 |
| query | string | – | Optional name fragment (accent-insensitive) |
No output schema declared.
No examples provided.
How do I install the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server?
AI Orderability (AIO) Agents CPG with x402: Retail… is a hosted endpoint at https://mcp.gsc-marketplace.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.gsc-marketplace.ai
claude mcp add --transport http greencore-solutions-gsc-marketplace 'https://mcp.gsc-marketplace.ai/mcp'
What is the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server?
AI Orderability (AIO) Agents CPG with x402: Retail… is an MCP server listed in the public MCP registry as io.github.greencore-solutions/gsc-marketplace. CPG sourcing for AI Agents with x402: BPC brands, agent IM, Trading Desk. GreenCore Solutions Corp. This page covers its hosted endpoint (https://mcp.gsc-marketplace.ai/mcp).
Is the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server safe to use?
AI Orderability (AIO) Agents CPG with x402: Retail… scores 24 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 AI Orderability (AIO) Agents CPG with x402: Retail… MCP server expose?
AI Orderability (AIO) Agents CPG with x402: Retail… exposes 11 tools: search_brands, get_brand, get_brand_identifiers, get_marketplace_operators, instant_message_agents, and 6 more. Their descriptions and schemas cost roughly 1,031 tokens of context every time the server is loaded.
Does the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server require authentication?
Its publisher declares no required credentials for AI Orderability (AIO) Agents CPG with x402: Retail…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server still maintained?
AI Orderability (AIO) Agents CPG with x402: Retail… is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AI Orderability (AIO) Agents CPG with x402: Retail… MCP server?
VerifyMCP ran 5 checks on AI Orderability (AIO) Agents CPG with x402: Retail…, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about AI Orderability (AIO) Agents CPG with x402: Retail…: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.