Skip to content

stub.page MCP server

page.stub/stub-pagestub.pagestreamable-httpv0.1.0Scanned

Publish plain-text posts at a public URL. No account, no sign-up.

4 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

3 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 →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the stub.page MCP server can do

The stub.page MCP server is published by stub.page, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: delete_page), do things that cannot be undone, such as sending, paying or publishing (create_page) and create or change data (1 tool: update_page). 1 tool only reads.

1 tool brings in text other people can write (get_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.

Last scanned Nov 19, 2026, version 0.1.0.

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.

4 tools

Deletes or cancels 1Claude Code: deny
  • delete_pagePermanently delete a post.No findings

    Why it is in this group

    • The name "delete_page" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    Description, as the server wrote it
    Permanently delete a post. Requires the edit_key. The slug is never reused and the deletion cannot be undone.
Can't be undone 1Claude Code: ask
  • create_pagePublish a new text post and return its slug, public URL and edit_key.No findings

    Why it is in this group

    • The name "create_page" says "create": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    • The description says "cannot be recovered".
    Description, as the server wrote it
    Publish a new text post and return its slug, public URL and edit_key. Content is Markdown (paragraphs, headings, bold, italic, lists, quotes, code, links, and images via external https URLs — images are embedded, never hosted). The returned edit_key is shown exactly once and cannot be recovered. Keep it in context — without it the page can never be edited or deleted again.
Changes things 1Claude Code: ask
  • update_pageReplace title and/or content of an existing post.No findings

    Why it is in this group

    • The name "update_page" says "update": a word for a change.
    Description, as the server wrote it
    Replace title and/or content of an existing post. Requires the edit_key from create_page. The URL stays the same even when the title changes.
Only reads 1Show 1 read-only tool
  • get_pageFetch a published post by slug.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Fetch a published post by slug. Public — no edit_key required.

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 or outbound.

Reads private data0
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 out0
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 20, 2026, 19:17 UTC, unchanged since Oct 22, 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://stub.page/.well-known/oauth-protected-resource
Authorization servers
https://stub.page
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://stub.page/mcp: tools/list returned 4 tools to an anonymous client, including delete_page (destructive), create_page (irreversible), update_page (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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http stub-page https://stub.page/mcp
claude mcp add --transport http stub-page https://stub.page/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": [
      "mcp__stub-page__get_page"
    ],
    "ask": [
      "mcp__stub-page__create_page",
      "mcp__stub-page__update_page"
    ],
    "deny": [
      "mcp__stub-page__delete_page"
    ]
  }
}

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 stub-page. Review it before you use it.

Capability tags behind 1 rule
  • mcp__stub-page__get_page 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/page.stub/stub-page/verify?hash=b1433c747a330b73ca6148e7491fe85c9d784a2836e9994a122e7f7bd2d53fa0" | jq -e '.changed == false'

Pinned hash b1433c747a33, from Nov 19, 2026, 01:17 UTC.

Watch

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

https://radar.anlyon.com/servers/page.stub/stub-page/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

stub.page MCP server: questions and answers

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

Is the stub.page MCP server safe?

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

Yes. 1 tool can delete, cancel or revoke something: delete_page.

Can the stub.page MCP server do things that cannot be undone?

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

What tools does the stub.page MCP server have?

4 tools: 1 destructive, 1 irreversible, 1 write, 1 read. delete_page, create_page, update_page and get_page.

Does the stub.page MCP server need sign-in or OAuth?

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

Does the stub.page MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the stub.page MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.