io.github.shdomi8599/vibie-mcp
NPM · VIBIE-MCP · SCANNED AUG 3
Deploy HTML folders to vibie.page from Claude / Cursor — one-line install, OAuth, auto-update.
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 440 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · vibie-mcp
claude mcp add shdomi8599-vibie-mcp -- npx -y vibie-mcp
codex mcp add shdomi8599-vibie-mcp -- npx -y vibie-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shdomi8599-vibie-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"vibie-mcp"
],
"enabled": true
}
}
} openclaw mcp add shdomi8599-vibie-mcp --command npx --arg -y --arg vibie-mcp
mcp_servers:
shdomi8599-vibie-mcp:
command: "npx"
args: ["-y", "vibie-mcp"] {
"mcpServers": {
"shdomi8599-vibie-mcp": {
"command": "npx",
"args": [
"-y",
"vibie-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.
- 2 Aug 26 +36
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Schema quality: unverified → excellent ▲ functional
- 1 Aug 26 +8
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +22
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- 27 Jul 26 24
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
vibie_create_site ~196
Create a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Category id (portfolio / wedding / landing / event / game / photo / linkbio / misc). Defaults to misc. |
| folder | string | yes | Absolute or relative path to the folder containing index.html (or a single HTML file). Required. |
| is_public | boolean | — | Whether the site appears in the public gallery. Defaults to true. |
| name | string | — | Display name. Defaults to folder name. |
| note | string | — | Optional deployment note (changelog-style). |
No output schema declared.
No examples provided.
vibie_get_site ~54
Get metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Site slug, e.g. my-site-a3f9 |
No output schema declared.
No examples provided.
vibie_list_sites ~55
List all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vibie_update_site ~135
Update an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | yes | Folder to upload. Required. |
| note | string | — | Optional deployment note (changelog-style). |
| slug | string | — | Site slug to update (e.g. my-site-a3f9). If omitted, read from .vibie/site.json in folder. |
No output schema declared.
No examples provided.