MachineWitness MCP server
eu.machinewitness/archivemachinewitness.eustreamable-httpv1.3.0Scanned
EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.
6 tools: 1 do something that can't be undone, 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MachineWitness MCP server can do
The MachineWitness MCP server is published by machinewitness.eu, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (order_capture) and create or change data (4 tools: check_coverage, suggest_domain, order_extract and order_observation), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (order_capture).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
order_captureCreate 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 tim…Reads text others writeNo findings
Why it is in this group
- The name "order_capture" says "capture": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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
Annotations the server declares
- title: Order a point-in-time record of public addresses
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 4Claude Code: ask
check_coverageAnswer whether this archive observes a given domain, from which sealed day onward, which machine-readable files it requests, and at what cadence.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check whether a domain is observed
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
order_extractCreate 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 t…No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it 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
Annotations the server declares
- title: Order an evidence extract for observed domains
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
order_observationCreate 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 reco…No findings
Why it is in this group
- The description's first verb is "create": a word for a change.
Description, as the server wrote it 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
Annotations the server declares
- title: Subscribe domains to daily observation
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
suggest_domainSuggest that a domain be observed.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Suggest a domain for observation
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
capture_statusWhere a point-in-time record stands, by its reference (MW-K-…): awaiting payment, queued, capturing, first delivery sent, complete.No findings
Why it is in this group
- The name "capture_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Status of a point-in-time record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://machinewitness.eu/mcp: tools/list returned 6 tools to an anonymous client, including order_capture (irreversible), check_coverage (write), suggest_domain (write), order_extract (write), order_observation (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http archive https://machinewitness.eu/mcpclaude mcp add --transport http archive https://machinewitness.eu/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__archive__capture_status"
],
"ask": [
"mcp__archive__check_coverage",
"mcp__archive__suggest_domain",
"mcp__archive__order_capture",
"mcp__archive__order_extract",
"mcp__archive__order_observation"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as archive. Review it before you use it.
Capability tags behind 1 rule
- mcp__archive__order_capture untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/eu.machinewitness/archive/verify?hash=c7bda33139ab650a1e673b09c95a8a3628a788f58df21e17a34b77938e359dbe" | jq -e '.changed == false'Pinned hash c7bda33139ab, from Nov 11, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/eu.machinewitness/archive/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/eu.machinewitness/archive)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
MachineWitness MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MachineWitness MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MachineWitness MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MachineWitness MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: order_capture.
What tools does the MachineWitness MCP server have?
- 6 tools: 1 irreversible, 4 write, 1 read. order_capture, check_coverage, suggest_domain, order_extract, order_observation and capture_status.
Does the MachineWitness MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MachineWitness MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MachineWitness MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.