# page.stub/stub-page

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** page.stub
- **License:** Unknown
- **Endpoints:** streamable-http https://stub.page/mcp
- **Source:** https://stub.page
- **Endpoint health:** reachable (last checked 2026-10-10T06:23:26.831Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 3 days

## Security scan

**Assessment scope:** Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- **Status:** probed (endpoint answered; no code examined)
- **Scanned:** 2026-10-10T06:23:26.831Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

4 declared. Observed from a live `tools/list` probe.
- `create_page` — 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 i
- `get_page` — Fetch a published post by slug. Public — no edit_key required.
- `update_page` — 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.
- `delete_page` — Permanently delete a post. Requires the edit_key. The slug is never reused and the deletion cannot be undone.

## Install

**Verdict: review** — Installable, but 3 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- Hosted endpoint only: Forge can assess who publishes it and whether it answers, not the code behind it. No CVE, dependency or source analysis applies, so nothing here is a clean bill for that code.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"stub-page\": {\n      \"type\": \"http\",\n      \"url\": \"https://stub.page/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 32, ceiling 56 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/page.stub%2Fstub-page
- Install plan: https://forgeregistry.com/api/v1/packages/page.stub%2Fstub-page/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/page.stub%2Fstub-page
- HTML page: https://forgeregistry.com/registry/page.stub%2Fstub-page
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.