holdmark · facts about online stores

Does this store deliver and refund? Measured with carriers and payment processors.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
73%
Naming quality
93%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~515Tokens (tool definitions)
~1007 BTypical response size
Minimal attention impact (0.40% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "registry": {
      "url": "https://holdmark.org/mcp"
    }
  }
}

Remote endpoints

https://holdmark.org/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢find_stores(category, meets_limits, sort, order, limit, ...)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "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."
    },
    "sort": {
      "type": "string",
      "description": "Field to order by. Default: domain (alphabetical)."
    },
    "order": {
      "type": "string",
      "enum": [
        "asc",
        "desc"
      ],
      "description": "Ascending or descending. Default: asc."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100,
      "description": "How many to return. Default 50, maximum 100."
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip this many, to page through the list."
    }
  },
  "additionalProperties": false
}
🟢get_store(domain)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "The store's domain, for example tienda.com. Without https:// and without www."
    }
  },
  "required": [
    "domain"
  ],
  "additionalProperties": false
}
🟢how_holdmark_works

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.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools