guardvibe

MCPcommunity
v3.46.0GokLabApache-2.0Updated 1d agonpmGitHub

Security infrastructure your AI can't be — deterministic, current past your model's training cutoff, whole-repo-aware, author-independent. Security MCP for vibe coding. 530 rules, 39 tools, CLI + doctor. Prompt-level shift-left security (secure_prompt — e

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 →
5GitHub stars
1d agoLast update
Package
AuthorGokLab
LicenseApache-2.0
Version3.46.0
Sourcenpm+mcp-registry
npmguardvibe
GitHubgoklab/guardvibe
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 surface40 tools · 1 privileged
Security scan✓ Cleanv3.22.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 15, 2026

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

Tools

40 tools · 1 privileged
Statically extracted from the published packagev3.22.0 · 3mo 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.

lookup_userNo description published

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

fetch_pageNo description published

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

fetch_weatherNo description published

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

get_userNo description published

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

check_codeNo description published

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

check_projectNo description published

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

get_security_docsNo description published

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

check_dependenciesNo description published

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

scan_directoryNo description published

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

scan_dependenciesNo description published

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

scan_hallucinated_packagesNo description published

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

scan_secretsNo description published

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

scan_stagedNo description published

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

compliance_reportNo description published

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

export_sarifNo description published

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

check_package_healthNo description published

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

fix_codeNo description published

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

secure_thisNo description published

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

audit_configNo description published

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

generate_policyNo description published

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

review_prNo description published

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

scan_secrets_historyNo description published

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

policy_checkNo description published

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

analyze_dataflowNo description published

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

analyze_cross_file_dataflowNo description published

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

check_commandprivilegedNo description published

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

scan_config_changeNo description published

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

repo_security_postureNo description published

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

explain_remediationNo description published

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

scan_fileNo description published

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

scan_changed_filesNo description published

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

security_statsNo description published

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

audit_mcp_configNo description published

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

scan_host_configNo description published

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

guardvibe_doctorNo description published

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

verify_fixNo description published

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

security_workflowNo description published

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

auth_coverageNo description published

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

deep_scanNo description published

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

full_auditNo description published

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

0 of 40 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

Security infrastructure your AI can't be — deterministic, current past your model's training cutoff, whole-repo-aware, author-independent. Security MCP for vibe coding. 530 rules, 39 tools, CLI + doctor. Prompt-level shift-left security (secure_prompt — e

Keywords
mcpsecurityvibe-codingowaspvulnerabilityclaudecursorgeminicodexwindsurfai-securitycode-auditnextjssupabasestripeclerkprismadrizzlevercelsastsecret-detectionwebhook-securitycomplianceresendupstashpineconeposthogcloudflareopenaidockerterraformgithub-actionspre-commitsarifcvereact-nativeexpofirebasemcp-serverprompt-injectionsupply-chaintrpchonographqlconvextursolibsqluploadthingoauthcspbolamass-assignmentauto-fix
Alternatives
Comparing tool surfaces…

Tools exposed

40 tools · 1 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.

Topics

Related in analytics & dashboards