Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Crypto-Goatz/rocket-plus-mcp

NPM · ROCKET-PLUS-MCP

56+ AI tools for CRM, content, workflows, SkillForge & marketing automation.

Available components

0 this week 70 Trust /100

Last scanned (14 hours ago)

Scores higher than 41% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.5.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 7 of 14 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3267 tokens (~46/item across 71 items; 64 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_sms" implies "send" 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 65 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 19 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 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.

  • 9 Nov 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 7 Nov 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.

Diagnostics

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 21 Nov 2026 · Analysed npm/rocket-plus-mcp@2.1.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 →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-w48q-cv73-mx4w CVE-2025-66414 high yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 14 packages
Packages resolved 14
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 64 exposed · ~3,192 tokens

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 →

Tool Tokens
seo_analyze ~40

Analyze a page for SEO issues and opportunities

NameTypeReqDescription
keywordsstring–Target keywords (comma-separated)
urlstringyesURL to analyze

No output schema declared.

No examples provided.

seo_generate_meta ~53

Generate SEO-optimized meta tags

NameTypeReqDescription
contentstringyesPage content or description
keywordsstring–Target keywords
typestring–Page type: homepage, product, blog, landing

No output schema declared.

No examples provided.

seo_keyword_research ~43

Get keyword suggestions and search volume estimates

NameTypeReqDescription
intentstring–Intent: informational, commercial, transactional
seedstringyesSeed keyword or topic

No output schema declared.

No examples provided.

skillforge_create ~68

Create a custom SkillForge skill from a description

NameTypeReqDescription
descriptionstringyesWhat the skill should do
namestringyesSkill name
outputsarray–Expected outputs (tags, fields, actions)
triggersarray–CRM events that trigger this skill

No output schema declared.

No examples provided.

skillforge_execute ~110

Execute a SkillForge AI skill. Available skills: lead-qualifier (AI lead scoring), proposal-generator (auto-generate proposals), content-loop (blog + social campaigns).

NameTypeReqDescription
asyncboolean–Run asynchronously (default: false)
contactIdstringyesContact ID to execute skill for
inputobject–Additional input data for the skill
skillIdstringyesSkill ID: lead-qualifier, proposal-generator, content-loop, or custom skill ID

No output schema declared.

No examples provided.

skillforge_list ~40

List all available SkillForge skills (pre-built and custom)

NameTypeReqDescription
categorystring–Filter by category: lead-gen, sales, content, custom

No output schema declared.

No examples provided.

skillforge_results ~45

Get the results of a completed SkillForge execution

NameTypeReqDescription
executionIdstringyesExecution ID
formatstring–Output format: full, summary, actions-only

No output schema declared.

No examples provided.

skillforge_status ~30

Check the status of a SkillForge execution

NameTypeReqDescription
executionIdstringyesExecution ID to check

No output schema declared.

No examples provided.

skillforge_usage ~34

Get SkillForge usage statistics and billing info

NameTypeReqDescription
periodstring–Period: today, week, month, all

No output schema declared.

No examples provided.

update_contact ~69

Update an existing contact

NameTypeReqDescription
contactIdstringyesContact ID to update
emailstring––
firstNamestring––
lastNamestring––
phonestring––
tagsstring–Tags to set (replaces existing)

No output schema declared.

No examples provided.

visitors_active ~28

Get currently active visitors on your site

NameTypeReqDescription
siteIdstring–Site ID (optional)

No output schema declared.

No examples provided.

visitors_history ~55

Get visitor history and analytics

NameTypeReqDescription
filterstring–Filter: all, identified, high_intent
timeframestring–Timeframe: 1h, 24h, 7d, 30d

No output schema declared.

No examples provided.

webhook_create ~51

Create a new webhook endpoint

NameTypeReqDescription
eventsarray–Events to listen for
namestringyesWebhook name
targetUrlstring–URL to forward webhooks to (optional)

No output schema declared.

No examples provided.

webhook_list ~26

List webhook endpoints and recent events

NameTypeReqDescription
includeEventsboolean–Include recent events

No output schema declared.

No examples provided.

Install

How do I install the io.github.Crypto-Goatz/rocket-plus-mcp server?

io.github.Crypto-Goatz/rocket-plus-mcp runs locally as an npm package, launched with npx -y rocket-plus-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 · rocket-plus-mcp

# add to Claude Code
claude mcp add crypto-goatz-rocket-plus-mcp -- npx -y rocket-plus-mcp
Common questions

What is the io.github.Crypto-Goatz/rocket-plus-mcp server?

io.github.Crypto-Goatz/rocket-plus-mcp is listed in the public MCP registry as io.github.Crypto-Goatz/rocket-plus-mcp. 56+ AI tools for CRM, content, workflows, SkillForge & marketing automation. This page covers its npm package (rocket-plus-mcp).

Is the io.github.Crypto-Goatz/rocket-plus-mcp server safe to use?

io.github.Crypto-Goatz/rocket-plus-mcp scores 70 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 21 November 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 io.github.Crypto-Goatz/rocket-plus-mcp server expose?

io.github.Crypto-Goatz/rocket-plus-mcp exposes 64 tools: get_contacts, create_contact, update_contact, add_tags, get_opportunities, and 59 more. Their descriptions and schemas cost roughly 3,192 tokens of context every time the server is loaded.

Is the io.github.Crypto-Goatz/rocket-plus-mcp server still maintained?

io.github.Crypto-Goatz/rocket-plus-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.Crypto-Goatz/rocket-plus-mcp server under?

io.github.Crypto-Goatz/rocket-plus-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.

What did VerifyMCP test on the io.github.Crypto-Goatz/rocket-plus-mcp server?

VerifyMCP ran 16 checks on io.github.Crypto-Goatz/rocket-plus-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.