Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CyberPunk11147/cyberwarex-web-access

OCI · GHCR.IO/CYBERPUNK11147/CYBERWAREX-WEB-ACCESS

Web access for agents: fetch, extract, screenshot, or PDF any public URL.

+3 this week 46 Trust /100

Last scanned (49 minutes ago)

Scores higher than 65% of OCI servers

Category Browser Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 172 tokens (~43/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Analysed oci/ghcr.io/cyberpunk11147/cyberwarex-web-access@1.5.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~172 tokens

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 →

Tool Tokens
web_extract ~40

Return text + attributes of elements matching a CSS selector on a fully rendered page.

NameTypeReqDescription
selectorstringyesCSS selector
urlstringyes–

No output schema declared.

No examples provided.

web_fetch ~57

Render a live web page (JavaScript executed) and return clean content. Use this to read pages an LLM can't reach natively.

NameTypeReqDescription
formatstring––
urlstringyesPublic http(s) URL to render

No output schema declared.

No examples provided.

web_pdf ~30

Render a live web page and return it as a PDF (base64).

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

web_screenshot ~45

Render a live web page and return a PNG screenshot (base64).

NameTypeReqDescription
fullpageboolean––
urlstringyes–
widthinteger––

No output schema declared.

No examples provided.

Install

How do I install the io.github.CyberPunk11147/cyberwarex-web-access MCP server?

io.github.CyberPunk11147/cyberwarex-web-access runs locally as a container image, launched with docker run --rm -i -e AWA_X_PAYMENT -e AWA_BASE_URL ghcr.io/cyberpunk11147/cyberwarex-web-access:1.5.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cyberpunk11147/cyberwarex-web-access

# add to Claude Code
claude mcp add cyberpunk11147-cyberwarex-web-access -- docker run --rm -i -e AWA_X_PAYMENT -e AWA_BASE_URL ghcr.io/cyberpunk11147/cyberwarex-web-access:1.5.0

This image reads AWA_X_PAYMENT and AWA_BASE_URL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the io.github.CyberPunk11147/cyberwarex-web-access MCP server?

io.github.CyberPunk11147/cyberwarex-web-access is an MCP server listed in the public MCP registry as io.github.CyberPunk11147/cyberwarex-web-access. Web access for agents: fetch, extract, screenshot, or PDF any public URL. This page covers its container image (ghcr.io/cyberpunk11147/cyberwarex-web-access).

Is the io.github.CyberPunk11147/cyberwarex-web-access MCP server safe to use?

io.github.CyberPunk11147/cyberwarex-web-access scores 46 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 io.github.CyberPunk11147/cyberwarex-web-access MCP server expose?

io.github.CyberPunk11147/cyberwarex-web-access exposes 4 tools: web_fetch, web_extract, web_screenshot, web_pdf. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.

Is the io.github.CyberPunk11147/cyberwarex-web-access MCP server still maintained?

io.github.CyberPunk11147/cyberwarex-web-access is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.