Taskbounty Check vs Jamjet Policy

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
Taskbounty Check
eliottreich
🔒 Security
Jamjet Policy
jamjet-labs
🔒 Security
SummaryLocal-only GitHub Actions and CI maintenance scanner for AI-built apps. Exposes scanrepo, explainfinding, and generatefixplan to MCP clients; reads only allowlisted workflow and update configuration, modifies nothing, makes no outbound requests by default, and has zero runtime dependencies. Run with npx -y taskbounty-check@0.1.6 mcp.MCP stdio interceptor (@jamjet/mcp-shim) that applies one YAML policy file (block / requireapproval / audit / budget cap) to tools/call requests before they reach the real MCP server. The same policy also runs in Claude Code PreToolUse hooks (@jamjet/claude-code-hook), OpenAI Agents SDK guardrails (@jamjet/openai-guardrail), and JamJet's Python/TS SDKs — jamjet audit show tails every decision across every adapter from /.jamjet/audit/.
Quality signal24/100 (Emerging)25/100 (Emerging)
Install pathnpx · highuvx · low
Engagement 0 0 0 2 0 0 0 2
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Taskbounty CheckView Jamjet Policy
More alternatives to Taskbounty CheckMore alternatives to Jamjet PolicySecurity category

Other servers like Taskbounty Check