Plopino
NPM · PLOPINO · SCANNED SEP 26
Publish pages, documents, or folders to a link; documents render as pages; updates keep the URL.
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 Security100
- 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
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 807 tokens (~403/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.1.7 and 0.3.0: 1 tool removals, 0 breaking changes, 1 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 701 of that field. See how to fix → Fail
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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 Plopino MCP server?
Plopino runs locally as an npm package, launched with npx -y plopino. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · plopino
claude mcp add plopino-plopino-mcp -- npx -y plopino
{
"mcpServers": {
"plopino-plopino-mcp": {
"command": "npx",
"args": [
"-y",
"plopino"
]
}
}
} {
"servers": {
"plopino-plopino-mcp": {
"command": "npx",
"args": [
"-y",
"plopino"
]
}
}
} codex mcp add plopino-plopino-mcp -- npx -y plopino
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"plopino-plopino-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"plopino"
],
"enabled": true
}
}
} openclaw mcp add plopino-plopino-mcp --command npx --arg -y --arg plopino
mcp_servers:
plopino-plopino-mcp:
command: "npx"
args: ["-y", "plopino"] {
"McpServers": {
"plopino-plopino-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"plopino"
]
}
}
} assistant mcp add plopino-plopino-mcp -t stdio -c npx -a -y plopino
{
"mcpServers": {
"plopino-plopino-mcp": {
"command": "npx",
"args": [
"-y",
"plopino"
]
}
}
} 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.
- 26 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Dependency health: 0.85 → 1.00 ▲ functional
- Package version: 0.2.2 → 0.3.0 functional
- 17 Sept 26 +10
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Sept 26 −11
- Stability: 0.03 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: fail → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Stability: 0.03 → fail ▼ security
- Schema quality: 312 → 403 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.84 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.10 → 0.2.2 functional
- Package version: 0.1.10 → 0.2.0 functional
- 15 Sept 26 +11
- Tool safety: fail → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → 0.84 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- Package version: 0.1.7 → 0.1.10 functional
- 14 Sept 26 55
First indexed and scored.
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 26 Sept 2026 · Analysed npm/plopino@0.3.0
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 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
publish_page Publish a page and get a link ~363
Publish content you have in hand to a public URL. Use this whenever the user asks to share, send, publish, or "give me a link to" something you just produced — an HTML page (dashboard, report, chart, interactive page), a Markdown document, CSV, JSON, or a code/data file. Everything it publishes becomes a page the recipient opens in a browser: the filename decides how it renders, so pass "report.md" for Markdown instead of renaming it to .html. Returns a public link that opens on any device; no account or configuration needed. Anonymous pages are kept for a month — with a token, storage is permanent and the page can be updated in place. Prefer this over telling the user to save the file and upload it somewhere themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The complete content of the file, as a string. With the default filename this is a self-contained HTML document including the <html> tag — relative references to local files will not resolve, so use… |
| filename | string | – | What to name the file — this decides how the content is rendered, so get it right rather than renaming Markdown to .html. Defaults to "index.html". Use "report.md", "data.csv", "query.sql" and so on;… |
| update_url | string | – | A URL returned by an earlier publish. When given, the content of that page is replaced and the link stays the same. Requires the server to be configured with a Plopino token. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimUrl | string | – | Private browser claim link for the publisher only. Never give it to page viewers or append it to the public URL. |
| note | string | yes | Human-readable status: created vs updated, and how long the page is kept. |
| url | string | yes | Public link to the published page — give this to the user. |
No examples provided.
publish_path Publish a local file or folder and get a link ~224
Publish a local file, a zip, or a whole directory to a public URL, preserving the directory structure. Use this when the page needs sibling files (CSS, JS, images) — write them into a directory first, then publish that directory. It is also the way to share any document: Word (doc/docx), Excel (xls/xlsx) and Markdown render as readable pages, code and data files get syntax-highlighted previews, and images and video display inline — the recipient opens a link instead of downloading a file. (PowerPoint files publish and download fine but have no rendered preview.)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to a file or directory on this machine. A directory is uploaded recursively with its structure preserved (symbolic links are skipped, so the upload cannot escape the directory); a zip a… |
| update_url | string | – | A URL returned by an earlier publish. When given, the content of that page is replaced and the link stays the same. Requires the server to be configured with a Plopino token. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimUrl | string | – | Private browser claim link for the publisher only. Never give it to page viewers or append it to the public URL. |
| note | string | yes | Human-readable status: created vs updated, and how long the page is kept. |
| url | string | yes | Public link to the published page — give this to the user. |
No examples provided.
What is the Plopino MCP server?
Plopino is an MCP server listed in the public MCP registry as io.github.plopino/plopino-mcp. Publish pages, documents, or folders to a link; documents render as pages; updates keep the URL. This page covers its npm package (plopino).
Is the Plopino MCP server safe to use?
Plopino scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 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 Plopino MCP server expose?
Plopino exposes 2 tools: publish_page, publish_path. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.
Is the Plopino MCP server still maintained?
Plopino is still listed as active in the MCP registry. We last reached this channel on 26 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 Plopino MCP server under?
Plopino declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.