BrewPage MCP
NPM · BREWPAGE-MCP · SCANNED SEP 22
Publish HTML, Markdown, KV, JSON, and files to brewpage.app from AI assistants. No signup.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 105 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 597 tokens (~99/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_html" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BrewPage MCP server?
BrewPage MCP runs locally as an npm package, launched with npx -y brewpage-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · brewpage-mcp
claude mcp add kochetkov-ma-brewpage-mcp -- npx -y brewpage-mcp
{
"mcpServers": {
"kochetkov-ma-brewpage-mcp": {
"command": "npx",
"args": [
"-y",
"brewpage-mcp"
]
}
}
} {
"servers": {
"kochetkov-ma-brewpage-mcp": {
"command": "npx",
"args": [
"-y",
"brewpage-mcp"
]
}
}
} codex mcp add kochetkov-ma-brewpage-mcp -- npx -y brewpage-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kochetkov-ma-brewpage-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"brewpage-mcp"
],
"enabled": true
}
}
} openclaw mcp add kochetkov-ma-brewpage-mcp --command npx --arg -y --arg brewpage-mcp
mcp_servers:
kochetkov-ma-brewpage-mcp:
command: "npx"
args: ["-y", "brewpage-mcp"] {
"McpServers": {
"kochetkov-ma-brewpage-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"brewpage-mcp"
]
}
}
} assistant mcp add kochetkov-ma-brewpage-mcp -t stdio -c npx -a -y brewpage-mcp
{
"mcpServers": {
"kochetkov-ma-brewpage-mcp": {
"command": "npx",
"args": [
"-y",
"brewpage-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
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 22 Sept 2026 · Analysed npm/brewpage-mcp@1.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delete_resource ~76
Delete a BrewPage resource (HTML page, KV store, JSON collection, or file) using the owner token.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Resource ID |
| namespace | string | yes | Resource namespace |
| ownerToken | string | yes | Owner token received when the resource was created |
| type | string | yes | Resource type to delete |
No output schema declared.
No examples provided.
get_page ~52
Fetch a published BrewPage HTML page content by namespace and ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Page ID |
| namespace | string | yes | Page namespace |
| password | string | – | Password if the page is protected |
No output schema declared.
No examples provided.
get_stats ~26
Get BrewPage platform-wide usage statistics including page count, file count, and storage usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_file ~67
Upload a file to BrewPage via URL. Returns a public URL and owner token.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Custom filename (optional) |
| namespace | string | – | Namespace for the file (optional, defaults to 'public') |
| url | string | yes | URL of the file to upload |
No output schema declared.
No examples provided.
publish_html ~187
Publish HTML or Markdown content to BrewPage. Returns a public URL and owner token. Supports password protection, custom TTL, optional filename, and an opt-in top toolbar (showTopBar).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | HTML or Markdown content to publish |
| filename | string | – | Optional original filename (≤200 chars). Used as title fallback when no <title>/<h1>; immutable on update. |
| format | string | – | Content format: HTML or MARKDOWN |
| namespace | string | – | Namespace for the page (optional, defaults to 'public') |
| password | string | – | Optional password to protect the page |
| showTopBar | boolean | – | Add a thin top toolbar (filename + Download button + theme toggle) on the served page. Default: hidden. |
| ttlDays | integer | – | Time to live in days (1-30, default: 15) |
No output schema declared.
No examples provided.
publish_site ~189
Publish an HTML site to BrewPage. Single-page: pass `entryContent`. Multi-page: pass `files` (array of `{path, content}`). Optional `entry` overrides default `index.html`.
| Name | Type | Req | Description |
|---|---|---|---|
| entry | string | – | Entry file path, default index.html |
| entryContent | string | – | HTML content for a single-page site (entry file). Mutually exclusive with `files`. |
| files | array | – | Multi-file site: array of `{path, content}`. Mutually exclusive with `entryContent`. |
| namespace | string | – | Namespace for the site (optional, defaults to 'public') |
| ownerToken | string | – | Existing owner token to group this site under the same owner as previous content |
| password | string | – | Optional password to protect the site |
| ttlDays | number | – | Time to live in days (1-30, default: 15) |
No output schema declared.
No examples provided.
What is the BrewPage MCP server?
BrewPage MCP is listed in the public MCP registry as io.github.kochetkov-ma/brewpage-mcp. Publish HTML, Markdown, KV, JSON, and files to brewpage.app from AI assistants. No signup. This page covers its npm package (brewpage-mcp).
Is the BrewPage MCP server safe to use?
BrewPage MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 BrewPage MCP server expose?
BrewPage MCP exposes 6 tools: publish_html, publish_file, delete_resource, get_page, get_stats, publish_site. Their descriptions and schemas cost roughly 597 tokens of context every time the server is loaded.
Is the BrewPage MCP server still maintained?
BrewPage MCP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the BrewPage MCP server under?
BrewPage MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.