ToolsMCP
urlsnap-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- urlsnap.dev
- Prerequisites
- Install urlsnap-mcp from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.2 · updated
- Official links
Publisher’s description
Screenshot, PDF, and markdown extraction from any URL via Claude Desktop and Claude Code.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.2, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- urlsnap.dev
- Version observed
- 1.0.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/dev.urlsnap%2Furlsnap-mcp/versions/1.0.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Extract structured data from PDFs | Publisher description mentions “pdf”, “extraction”. | No connection check or task run. Capability is as described by the publisher. | Rule pdf-extraction matched: “pdf”, “extraction”. Rule pdf-extraction. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
urlsnap-mcp(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
dev.urlsnap/urlsnap-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.