Skip to content

OxyPages MCP server

com.oxypages/oxypagesoxypages.comstreamable-httpv1.1.1Scanned

Deploy HTML pages and built web apps (React, Vue, Vite) to a live HTTPS link from your AI agent.

2 tools: 1 do something that can't be undone and 1 change things.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the OxyPages MCP server can do

The OxyPages MCP server is published by oxypages.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_page) and create or change data (1 tool: deploy_app), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (publish_page and deploy_app); 1 tool can send data out of your system (publish_page).

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 8, 2026, version 1.1.1.

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.

2 tools

Can't be undone 1Claude Code: ask
  • publish_pagePublish a website on OxyPages with no account and get a live HTTPS link.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_page" says "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_page" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish a website on OxyPages with no account and get a live HTTPS link. The link lasts 30 minutes unless the user claims it into a free account with claim_url. Up to 3 MB and 10 files. Send either html (one complete page) or files (several files, index.html at the top level). HTML, CSS, JS and images only - no SVG or PDF. For a framework app (React, Vue, Vite, Astro...), run its build and use deploy_app with the output folder instead, when deploy_app is listed. After publishing, give the user url, tell them it expires in 30 minutes, and give them claim_url to keep it.

    Annotations the server declares

    • title: Publish a page on OxyPages
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • deploy_appDeploy an already-BUILT web app (React, Vue, Svelte, Vite, Astro static output, any single-page app) to OxyPages with no account and get a live HTTPS link with Single-Page App rout…Reads text others writeNo findings

    Why it is in this group

    • The name "deploy_app" says "deploy": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Deploy an already-BUILT web app (React, Vue, Svelte, Vite, Astro static output, any single-page app) to OxyPages with no account and get a live HTTPS link with Single-Page App routing. OxyPages does NOT build: Run the project's build first (npm run build, or the build script in package.json) and send the OUTPUT folder (usually dist/, build/ or out/), not the source. Never send node_modules, source files or package.json - source is refused with needs_build. Text as utf8, binaries as base64. Up to 25 MB and 500 files. If the output has no index.html, pass root (the HTML file to serve at /) or root "none". The link lasts 30 minutes: give the user url AND claim_url, and tell them to open claim_url to keep the app in a free account.

    Annotations the server declares

    • title: Deploy a built app on OxyPages
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true

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

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 18, 2026, 16:23 UTC, unchanged since Nov 11, 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
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.oxypages.com/.well-known/oauth-protected-resource
Authorization servers
https://mcp.oxypages.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://mcp.oxypages.com/mcp: tools/list returned 2 tools to an anonymous client, including publish_page (irreversible), deploy_app (write)

    What this check looks for

Posture changes

  1. Nov 11, 2026
    • Tools that change things, listed without credentials: 1 to 2
  2. Nov 4, 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 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • RFC 9728 protected resource metadata: none to https://mcp.oxypages.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://mcp.oxypages.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

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. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2
  2. Tools1 added, 1 changed.+1 added~1 changedView diff
  3. 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 -> 1 (and 6 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 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • RFC 9728 protected resource metadata: none to https://mcp.oxypages.com/.well-known/oauth-protected-resource
    • Authorization servers: none to https://mcp.oxypages.com
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Install

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

claude mcp add --transport http oxypages https://mcp.oxypages.com/mcp
claude mcp add --transport http oxypages https://mcp.oxypages.com/mcp

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": [],
    "ask": [
      "mcp__oxypages__publish_page",
      "mcp__oxypages__deploy_app"
    ],
    "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 oxypages. Review it before you use it.

Capability tags behind 2 rules
  • mcp__oxypages__publish_page untrusted-input, outbound
  • mcp__oxypages__deploy_app untrusted-input

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/com.oxypages/oxypages/verify?hash=75017b923b7c2ba24164a1d4a3b0def71d87942fc1c00a8d62e7a4528b27a615" | jq -e '.changed == false'

Pinned hash 75017b923b7c, from Nov 8, 2026, 05:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.oxypages/oxypages/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 13, 2026, 07:17 UTC.

OxyPages MCP server: questions and answers

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

Is the OxyPages MCP server safe?

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

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

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

Yes. 1 tool can send, pay, publish or merge: publish_page.

What tools does the OxyPages MCP server have?

2 tools: 1 irreversible, 1 write. publish_page and deploy_app.

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

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

Does the OxyPages 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): publish_page.

Has the OxyPages MCP server changed its tools?

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