Koskamo

Holdmark MCP

An MCP server providing access to holdmark.org's public registry of facts about online stores. It allows agents to find stores, retrieve specific store records regarding delivery and refund metrics, and understand the methodology behind the data, all without requiring an API key.

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.

Holdmark MCP logo, by holdmark.orgVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by holdmark.org
MCP endpoint (Streamable HTTP)
https://holdmark.org/mcp
Vendor documentation

What you can do with it

  • Find stores in the registry
  • Get specific store delivery and refund facts
  • Understand how holdmark calculates figures

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: org.holdmark/registry@1.0.0Project website

Protocol and capabilities

Server
holdmark 1.0.0
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

holdmark is a public registry of measured facts about online stores: whether a store delivers its orders, checked with the carrier, and whether it refunds money, checked with the payment processor. These are not reviews. Nobody writes them and no store can pay to look better. Absence from this registry is not a signal against a store: it only means the store has not connected its data. holdmark does not score or rank stores by quality, and does not measure customer service or product quality. Free to read and cite, quoting holdmark.org as the source.

Tools

3 advertised

find_stores — Find stores in the holdmark registry
Advertised by the server during the last successful anonymous check.

List the online stores in the holdmark registry, with a summary of their published facts. Each store publishes the same facts under the same rules: whether it delivers its orders (checked with the carrier) and whether it refunds money (checked with the payment processor). holdmark does not rank stores and has no score, so compare them yourself by whatever the person actually cares about. The registry only contains stores that connected their data. A store missing from it has not been judged.

find_stores input schema
{
  "type": "object",
  "properties": {
    "sort": {
      "type": "string",
      "description": "Field to order by. Default: domain (alphabetical)."
    },
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "How many to return. Default 50, maximum 100."
    },
    "order": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "description": "Ascending or descending. Default: asc."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip this many, to page through the list."
    },
    "category": {
      "type": "string",
      "description": "Filter by the category the merchant declared. Declared, not checked: it says what a store sells, not how it behaves."
    },
    "meets_limits": {
      "type": "boolean",
      "description": "Only stores that meet (or do not meet) the published limits."
    }
  },
  "additionalProperties": false
}
get_store — Read one store's record
Advertised by the server during the last successful anonymous check.

Read the full holdmark record for one store, by its domain. Figures are rounded against the merchant, order volume is published in bands rather than exact numbers, and every figure carries the period it covers and the source it came from. A fact with no data answers "not_measured" with its reason, never "no". If the domain is not in the registry you get a plain answer saying so, which is not a verdict about that store.

get_store input schema
{
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "The store's domain, for example tienda.com. Without https:// and without www."
    }
  },
  "additionalProperties": false
}
how_holdmark_works — How holdmark measures and what it does not
Advertised by the server during the last successful anonymous check.

How every figure in the registry is calculated, what the words mean, and above all what holdmark does NOT measure. Read this before drawing a conclusion from any record: it is what stops a figure being read as something it is not.

how_holdmark_works input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

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
590 ms
95th percentile latency
590 ms

Maintenance history

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

  • · probe · passed · 590 ms · metadata changed · 3 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 holdmark-mcp https://holdmark.org/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 holdmark-mcp --url https://holdmark.org/mcp

Cursor

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

Cline

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start holdmark-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "holdmark-mcp": {
      "type": "http",
      "url": "https://holdmark.org/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 holdmark-mcp https://holdmark.org/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "holdmark-mcp": {
      "url": "https://holdmark.org/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": {
    "holdmark-mcp": {
      "serverUrl": "https://holdmark.org/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Holdmark 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 4,384

Do you run Holdmark MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing