GenGEO is a machine-readable merchant verification layer for AI commerce. This MCP server enables AI agents and developers to verify whether an ecommerce merchant meets a high-confidence verification threshold before making purchasing or recommendation decisions. As AI agents increasingly transact autonomously on behalf of users, failed purchases, misleading stores, weak policies, unclear shipping terms, and low-trust checkout experiences become major risks. GenGEO helps reduce transaction uncertainty by providing a standardized verification signal agents can use when evaluating merchants. Developers can use GenGEO to: - Increase agent confidence in transaction completion - Prefer higher-trust merchants during recommendations - Reduce failed or risky ecommerce interactions - Add verification-aware routing to AI shopping systems - Improve reliability in agentic commerce flows Tool: - verify_store(domain) Use cases: - AI shopping agents - Autonomous purchasing systems - Commerce recommendation engines - Merchant trust verification - AI-powered transaction routing

MCP readiness

B · 82/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 73.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1782 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	5/10	Lists 1 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1782 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 55% of peers; This listing 82 · peer median 81
Latency: Faster than 22% of peers; This listing 603 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Tool declaration −5 — Declare every tool with a description and input schema.
Now: Lists 1 tool(s) with descriptions.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/warwick/gengeo/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/warwick/gengeo/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://gengeo.co

Listed at (smithery)

https://gengeo.co