# MachineWitness (remote · machinewitness.eu)

EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `machinewitness.eu`: 83/100 (this document), [markdown](https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness.md), [page](https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness)

## Channel facts

- Endpoint: `https://machinewitness.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1496 tokens (~249/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 MachineWitness MCP server?

MachineWitness is a hosted endpoint at https://machinewitness.eu/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 eu-machinewitness-archive 'https://machinewitness.eu/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "eu-machinewitness-archive": {
      "url": "https://machinewitness.eu/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "eu-machinewitness-archive": {
      "type": "http",
      "url": "https://machinewitness.eu/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.eu-machinewitness-archive]
url = "https://machinewitness.eu/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-machinewitness-archive": {
      "type": "remote",
      "url": "https://machinewitness.eu/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-machinewitness-archive --url 'https://machinewitness.eu/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-machinewitness-archive:
    url: "https://machinewitness.eu/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "eu-machinewitness-archive": {
      "Transport": "http",
      "Url": "https://machinewitness.eu/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add eu-machinewitness-archive -t streamable-http -u 'https://machinewitness.eu/mcp'
```

### Other

```json
{
  "mcpServers": {
    "eu-machinewitness-archive": {
      "type": "http",
      "url": "https://machinewitness.eu/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-05 (score 83, 0)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 83, +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-01 (score 82, +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-10-30 (score 81, +1)

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

### 2026-10-28 (score 80, +1)

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

### 2026-10-26 (score 79, +1)

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

### 2026-10-24 (score 78, +1)

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

### 2026-10-22 (score 77, +1)

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

## MCP tools (6)

### `check_coverage` (~103 tokens)

Check whether a domain is observed

Answer whether this archive observes a given domain, from which sealed day onward, which machine-readable files it requests, and at what cadence. Returns metadata only — never the contents of any file, and never an assessment of the domain or its operator. 'Not observed' is a statement about this archive, not about the domain: most of the web is not observed.

Input parameters:

- `domain` (string, required): A domain name, for example example.eu. A pasted URL is accepted.

### `suggest_domain` (~152 tokens)

Suggest a domain for observation

Suggest that a domain be observed. This is a request, not an instruction: admission follows documented criteria (a connection to the European Union, publicly served machine-readable files) and is decided by the operator. The answer is always 'received' with 'guarantee: none' — it creates no obligation to observe the domain, no timeline, and no assurance that it will be added. A reason is required and is read by a person.

Input parameters:

- `domain` (string, required): The domain to suggest.
- `email` (string, required): Reply address. Used to answer the suggestion and nothing else.
- `reason` (string, required): Why this domain should be observed. Written for a human reader; a sentence or two is enough.

### `order_capture` (~261 tokens)

Order a point-in-time record of public addresses

Create a payment link for a point-in-time record: both witnesses fetch the named addresses, take a full-page picture of each, and give each capture its own qualified electronic time-stamp. Up to twenty public addresses, all on the same domain. Before the link is created, every address is checked at no charge: a public domain name, not on the stop list, robots.txt allows our crawler, and it answers without a login; refused addresses are named with the reason. This call charges nothing. The capture starts only after a person has paid on the returned page; the record is then delivered by e-mail, and a second e-mail follows after the night's seal. Only addresses are asked for, never a purpose. Fees: https://machinewitness.eu/services

Input parameters:

- `addresses` (array, required): Full addresses (https://…), one to twenty, all on one domain.
- `email` (string): Delivery address, prefilled on the payment page. Optional; the page asks for it otherwise.
- `language` (string): Language of the payment page and the e-mails. Default en.
- `timezone` (string): IANA time zone of the requester (e.g. Europe/Berlin) for the expected start time. Default Europe/Madrid.

### `order_extract` (~218 tokens)

Order an evidence extract for observed domains

Create a payment link for an evidence extract: everything this archive recorded on a domain, as one verifiable document (every observed day, every file type, both witnesses, with the seals and verification instructions). One to twenty domains. A domain this archive never observed is refused by name before the link is created, because there would be nothing to deliver; use check_coverage first. This call charges nothing. After a person has paid on the returned page, a confirmation with the reference follows at once and the extract is normally delivered by e-mail within five working days. Only domains are asked for, never a purpose or a matter. Terms: https://machinewitness.eu/extract · Fees: https://machinewitness.eu/services

Input parameters:

- `domains` (array, required): Domain names, one to twenty, e.g. example.eu.
- `email` (string): Delivery address, prefilled on the payment page. Optional; the page asks for it otherwise.
- `language` (string): Language of the payment page and the e-mails. Default en.

### `order_observation` (~232 tokens)

Subscribe domains to daily observation

Create a payment link for the daily observation of domains, as a yearly or monthly subscription: from admission, within five working days of payment, two independent witnesses record each domain every day in full (homepage and the machine-readable files), seal each day and anchor it externally; the admission is entered in the public record. The customer pays for the measurement, not for a document: the data in hand is an evidence extract (order_extract). A domain already observed daily in the core is refused by name, because it costs nothing. On cancellation the subscription ends with the paid period and everything witnessed until then stays sealed. This call charges nothing; the subscription starts only after a person has paid on the returned page. Fees and tiers: https://machinewitness.eu/services

Input parameters:

- `domains` (array, required): Domain names, one to 500, e.g. example.eu.
- `email` (string): Address for confirmations, prefilled on the payment page. Optional.
- `interval` (string): Billing interval. Default year.
- `language` (string): Language of the payment page and the e-mails. Default en.

### `capture_status` (~93 tokens)

Status of a point-in-time record

Where a point-in-time record stands, by its reference (MW-K-…): awaiting payment, queued, capturing, first delivery sent, complete. Per witness: waiting, capturing, captured, failed or refused. Never returns the e-mail address, the addresses ordered or anything else about the customer.

Input parameters:

- `reference` (string, required): The order reference, e.g. MW-K-3F9A2C1D.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80
- 2026-10-28: 80
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-07: 71
- 2026-10-06: 70

## Common questions

### What is the MachineWitness MCP server?

MachineWitness is an MCP server listed in the public MCP registry as eu.machinewitness/archive. EU archive of the machine-readable web: check a domain, order a time-stamped record or extract. This page covers its hosted endpoint (https://machinewitness.eu/mcp).

### Is the MachineWitness MCP server safe to use?

MachineWitness scores 83 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 MachineWitness MCP server expose?

MachineWitness exposes 6 tools: check_coverage, suggest_domain, order_capture, order_extract, order_observation, capture_status. Their descriptions and schemas cost roughly 1,059 tokens of context every time the server is loaded.

### Does the MachineWitness MCP server require authentication?

No. We connected to MachineWitness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MachineWitness MCP server still maintained?

MachineWitness is still listed as active in the MCP registry. We last reached this channel on 5 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 MachineWitness MCP server?

VerifyMCP ran 13 checks on MachineWitness, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://machinewitness.eu/mcp
- Repository: https://github.com/martinschenk/machinewitness-mcp
- Website: https://machinewitness.eu/api
- Changelog RSS feed: https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness.json
- HTML version of this page: https://verifymcp.io/servers/eu-machinewitness-archive/machinewitness