MachineWitness
REMOTE · MACHINEWITNESS.EU
EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.
Available components
Last scanned (11 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://machinewitness.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=machinewitness.eu | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 33c8b1fd492a12be0e6019f0570ab1ee |
| SANs: machinewitness.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of machinewitness.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| machinewitness.eu. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machinewitness.eu/mcp | Verified | 200 | |
| http (plaintext) | http://machinewitness.eu/mcp | HTTPS enforced | 301 | https://machinewitness.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capture_status Status of a point-in-time record ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | The order reference, e.g. MW-K-3F9A2C1D. |
No output schema declared.
No examples provided.
check_coverage Check whether a domain is observed ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name, for example example.eu. A pasted URL is accepted. |
No output schema declared.
No examples provided.
order_capture Order a point-in-time record of public addresses ~261
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
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | Full addresses (https://…), one to twenty, all on one domain. |
| 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. |
No output schema declared.
No examples provided.
order_extract Order an evidence extract for observed domains ~218
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
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names, one to twenty, e.g. example.eu. |
| 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. |
No output schema declared.
No examples provided.
order_observation Subscribe domains to daily observation ~232
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
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names, one to 500, e.g. example.eu. |
| 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. |
No output schema declared.
No examples provided.
suggest_domain Suggest a domain for observation ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to suggest. |
| string | yes | Reply address. Used to answer the suggestion and nothing else. | |
| reason | string | yes | Why this domain should be observed. Written for a human reader; a sentence or two is enough. |
No output schema declared.
No examples provided.
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.
remote · machinewitness.eu
claude mcp add --transport http eu-machinewitness-archive 'https://machinewitness.eu/mcp'
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.