Fix GuardBee AI Security Engineer findings in your repo with your coding agent, then verify
Security-engineer is an MCP integration. Fix GuardBee AI Security Engineer findings in your repo with your coding agent, then verify.
The published npm package is @guardbee/mcp-security-engineer, version 0.2.0. Its declared MCP transport is stdio.
The package declares GUARDBEE_API_KEY (required): GuardBee API key with remediations.read and remediations.write scopes.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| GUARDBEE_API_KEY | GuardBee API key with remediations.read and remediations.write scopes | Yes |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
`chuk-mcp` gives you a clean, typed, transport-agnostic implementation for both **MCP clients and servers**. It focuses on the protocol surface
Whistle MCP Server is a Whistle proxy management tool based on the Model Context Protocol (MCP), allowing AI assistants to directly operate and
MCP Server for downloading and parsing Substack posts
MCP server for untun integration