@vibesharingapp/mcp-server

MCPcommunity
v0.17.0VibeSharingMITUpdated 1mo agonpmGitHub

MCP server for VibeSharing - register prototypes and get feedback directly from Claude Code

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
56Downloads/wk
1mo agoLast update
Needs 1 credential before it runs
  • VIBESHARING_TOKENAPI keyrequired

    Your VibeSharing deploy token (get it from vibesharing.app/dashboard/account)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorVibeSharing
LicenseMIT
Version0.17.0
Sourcenpm+mcp-registry
npm@vibesharingapp/mcp-server
GitHuberova/vibesharing-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface31 tools · 3 privileged
Security scan✓ Cleanv0.16.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

31 tools · 3 privileged
Statically extracted from the published packagev0.16.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

register_prototypeNo description published

This tool published no description. Forge does not invent one.

list_prototypesNo description published

This tool published no description. Forge does not invent one.

list_collectionsNo description published

This tool published no description. Forge does not invent one.

get_feedbackNo description published

This tool published no description. Forge does not invent one.

triage_feedbackNo description published

This tool published no description. Forge does not invent one.

close_feedback_loopNo description published

This tool published no description. Forge does not invent one.

sync_contextNo description published

This tool published no description. Forge does not invent one.

verify_tokenNo description published

This tool published no description. Forge does not invent one.

upload_sourceprivilegedNo description published

This tool published no description. Forge does not invent one.

deploy_prototypeNo description published

This tool published no description. Forge does not invent one.

share_htmlNo description published

This tool published no description. Forge does not invent one.

create_collectionNo description published

This tool published no description. Forge does not invent one.

create_campaignNo description published

This tool published no description. Forge does not invent one.

deploy_filesNo description published

This tool published no description. Forge does not invent one.

import_repoNo description published

This tool published no description. Forge does not invent one.

resolve_targetNo description published

This tool published no description. Forge does not invent one.

list_templatesNo description published

This tool published no description. Forge does not invent one.

get_templateNo description published

This tool published no description. Forge does not invent one.

quick_prototypeNo description published

This tool published no description. Forge does not invent one.

add_context_linkNo description published

This tool published no description. Forge does not invent one.

list_context_linksNo description published

This tool published no description. Forge does not invent one.

remove_context_linkprivilegedNo description published

This tool published no description. Forge does not invent one.

generate_feedback_topicsNo description published

This tool published no description. Forge does not invent one.

diagnoseNo description published

This tool published no description. Forge does not invent one.

validate_projectNo description published

This tool published no description. Forge does not invent one.

send_support_requestNo description published

This tool published no description. Forge does not invent one.

list_versionsNo description published

This tool published no description. Forge does not invent one.

rollback_deployNo description published

This tool published no description. Forge does not invent one.

fork_prototypeNo description published

This tool published no description. Forge does not invent one.

delete_prototypeprivilegedNo description published

This tool published no description. Forge does not invent one.

update_prototypeNo description published

This tool published no description. Forge does not invent one.

0 of 31 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for VibeSharing - register prototypes and get feedback directly from Claude Code

Keywords
mcpmodel-context-protocolclaudeclaude-codevibesharingprototypesfeedbackcollaborationaicursorvibe-coding
Alternatives
Comparing tool surfaces…

Tools exposed

31 tools · 3 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.