# holdmark · facts about online stores (remote · holdmark.org)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `holdmark.org`: 79/100 (this document), [markdown](https://verifymcp.io/servers/org-holdmark-registry/holdmark.md), [page](https://verifymcp.io/servers/org-holdmark-registry/holdmark)

## Channel facts

- Endpoint: `https://holdmark.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 522 tokens (~174/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the holdmark · facts about online stores MCP server?

holdmark · facts about online stores is a hosted endpoint at https://holdmark.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-holdmark-registry 'https://holdmark.org/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "org-holdmark-registry": {
      "type": "http",
      "url": "https://holdmark.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-holdmark-registry]
url = "https://holdmark.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-holdmark-registry": {
      "type": "remote",
      "url": "https://holdmark.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-holdmark-registry --url 'https://holdmark.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-holdmark-registry:
    url: "https://holdmark.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-holdmark-registry": {
      "Transport": "http",
      "Url": "https://holdmark.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-holdmark-registry -t streamable-http -u 'https://holdmark.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-holdmark-registry": {
      "type": "http",
      "url": "https://holdmark.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-11-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `find_stores` (~225 tokens)

Find stores in the holdmark registry

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 parameters:

- `category` (string): Filter by the category the merchant declared. Declared, not checked: it says what a store sells, not how it behaves.
- `limit` (integer): How many to return. Default 50, maximum 100.
- `meets_limits` (boolean): Only stores that meet (or do not meet) the published limits.
- `offset` (integer): Skip this many, to page through the list.
- `order` (string): Ascending or descending. Default: asc.
- `sort` (string): Field to order by. Default: domain (alphabetical).

### `get_store` (~122 tokens)

Read one store's record

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 parameters:

- `domain` (string, required): The store's domain, for example tienda.com. Without https:// and without www.

### `how_holdmark_works` (~59 tokens)

How holdmark measures and what it does not

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-holdmark-registry/holdmark#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65

## Common questions

### What is the holdmark · facts about online stores MCP server?

holdmark · facts about online stores is an MCP server listed in the public MCP registry as org.holdmark/registry. Does this store deliver and refund? Measured with carriers and payment processors. This page covers its hosted endpoint (https://holdmark.org/mcp).

### Is the holdmark · facts about online stores MCP server safe to use?

holdmark · facts about online stores scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the holdmark · facts about online stores MCP server expose?

holdmark · facts about online stores exposes 3 tools: find_stores, get_store, how_holdmark_works. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Does the holdmark · facts about online stores MCP server require authentication?

No. We connected to holdmark · facts about online stores without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the holdmark · facts about online stores MCP server still maintained?

holdmark · facts about online stores is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the holdmark · facts about online stores MCP server?

VerifyMCP ran 12 checks on holdmark · facts about online stores, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about holdmark · facts about online stores: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://holdmark.org/mcp
- Website: https://holdmark.org/api
- Changelog RSS feed: https://verifymcp.io/servers/org-holdmark-registry/holdmark.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-holdmark-registry/holdmark/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-holdmark-registry/holdmark.json
- HTML version of this page: https://verifymcp.io/servers/org-holdmark-registry/holdmark
