Skip to content

webcapture MCP server

io.webcapture/webcapturewebcapture.iostreamable-httpv1.0.2Scanned

Hosted MCP server: render any URL to print-stable PDF, PNG, WebP or Markdown

3 tools: 1 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • 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 webcapture MCP server can do

The webcapture MCP server is published by webcapture.io, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: render_pdf), but cannot delete data. 2 tools only read.

1 tool reads private data (get_usage); 1 tool brings in text other people can write (render_pdf); 1 tool can send data out of your system (render_pdf). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.2.

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.

3 tools

Changes things 1Claude Code: ask
  • render_pdfRender a web page to PDF, PNG, JPEG, WebP or Markdown.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Render a web page to PDF, PNG, JPEG, WebP or Markdown. Returns the download URL of the finished file; fetch it with your API key as the Bearer token. One tool call: the answer carries the finished file's download URL; no job polling.

    Annotations the server declares

    • title: Render a URL to PDF or image
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • get_pricingList the pricing tiers with their monthly price in USD and their included monthly conversions.No findings

    Why it is in this group

    • The name "get_pricing" says "get": a word for reading.
    Description, as the server wrote it
    List the pricing tiers with their monthly price in USD and their included monthly conversions.

    Annotations the server declares

    • title: Show pricing tiers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_usageReport the calling key's monthly quota state: tier, calendar month, renders used, monthly limit, remaining renders, and the date the count resets.Reads private dataNo findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "calendar": it reads calendars.
    Description, as the server wrote it
    Report the calling key's monthly quota state: tier, calendar month, renders used, monthly limit, remaining renders, and the date the count resets.

    Annotations the server declares

    • title: Show my quota usage
    • 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.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
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 out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__webcapture__render_pdf"
    ]
  }
}

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 14, 2026, 12:22 UTC, unchanged since Oct 30, 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
1
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://webcapture.io/mcp: tools/list returned 3 tools to an anonymous client, including render_pdf (write)

    What this check looks for

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. Tools1 changed.~1 changedView diff
  2. Tools3 changed.~3 changedView diff

Install

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

claude mcp add --transport http webcapture https://webcapture.io/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http webcapture https://webcapture.io/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__webcapture__get_usage",
      "mcp__webcapture__get_pricing"
    ],
    "ask": [
      "mcp__webcapture__render_pdf"
    ],
    "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 webcapture. Review it before you use it.

Capability tags behind 2 rules
  • mcp__webcapture__render_pdf untrusted-input, outbound
  • mcp__webcapture__get_usage private-data

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.webcapture/webcapture/verify?hash=904bcc608e80d6e87e5e5068e1aab1fcad6a0da1e376ec7052b560c8b8471cd7" | jq -e '.changed == false'

Pinned hash 904bcc608e80, from Nov 15, 2026, 23:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.webcapture/webcapture/changes.xml

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

Badge

Anlyon Radar badge for io.webcapture/webcapture
[![Anlyon Radar](https://radar.anlyon.com/badge/io.webcapture/webcapture.svg)](https://radar.anlyon.com/servers/io.webcapture/webcapture)

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

webcapture MCP server: questions and answers

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

Is the webcapture MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 1 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 webcapture MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the webcapture MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the webcapture MCP server have?

3 tools: 1 write, 2 read. render_pdf, get_usage and get_pricing.

Does the webcapture MCP server need sign-in or OAuth?

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

Does the webcapture MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): render_pdf.

Has the webcapture MCP server changed its tools?

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