Decapodkernel MCP vs Semgrep
A side-by-side look at the Decapodkernel MCP and Semgrep MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Decapodkernel MCP for security work over a hosted endpoint; choose Semgrep for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Decapodkernel MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
create_intent_contract, check_agent_boundary, record_completion_proof.
Choose Semgrep when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 48/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 17,186 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Decapodkernel MCP | View Semgrep |
Tools & capabilities
Decapodkernel MCP tools 4
create_intent_contractcheck_agent_boundaryrecord_completion_proofexport_intent_receipt
Semgrep tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Decapodkernel MCP
{
"mcpServers": {
"decapodkernel-mcp": {
"url": "https://decapodkernel.clauxel.com/mcp"
}
}
}
Semgrep
{
"mcpServers": {
"semgrep-semgrep": {
"command": "uvx",
"args": [
"semgrep"
]
}
}
}
Frequently asked questions
Decapodkernel MCP is categorized under Security and uses a remote HTTP/SSE transport. Semgrep belongs to Security and uses a local stdio subprocess. Pick Decapodkernel MCP for security work and Semgrep for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Decapodkernel MCP has no declared pricing — check the project's own site. Semgrep is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add decapodkernel-mcp and semgrep-semgrep as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Decapodkernel MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Semgrep has 48/100 (Fair) with 1 views, 0 installs and 17,186 GitHub stars.