holdmark · facts about online stores

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

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
73%
Calidad de los nombres
93%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~515Tokens (definiciones de herramientas)
~1007 BTamaño de respuesta típico
Impacto mínimo en la atención (0.40% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

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

Puntos de conexión remotos

https://holdmark.org/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (3)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

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

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada3 herramientas