Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
作者提供的说明(英文原文)
Merchant verification for AI shopping agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.gengeo.co/mcp在终端中运行这条命令
claude mcp add --transport http gengeo https://mcp.gengeo.co/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"gengeo": {
"url": "https://mcp.gengeo.co/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"gengeo": {
"type": "http",
"url": "https://mcp.gengeo.co/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.gengeo.co/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 warwickwood-cell 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Machine-readable trust infrastructure for autonomous commerce systems.
GenGEO is building the world's largest merchant trust registry for AI agents and the foundation of a global reputation network for agentic commerce.
GenGEO enables AI agents and developers to verify whether an ecommerce merchant meets a high operational verification threshold before autonomous purchasing or recommendation decisions are made.
As AI agents increasingly transact on behalf of users, a major infrastructure problem is emerging:
There is currently no standardized machine-readable trust layer for determining whether a merchant is operationally ready and appropriate for autonomous transactions.
At the same time, legitimate AI-driven commerce activity is increasingly colliding with fraud and bot-detection systems that cannot distinguish autonomous AI agents from malicious automation.
AI agents can already:
But there is still no common verification layer for evaluating merchant transaction readiness before autonomous commerce actions proceed.
GenGEO helps reduce transaction uncertainty by providing a deterministic machine-readable verification signal that agents can incorporate into broader commerce decision frameworks.
Trust verification SDK for AI agents.
Verify whether an ecommerce merchant meets GenGEO trust standards before recommending, purchasing, or transacting.
GenGEO provides lightweight SDKs and APIs for merchant verification within autonomous commerce and AI-agent workflows.
# JavaScript / Node.js
npm install @gengeo/gengeo
pip install gengeo
import { verify } from '@gengeo/gengeo'
const result = await verify('store.example.com')
console.log(result)
/* { verified: true, decision: 'verified', registry: 'gengeo' } */
from gengeo import verify
result = verify('store.example.com')
print(result)
curl "https://api.gengeo.co/api/verify?domain=store.example.com"
AI agents increasingly transact autonomously on behalf of users.
GenGEO provides a standardized trust verification layer that helps agents evaluate whether a merchant is safe and transaction-ready before executing commerce actions.
For MCP-enabled integrations and agent workflows:
Traditional ecommerce trust systems were designed primarily for humans:
Autonomous agents evaluate commerce differently.
Agents increasingly rely on:
GenGEO exists to help address this emerging infrastructure gap through machine-readable merchant verification for autonomous commerce systems.
GenGEO uses a deterministic verification model designed to evaluate whether merchants meet a high operational verification threshold before autonomous agents proceed with commerce actions.
Verification may include signals such as:
The goal is not to guarantee outcomes, but to provide autonomous systems with a stronger machine-readable trust signal that may improve transaction confidence within broader agent decision frameworks.
GenGEO answers a simple question:
Has this merchant been verified within the GenGEO registry?
GenGEO uses a binary verification model.
A merchant is either:
GenGEO does not:
GenGEO provides verification status only.
Developer documentation: https://gengeo.co/docs
Includes:
Agents and developers can verify merchants in real time:
GET https://api.gengeo.co/api/verify?domain=example.com
Verified merchant:
{
"domain": "example.com", "verified": true, "status": "active", "eligible_for_ai_agent_purchase": "yes", "decision": "verified", "registry": "GenGEO" }
Non-verified merchant:
{
"domain": "example.com", "verified": false, "status": "not_found", "eligible_for_ai_agent_purchase": "unknown", "decision": "verification_required", "registry": "GenGEO" }
GenGEO uses deterministic binary verification logic.
Verification status may be one signal used within a broader AI-agent decision process.
Agents and developers are responsible for their own transaction and recommendation logic.
Agents may optionally preload registry information:
GET https://gengeo.co/.well-known/gengeo-registry.json
This may be used for:
Real-time verification should still be performed where appropriate.
This repository includes a Model Context Protocol (MCP) server for AI agents.
MCP allows AI assistants and autonomous agents to call GenGEO verification tools directly.
Location:
/mcp
Checks whether a merchant exists in the GenGEO verification registry.
Input:
{
"domain": "example.com" }
Example output:
{
"verified": true, "status": "active", "eligible_for_ai_agent_purchase": "yes", "decision": "verified" }
cd mcp
npm install node server.js
Example configuration:
{
"mcpServers": { "gengeo": { "command": "node", "args": ["/absolute/path/to/gengeo-agent-registry/mcp/server.js"] } } }
Remote MCP endpoint for ChatGPT Apps / OpenAI-compatible MCP clients:
https://chatgpt-mcp.gengeo.co/mcp
This endpoint exposes GenGEO merchant verification through a remote MCP server.
Legacy/general MCP references may use:
https://mcp.gengeo.co/mcp
For ChatGPT Apps submission and OpenAI Developer Mode testing, use:
https://chatgpt-mcp.gengeo.co/mcp
User:
Find me running shoes under $200
Agent:
GenGEO is designed to be:
AI agents may use GenGEO verification status when evaluating ecommerce merchants.
Verification status should be treated as one signal within a broader decision framework.
Full protocol and integration details:
→ SPEC.md
GenGEO is live and integrated with Shopify-based merchants.
GenGEO provides informational verification status only.
GenGEO does not:
Agents, developers, merchants, and users are responsible for their own decisions and risk assessments.
https://gengeo.co
https://api.gengeo.co/api/verify
/mcp
Live remote MCP endpoint: https://mcp.gengeo.co/mcp
https://gengeo.co/docs
https://gengeo.co/acp
User request
↓ AI shopping agent ↓ Identifies merchant ↓ Calls GenGEO verify_store(domain) ↓ Receives verification status ↓ Uses result as one signal in broader decision process