# @micropage-sh/mcp

MCP server for micropage.sh: let an AI assistant create, edit and publish micropages from markup.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.1.12
- **Author:** io.github.micropage-sh
- **License:** MIT
- **npm:** @micropage-sh/mcp
- **Endpoints:** streamable-http https://mcp.micropage.sh/mcp
- **Source:** https://github.com/micropage-sh/mcp
- **Endpoint health:** reachable (last checked 2026-10-11T15:37:29.594Z, 1 sample) — 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

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-13T23:16:20.947Z
- **Version scanned:** 0.1.12
- **CVEs:** none found by OSV at scan time

## Tools

22 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `whoami`
- `publish_build`
- `get_deploy_status`
- `list_builds` — List a micropage project's builds, newest first: number, id, status (draft, publishing, deployed, failed), created and updated times, failure reason, and which 
- `upload_asset`
- `list_files` — List the files stored in a micropage project (images uploaded by upload_asset, the editor or the CLI), newest first: filename, type, size, SHA-256 and upload da
- `get_file_url` — Get the URL a stored project file is served from, by its filename (as list_files reports it). Use it when the user wants a link to an uploaded image, or a full 
- `list_forms` — List the forms on a micropage project's site (registered when the page markup is saved): form uuid, name, page, whether it is the site footer form, and how many
- `list_submissions`
- `list_posts`
- `upsert_post`
- `preview_post_send`
- `publish_post`
- `unpublish_post`
- `delete_post`
- `list_projects`
- `get_project`
- `get_page_source`
- `create_project`
- `save_page`
- `delete_project`
- `get_markup_reference`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@micropage-sh/mcp\"\n      ],\n      \"env\": {\n        \"MICROPAGE_DEPLOY_TOKEN\": \"<YOUR_MICROPAGE_DEPLOY_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `MICROPAGE_DEPLOY_TOKEN` — Micropage Deploy Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; runs locally and hosted.
- Floor 57, ceiling 57 (tier: extensive)
- 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/%40micropage-sh%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40micropage-sh%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40micropage-sh%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40micropage-sh%2Fmcp
- 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.