Skip to content

Web Resource Ledger MCP server

io.github.benpeter/web-resource-ledgerbenpeterstreamable-httpv1.6.0Scanned

Capture web pages as cryptographically signed, tamper-evident evidence with WACZ archives.

13 tools: 1 can delete or cancel things, 3 do something that can't be undone, 2 change things and 7 only read.

Tools: 1 delete, 3 irreversible, 2 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 6
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 3 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Web Resource Ledger MCP server can do

The Web Resource Ledger MCP server is published by the GitHub account benpeter. It has 13 tools. It can delete or cancel things (1 tool: delete_schedule), do things that cannot be undone, such as sending, paying or publishing (capture_url, verify_capture and batch_capture) and create or change data (2 tools: create_schedule and update_schedule). 7 tools only read.

4 tools bring in text other people can write (list_captures, diff_captures, read_sitemap and 1 more); 6 tools can send data out of your system (capture_url, list_captures, batch_capture and 3 more).

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.6.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.

13 tools

Deletes or cancels 1Claude Code: deny
  • delete_scheduleDelete a scheduled capture by ID.No findings

    Why it is in this group

    • The name "delete_schedule" says "delete": a word for removing or ending something.
    • The description says "irreversible".
    Description, as the server wrote it
    Delete a scheduled capture by ID. Requires capture scope. Answers "Schedule not found." both for an ID that doesn't exist and for another account's schedule, without telling them apart. Deletion is immediate and irreversible. Use list_schedules to find schedule IDs.
Can't be undone 3Claude Code: ask
  • batch_captureSubmit up to 20 URLs for capture in a single call.Can send data outNo findings

    Why it is in this group

    • The name "batch_capture" says "capture": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Submit up to 20 URLs for capture in a single call. Returns a per-item status report showing accepted captures and any rejected URLs with reasons. Typically enqueues in under 2 seconds; each capture then typically completes in 20-60 seconds. Use get_capture with each returned ID to track progress.
  • capture_urlCapture a web page as tamper-evident evidence.Can send data outNo findings

    Why it is in this group

    • The name "capture_url" says "capture": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Capture a web page as tamper-evident evidence. Takes a screenshot, saves rendered HTML and HTTP headers, and creates a cryptographically signed WACZ bundle with Ed25519 signature and RFC 3161 timestamp. Returns a capture ID — use get_capture to check progress. Typically completes in 20-60 seconds. Failed attempts are retried, so a capture can stay pending for a few minutes; one still pending after 24 hours is marked failed.
  • verify_captureVerify the cryptographic integrity of a captured web page.No findings

    Why it is in this group

    • The name "verify_capture" says "capture": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Verify the cryptographic integrity of a captured web page. Checks artifact hashes, WACZ bundle hash, Ed25519 signature, and RFC 3161 timestamp, plus the eIDAS-qualified timestamp when the capture has one. Confirms the evidence has not been tampered with since capture.
Changes things 2Claude Code: ask
  • create_scheduleRegister a recurring capture schedule for a URL using a cron expression.Can send data outNo findings

    Why it is in this group

    • The name "create_schedule" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Register a recurring capture schedule for a URL using a cron expression. Requires capture scope; minimum interval is hourly. Returns the new schedule ID and next scheduled run time. Use list_schedules to see all schedules or delete_schedule to remove one.
  • update_scheduleChange a schedule: rename it, point it at a different URL, change how often it runs, or pause and resume it.Can send data outNo findings

    Why it is in this group

    • The name "update_schedule" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Change a schedule: rename it, point it at a different URL, change how often it runs, or pause and resume it. Pass only the fields to change. Resuming, or changing the frequency, sets the next run to the next matching time from now; missed runs are not caught up.
Only reads 7Show 7 read-only tools
  • diff_capturesCompare two complete captures owned by this account and return a structured diff of HTML, screenshot, and HTTP headers.Reads text others writeNo findings

    Why it is in this group

    • The name "diff_captures" says "diff": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "compare" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Compare two complete captures owned by this account and return a structured diff of HTML, screenshot, and HTTP headers. Both captures must be in complete status; pending or failed captures are not eligible. Use the summary to quickly see whether the page changed, then inspect the html or headers sections for details.
  • get_captureGet the status and details of a capture by ID.No findings

    Why it is in this group

    • The name "get_capture" says "get": a word for reading.
    Description, as the server wrote it
    Get the status and details of a capture by ID. Returns status (pending, complete, failed) and when complete includes artifact URLs for screenshot, HTML, WACZ bundle, and a verification link. No additional auth scope needed beyond the route-level read scope.
  • get_certificateRetrieve certificate metadata for a complete capture, summarizing the FRE 902(13) attestation details, bundle hash, Ed25519 key ID, and timestamp status.No findings

    Why it is in this group

    • The name "get_certificate" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve certificate metadata for a complete capture, summarizing the FRE 902(13) attestation details, bundle hash, Ed25519 key ID, and timestamp status. Returns formatted text, not a binary PDF; use the certificate URL to download the actual PDF. Useful for programmatic verification of signing metadata before presenting evidence.
  • get_usageReturn current-period quota usage for this account, including capture count, storage bytes, billing status, and reset date.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    Return current-period quota usage for this account, including capture count, storage bytes, billing status, and reset date. No additional scope is required beyond the read scope used for MCP access. Use this to check remaining quota before submitting large batches.
  • list_capturesList your recent captures with optional filters.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "list_captures" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    List your recent captures with optional filters. Returns summaries in reverse chronological order (newest first by default). Supports filtering by status, URL prefix, date range, schedule, and custom sort. Use offset for pagination. Use get_capture with a specific ID for full details.
  • list_schedulesList all scheduled captures registered for this account, including their URL, cron expression, and next scheduled run time.Reads text others writeNo findings

    Why it is in this group

    • The name "list_schedules" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List all scheduled captures registered for this account, including their URL, cron expression, and next scheduled run time. Requires capture scope. Use create_schedule to add a new schedule or delete_schedule to remove one.
  • read_sitemapRead a sitemap (or a sitemap index and up to 10 of its child sitemaps) and return up to 200 page URLs.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "read_sitemap" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Read a sitemap (or a sitemap index and up to 10 of its child sitemaps) and return up to 200 page URLs. Nothing is captured; pass the URLs to batch_capture in groups no larger than your per-minute rate limit (10 by default). Private addresses, compressed (.xml.gz) sitemaps and sitemaps over 5 MB are refused. Requires the capture scope; 10 reads per minute.

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.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out6
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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:24 UTC, unchanged since Nov 21, 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
6
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 6 tools that change things (1 destructive, 3 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.webresourceledger.com/mcp: tools/list returned 13 tools to an anonymous client, including delete_schedule (destructive), capture_url (irreversible), verify_capture (irreversible), batch_capture (irreversible), create_schedule (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 6 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 6
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
  2. Tools4 changed.~4 changedView diff

Install

Pinned to version 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http web-resource-ledger https://api.webresourceledger.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http web-resource-ledger https://api.webresourceledger.com/mcp --header 'Authorization: <your-authorization>'

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__web-resource-ledger__get_capture",
      "mcp__web-resource-ledger__diff_captures",
      "mcp__web-resource-ledger__get_usage",
      "mcp__web-resource-ledger__list_schedules",
      "mcp__web-resource-ledger__get_certificate"
    ],
    "ask": [
      "mcp__web-resource-ledger__capture_url",
      "mcp__web-resource-ledger__list_captures",
      "mcp__web-resource-ledger__verify_capture",
      "mcp__web-resource-ledger__batch_capture",
      "mcp__web-resource-ledger__read_sitemap",
      "mcp__web-resource-ledger__create_schedule",
      "mcp__web-resource-ledger__update_schedule"
    ],
    "deny": [
      "mcp__web-resource-ledger__delete_schedule"
    ]
  }
}

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 web-resource-ledger. Review it before you use it.

Capability tags behind 8 rules
  • mcp__web-resource-ledger__capture_url outbound
  • mcp__web-resource-ledger__list_captures untrusted-input, outbound
  • mcp__web-resource-ledger__batch_capture outbound
  • mcp__web-resource-ledger__diff_captures untrusted-input
  • mcp__web-resource-ledger__read_sitemap untrusted-input, outbound
  • mcp__web-resource-ledger__list_schedules untrusted-input
  • mcp__web-resource-ledger__create_schedule outbound
  • mcp__web-resource-ledger__update_schedule outbound

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/io.github.benpeter/web-resource-ledger/verify?hash=15cb59982ab25a1d2301270c671538e9c2005670bd15c484cc3014d538e33d68" | jq -e '.changed == false'

Pinned hash 15cb59982ab2, from Nov 16, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.benpeter/web-resource-ledger/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.benpeter/web-resource-ledger
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.benpeter/web-resource-ledger.svg)](https://radar.anlyon.com/servers/io.github.benpeter/web-resource-ledger)

Source: MCP Registry · repository. Synced Nov 16, 2026, 00:18 UTC.

Web Resource Ledger MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Web Resource Ledger MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 6 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 Web Resource Ledger MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_schedule.

Can the Web Resource Ledger MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: capture_url, verify_capture and batch_capture.

What tools does the Web Resource Ledger MCP server have?

13 tools: 1 destructive, 3 irreversible, 2 write, 7 read. delete_schedule, capture_url, verify_capture, batch_capture, create_schedule, update_schedule, get_capture, list_captures and 5 more.

Does the Web Resource Ledger MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Web Resource Ledger MCP server send data to outside services?

6 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): capture_url, list_captures, batch_capture, read_sitemap, create_schedule and update_schedule.

Has the Web Resource Ledger MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.