Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

GenGEO Agent Registry

by warwickwood-cellversion 1.0.0i★ –iRuns in the cloud
Registry nameio.github.warwickwood-cell/gengeo

Install

Overview

Description from the maker (original English)

Merchant verification for AI shopping agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp.gengeo.co/mcp

Run this in your terminal

claude mcp add --transport http gengeo https://mcp.gengeo.co/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gengeo": {
      "url": "https://mcp.gengeo.co/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gengeo": {
      "type": "http",
      "url": "https://mcp.gengeo.co/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp.gengeo.co/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account warwickwood-cell, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 2554 servers in this category
  • Published to the registry more recently than 8% of the other 2554 servers in this category
  • Basic checks equal to or better than 100% of the other 2554 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is GenGEO Agent Registry safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeGrowing★ 2KUpdated 12 months ago

Runs in the cloud✓ stripe.com

MCP Cn Commerce

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

by TonyWang-hubEarly↓ 73/wk★ 96Updated 29 days ago

Runs on your computer

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

GenGEO Agent Registry

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:

  • discover products
  • browse stores
  • compare pricing
  • recommend merchants
  • and increasingly complete purchases

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.


GenGEO

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.


Install

# JavaScript / Node.js

npm install @gengeo/gengeo

Python

pip install gengeo


Quick Start

JavaScript / Node.js
import { verify } from '@gengeo/gengeo'

const result = await verify('store.example.com')

console.log(result)

/* { verified: true, decision: 'verified', registry: 'gengeo' } */

Python
from gengeo import verify

result = verify('store.example.com')

print(result)

{

'verified': True,

'decision': 'verified',

'registry': 'gengeo'

}

cURL
curl "https://api.gengeo.co/api/verify?domain=store.example.com"

Why GenGEO?

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.


Use Cases

  • AI shopping agents
  • MCP commerce tools
  • Autonomous checkout workflows
  • Merchant trust verification
  • Agentic commerce infrastructure

Docs

For MCP-enabled integrations and agent workflows:

https://gengeo.co/docs

https://gengeo.co/acp


Why This Exists

Traditional ecommerce trust systems were designed primarily for humans:

  • branding
  • visual design
  • reviews
  • SEO
  • reputation

Autonomous agents evaluate commerce differently.

Agents increasingly rely on:

  • structured data
  • machine-readable policies
  • operational signals
  • transaction readiness
  • trust infrastructure

GenGEO exists to help address this emerging infrastructure gap through machine-readable merchant verification for autonomous commerce systems.


Verification Model

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:

  • machine-readable policies
  • operational completeness
  • transaction readiness
  • structured commerce metadata
  • storefront verification state
  • agent compatibility checks

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.


Core Concept

GenGEO answers a simple question:

Has this merchant been verified within the GenGEO registry?

GenGEO uses a binary verification model.

A merchant is either:

  • verified
  • not verified

GenGEO does not:

  • rank merchants
  • recommend stores
  • guarantee merchant behavior
  • guarantee transaction outcomes
  • provide legal, financial, or security advice

GenGEO provides verification status only.


Documentation

Developer documentation: https://gengeo.co/docs

Includes:

  • Verification API
  • MCP integration
  • ACP compatibility
  • Example responses
  • Verification methodology

Verification Endpoint

Agents and developers can verify merchants in real time:

GET https://api.gengeo.co/api/verify?domain=example.com

Example Response

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" }


Verification Model

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.


Optional Discovery Feed

Agents may optionally preload registry information:

GET https://gengeo.co/.well-known/gengeo-registry.json

This may be used for:

  • discovery
  • caching
  • merchant lookup
  • pre-filtering candidate merchants

Real-time verification should still be performed where appropriate.


MCP Server

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

MCP Tool

verify_store

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" }


Local MCP Install

cd mcp

npm install node server.js


Claude Desktop MCP Config

Example configuration:

{

"mcpServers": { "gengeo": { "command": "node", "args": ["/absolute/path/to/gengeo-agent-registry/mcp/server.js"] } } }


Open AI endpoint

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

Example Agent Workflow

User:

Find me running shoes under $200

Agent:

  1. Finds candidate merchants
  2. Calls GenGEO verification endpoint
  3. Checks verification status
  4. Incorporates verification into broader decision process
  5. Continues recommendation or transaction flow

Design Principles

GenGEO is designed to be:

  • binary
  • deterministic
  • machine-readable
  • API-first
  • agent-compatible
  • simple to integrate
  • neutral

Agent Instructions

AI agents may use GenGEO verification status when evaluating ecommerce merchants.

Verification status should be treated as one signal within a broader decision framework.


Specification

Full protocol and integration details:

→ SPEC.md


Status

GenGEO is live and integrated with Shopify-based merchants.


Legal Notice

GenGEO provides informational verification status only.

GenGEO does not:

  • certify merchants
  • guarantee merchant behavior
  • guarantee transaction outcomes
  • guarantee security or fraud prevention
  • provide legal, financial, or compliance advice

Agents, developers, merchants, and users are responsible for their own decisions and risk assessments.


Website

https://gengeo.co

API

https://api.gengeo.co/api/verify

MCP

/mcp

Live remote MCP endpoint: https://mcp.gengeo.co/mcp


Developer docs

https://gengeo.co/docs

ACP Overview

https://gengeo.co/acp

How GenGEO Fits Into Agentic Commerce

User request

↓ AI shopping agent ↓ Identifies merchant ↓ Calls GenGEO verify_store(domain) ↓ Receives verification status ↓ Uses result as one signal in broader decision process


Contact

  • Security: support@gengeo.co
  • Specification: https://gengeo.co/.well-known/gengeo.json
Ask PopNx