Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 0
- 4 4
- 3 11
- 2 3
- 1 0
Trust in production
- Trust it - 17%
- With caveats - 50%
- Wouldn't - 33%
50% would recommend this server
How reviewers scored it
- Setup & docs 3.2
- Auth experience 3.2
- Reliability 3.1
- Maintainer responsiveness 3.7
Why it got a C
This is not the same thing as semgrep-mcp. That listing grades the open-source server built into the Semgrep CLI, which scans on your machine. Guardian is the Claude Code plugin: an MCP server plus hooks, both run by a prebuilt Guardian binary that is closed source and downloaded from semgrep.dev (the README says it is checked against a signed manifest before it runs). Biggest deduction: transport scores 6 of 20 because the hooks run on every file write in every project and send the written files, and their previous contents, plus lockfiles and manifests, to scanner.semgrep.ai; that part cannot be switched off without removing the plugin. Telemetry to telemetry.semgrep.dev (no file contents) can be turned off with telemetry: false in ~/.semgrep/guardian.yml or SEMGREP_SEND_METRICS=off, and auto-update with auto_update: false. Auth needs a Semgrep login; scopes are not documented, so 18 of 30. The repo (Semgrep's own org, no licence file) holds the plugin wrapper and changelog, not the binary source, so this grade rests on the README and Semgrep docs. Maintenance is active (commit 2026-11-05) but has no GitHub releases. No advisories on record. Tools named in the changelog include status, whoami, version and update. Only use it on code you are happy to send to Semgrep.
How to connect
In Claude Code: /plugin, Discover, search Semgrep, Install; then /reload-plugins and ask Claude to log in to SemgrepIs Semgrep Guardian safe?
Is Semgrep Guardian safe to use?
Semgrep Guardian grades C (usable with care). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does Semgrep Guardian have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Semgrep Guardian support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
Embed this badge
[](https://trustedmcp.io/servers/semgrep-guardian)<a href="https://trustedmcp.io/servers/semgrep-guardian"><img src="https://trustedmcp.io/badge/semgrep-guardian.svg" alt="TrustedMCP grade C" height="80"></a>Community reviews
Recommended it to two teams already
Been running this for about a month now. Narrowing the scopes took ten minutes and made me much happier running it. Easy recommendation.
Used for Keeping project tickets in sync with code changes
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
No complaints after a month
Tried it on a side project first, then rolled it out at work. Local stdio process, easy to start and stop from the client. The scope options are worth reading carefully, the defaults are broader than I wanted.
Used for Code review summaries for pull requests
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Handy for dev, careful in prod
It does the job, but it took some tweaking. Setting up the token took longer than the server itself, but the scoping options are decent. Filed an issue and got a reply within two days. Local stdio process, easy to start and stop from the client. Worth it, just do not skip the hardening steps.
Used for Internal developer assistant
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Our team uses it every day
Clear tool names, sensible outputs, very few surprises. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Good choice if you need Semgrep Guardian in your agent.
Used for Letting a coding agent open and triage issues
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Capable but needs guardrails
Mostly reliable, with the odd timeout. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Keep permissions tight and it is a good tool.
Used for Scripting routine maintenance tasks
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Solid and well behaved
Of the Semgrep Guardian integrations I tried, this one is the most predictable. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Works, just lock it down
Works well enough for what I need. You create a token and pass it in. Scope it narrowly, that is the main thing.
Used for Generating boilerplate from existing patterns
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Decent, not set-and-forget
Good for experimenting, still deciding about production. I would prefer to read the code, but the hosted service has been dependable. Setting up the token took longer than the server itself, but the scoping options are decent.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Good, but read the permissions first
Mostly reliable, with the odd timeout. The scope options are worth reading carefully, the defaults are broader than I wanted.
Used for Scripting routine maintenance tasks
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
OK for read-only work
Useful tool, though I would not hand it to a junior unsupervised. Setting up the token took longer than the server itself, but the scoping options are decent. Local stdio process, easy to start and stop from the client. Fine in production if you sandbox it.
Used for Internal developer assistant
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Went back to calling the API directly
Ran into problems pretty quickly. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Filed an issue and got a reply within two days. For anything real I would look elsewhere.
Used for Code review summaries for pull requests
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Mixed feelings after two weeks
Took longer to configure than I expected. Narrowing the scopes took ten minutes and made me much happier running it. You can tell it is actively maintained, the rough edges keep getting fixed. I will check back in a few releases.
Used for Debugging sessions in Cursor
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Does the job, docs could be better
I like it, with reservations. You create a token and pass it in. Scope it narrowly, that is the main thing. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out. I would use it in prod, but only with a human approving writes.
Used for Looking up Semgrep Guardian data without leaving the editor
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Useful, with a few rough edges
Took longer to configure than I expected. I would prefer to read the code, but the hosted service has been dependable. Auth is there, but the credential still lives in my local config, so I keep that file locked down. Keeping it to local experiments for now.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Promising, a bit raw
Some tools are great, a couple feel half finished. You create a token and pass it in. Scope it narrowly, that is the main thing.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Struggled to get it stable
I wanted to like this one. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out.
Used for Debugging sessions in Cursor
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Not ready for anything that matters
Not what I expected from the description. Setting up the token took longer than the server itself, but the scoping options are decent. Being closed source, I cannot audit it, but the vendor has been responsive.
Used for Looking up Semgrep Guardian data without leaving the editor
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Fine once configured properly
Works well enough for what I need. Auth is there, but the credential still lives in my local config, so I keep that file locked down. The scope options are worth reading carefully, the defaults are broader than I wanted. Recommended, with sensible guardrails.
Used for CI failure investigation
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.