Houseofmvps/ultraship

COLLECTIONcommunity
v2.10.0HouseofmvpsMITUpdated 3mo agonpmGitHub

"ULTRASHIP" Claude Code plugin — 39 skills, 33 tools, 11 agents for ship-ready workflows: planning, review, pentesting, safety guardrails, canary monitoring, SEO/AI-readiness check, penetration testing, code review, competitive analysis, incident response. 1 dependency. 180 tests. MIT.

Built by Kaileskkhumar, founder of HouseofMVPs and Kailxlabs runs 5 tools in parallel and outputs a scorecard: Each tool is a standalone Node.js script (). JSON output. Exit 0 always. No build step. Tool | What it checks | | 63 rules: 39 SEO (meta tags, canonicals, headings, OG tags, structured data, sitemap, cross-page duplicate/orphan detection), 20 GEO (AI bot access in robots.txt, snippet…

This collection bundles
42 skills12 agents1 MCP server37 commands

⚠ The trust score below reflects the installer package ultraship only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
244Downloads/wk
106GitHub stars
13Forks
3mo agoLast update
Package
AuthorHouseofmvps
LicenseMIT
Version2.10.0
Sourcegithub
npmultraship
GitHubHouseofmvps/ultraship
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✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv2.10.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

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

Tools

No tool declarations found in the source3mo ago

Forge read 45 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Built by Kaileskkhumar, founder of HouseofMVPs and Kailxlabs runs 5 tools in parallel and outputs a scorecard: Each tool is a standalone Node.js script (). JSON output. Exit 0 always. No build step. Tool | What it checks | | 63 rules: 39 SEO (meta tags, canonicals, headings, OG tags, structured data, sitemap, cross-page duplicate/orphan detection), 20 GEO (AI bot access in robots.txt, snippet restrictions, llms.txt, structured data for AI extraction), 4 AEO (FAQPage/HowTo/speakable schema) | |…

Keywords
aeoaiclaudeclaude-codeclaude-code-pluginclaude-code-pluginscode-reviewcompetitive-analysisdeveloper-toolsgenerative-engine-optimizationgeoindie-hackerslighthousellms-txtmcpperformanceplaywrightsaassecurityseocollection
Alternatives
Comparing tool surfaces…

No dependency coverage

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

Topics

Related in security