Koskamo

GenGEO MCP

A Model Context Protocol server that enables AI agents to perform deterministic binary verification of ecommerce merchants. It checks if a merchant exists in the GenGEO registry and returns status signals to help agents make informed purchasing decisions.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

GenGEO MCP logo, by GenGEOCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by GenGEO
MCP endpoint (Streamable HTTP)
https://mcp.gengeo.co/mcp
Vendor documentation

What its tools do

1 tool, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (1)

1 of 1 have a description · 0 of 1 declare behavior hints · 0 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Verify if a merchant exists in the GenGEO registry
  • Check merchant verification status for AI shopping agents
  • Pre-filter candidate merchants before transaction

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.warwickwood-cell/gengeo@1.0.0Source repository
Maintenance checked

Protocol and capabilities

Server
gengeo-remote-mcp 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
1 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

1 advertised

verify_store — Verify Store
Advertised by the server during the last successful anonymous check.

Verify whether a merchant has an active GenGEO verification record. Results should be treated as one signal within a broader agent decision framework.

verify_store input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 3
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-07: 1 of 1 checks answered
  2. 2026-11-09: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
640 ms
95th percentile latency
640 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 640 ms · metadata changed · 1 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http gengeo-mcp https://mcp.gengeo.co/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add gengeo-mcp --url https://mcp.gengeo.co/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable gengeo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "gengeo-mcp": {
      "url": "https://mcp.gengeo.co/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "gengeo-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.gengeo.co/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start gengeo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "gengeo-mcp": {
      "type": "http",
      "url": "https://mcp.gengeo.co/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http gengeo-mcp https://mcp.gengeo.co/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.gengeo.co/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "gengeo-mcp": {
      "serverUrl": "https://mcp.gengeo.co/mcp"
    }
  }
}

Let your agent find its tools

Find servers like GenGEO MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,688