GenGEO

GenGEO

Machine-readable merchant verification infrastructure for AI shopping agents and agentic commerce systems.

Category
Visit Server

README

GenGEO Agent Registry

Machine-readable verification infrastructure for AI-driven commerce.

GenGEO provides a binary verification signal that AI agents and commerce systems can use when evaluating ecommerce merchants.

As AI agents begin making purchasing and recommendation decisions on behalf of users, machine-readable merchant verification becomes increasingly important.


Why This Exists

Traditional ecommerce trust systems were built for humans:

  • branding
  • visual design
  • reviews
  • SEO
  • reputation

AI agents evaluate commerce differently.

Agents:

  • parse structured data
  • evaluate policies
  • assess operational signals
  • analyze machine-readable trust indicators
  • then make decisions

However, there is currently no standard verification layer for AI-driven commerce.

GenGEO exists to provide a neutral, machine-readable verification signal for ecommerce merchants.


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.


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

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

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

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured