webcap
REMOTE · WEBCAP.SHOUTSID.FYI · SCANNED OCT 1
Screenshot, extract or audit any URL. Paid per call in USDC over x402; free tools need no wallet.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 993 tokens (~124/item across 8 items; 8 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 Management0
- Stability check failed: schema churn in the 6 days we've observed: 11 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the webcap MCP server?
webcap is a hosted endpoint at https://webcap.shoutsid.fyi/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 · webcap.shoutsid.fyi
claude mcp add --transport http shoutsid-lab-webcap 'https://webcap.shoutsid.fyi/mcp'
{
"mcpServers": {
"shoutsid-lab-webcap": {
"url": "https://webcap.shoutsid.fyi/mcp"
}
}
} {
"servers": {
"shoutsid-lab-webcap": {
"type": "http",
"url": "https://webcap.shoutsid.fyi/mcp"
}
}
} [mcp_servers.shoutsid-lab-webcap] url = "https://webcap.shoutsid.fyi/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shoutsid-lab-webcap": {
"type": "remote",
"url": "https://webcap.shoutsid.fyi/mcp",
"enabled": true
}
}
} openclaw mcp add shoutsid-lab-webcap --url 'https://webcap.shoutsid.fyi/mcp' --transport streamable-http
mcp_servers:
shoutsid-lab-webcap:
url: "https://webcap.shoutsid.fyi/mcp" {
"McpServers": {
"shoutsid-lab-webcap": {
"Transport": "http",
"Url": "https://webcap.shoutsid.fyi/mcp"
}
}
} assistant mcp add shoutsid-lab-webcap -t streamable-http -u 'https://webcap.shoutsid.fyi/mcp'
{
"mcpServers": {
"shoutsid-lab-webcap": {
"type": "http",
"url": "https://webcap.shoutsid.fyi/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- New tool “webcap_feedback” functional
- 25 Sept 26 61
First indexed and scored.
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 1 Oct 2026 · Probed https://webcap.shoutsid.fyi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shoutsid.fyi | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 68ccf329533890cd50203bf4c1252c95b3d |
| SANs: *.shoutsid.fyi, shoutsid.fyi | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of webcap.shoutsid.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | present | 24340 | 8 | Verified |
| shoutsid.fyi. | absent | 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://webcap.shoutsid.fyi/mcp | Verified | 200 | |
| http (plaintext) | http://webcap.shoutsid.fyi/mcp | Inconclusive | 405 |
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 →
webcap_analyze ~103
PAID ($0.01): AI analysis of one URL. Pick the task that matches the question you are answering.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | What to analyze (required, no default): classification = page type, accessibility = a11y issues, layout = structure and regions, entities = named entities and facts, sentiment = tone. |
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_audit ~68
PAID ($0.002): SEO basics plus link and Open Graph health for one URL in a single call. Returns issues with severity, not just raw tags.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_capture ~233
PAID ($0.001 image/PDF, $0.005 video): turn a URL into a persistent public artifact. png/jpeg/pdf are a screenshot or PDF and include free OG metadata; mp4/webm scroll-record the page. Settles gasless USDC over x402 — but an unpaid call runs free while the rolling per-IP allowance lasts, so just call it.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMs | integer | – | Video formats only. Scroll duration in milliseconds, 1-30000; default 5000. |
| format | string | – | Artifact format, default png. png/jpeg/pdf = screenshot/PDF at $0.001 (POST /v1/x402/capture); mp4/webm = scroll video at $0.005 (POST /v1/x402/video). The 402 challenge states the exact price for th… |
| fullPage | boolean | – | Image/PDF only. true captures the whole scrollable page (default false: viewport only). |
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_extract ~190
PAID ($0.01, one payment covers a batch of up to 50 URLs): structured content as JSON — title, headings, paragraphs, links, images, document-order markdown. Provide exactly one of "url" (a single page) or "urls" (a batch); "url" is shorthand for a one-item "urls".
| Name | Type | Req | Description |
|---|---|---|---|
| schema | string | – | Optional natural-language description of the JSON to extract. Omit it to get the default page structure. |
| url | string | – | A single page to extract, e.g. https://example.com/. Shorthand for "urls": ["<url>"]. Mutually exclusive with "urls" — sending both is an error. |
| urls | array | – | Batch of pages for one payment, at most 50 items; a batch of one is allowed. Mutually exclusive with "url" — sending both is an error. |
No output schema declared.
No examples provided.
webcap_map_lite ~107
PAID ($0.002): discover a site's URLs from its sitemap and robots.txt plus a 1-hop same-host crawl, and return them as a JSON list. Cheaper than crawling each page with webcap_extract.
| Name | Type | Req | Description |
|---|---|---|---|
| maxUrls | integer | – | Maximum number of URLs to return. Integer 1-50; default 20 when omitted. |
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_og ~54
Free Open Graph metadata for a URL: title, description, image, icon. No payment.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_preview ~94
Free bounded preview of a page: title, description, headings, links, word count and a truncated markdown slice. Use it to peek before the full extract. Rate-limited per IP. This is a teaser, not the product: the real products are free too inside the rolling per-IP allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute http(s) URL of the page to process, e.g. https://example.com/ |
No output schema declared.
No examples provided.
webcap_service_catalog ~76
Free service catalog (no payment): every paid endpoint with its exact price in USDC, the settlement network, USDC asset, payTo address, facilitator and the step-by-step x402 how-to-pay flow, plus the free allowance this caller has left. Call this first to learn what webcap sells and what it costs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the webcap MCP server?
webcap is an MCP server listed in the public MCP registry as io.github.shoutsid-lab/webcap. Screenshot, extract or audit any URL. Paid per call in USDC over x402; free tools need no wallet. This page covers its hosted endpoint (https://webcap.shoutsid.fyi/mcp).
Is the webcap MCP server safe to use?
webcap scores 60 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 webcap MCP server expose?
webcap exposes 8 tools: webcap_service_catalog, webcap_preview, webcap_og, webcap_capture, webcap_extract, and 3 more. Their descriptions and schemas cost roughly 925 tokens of context every time the server is loaded.
Does the webcap MCP server require authentication?
No. We connected to webcap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the webcap MCP server still maintained?
webcap is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.