Archived listing / no verified MCP endpoint/Development

VibeDefend listing

No MCP endpoint is published. This listing is retained for reference.

VibeDefend is a CLI installer and guardrail for AI coding agents. It gives an agent security and business rules, scans each diff for SAST, SCA, secrets and IaC while coding, and blocks dangerous commands. Install with npx -y @cybedefend/vibedefend@latest install, choose the EU or US region, sign in through the browser and tick Claude Code. The provider documents a CLI hook, not a hosted MCP server, endpoint or OAuth flow, so this page is a tool reference rather than a hosted-MCP listing.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Official docs
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Developers using Claude Code who want a security guardrail on each diff and dangerous-command blocking.

  • Install the VibeDefend CLI and hook it into Claude Code.
  • Scan each diff for SAST, SCA, secrets and IaC issues.
  • Block dangerous commands during coding.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

VibeDefend documentationhttps://www.cybedefend.com/en/vibedefend/agents/claude-codeGitHub repositoryhttps://github.com/CybeDefend/vibedefend-xp