A
licenseNot graded
qualityD
maintenanceEnables integration of Semgrep in development environments via the MCP protocol, supporting static code analysis, rule management, and scan result operations.
2
MIT
ocr-mcp-server
by Gwrominl
Related Servers
Alternatives to ocr-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to run security and code review on pull requests and diffs, exposing review_pr and review_diff capabilities with local-first analyzers and LLM explanations.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables code agents to run risk-based Jev quality reviews on focused diffs through a read-only MCP tool, returning structured scores and weakness hints without modifying code.MIT
@cognium/mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Cursor, Claude Desktop, and Claude Code to run deterministic static-analysis tools for scanning projects, listing entry points and reachable sinks, tracing taint paths, explaining findings, and checking sanitizers without API keys or network access.MIT- AlicenseNot gradedqualityAmaintenanceMCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.25 npm2MIT
- AlicenseNot gradedqualityDmaintenanceSecurity scanning MCP server. Semgrep integration, SARIF parsing, baseline diffing, framework-aware ruleset selection, and automated finding triage.7 npm1MIT
TDQS
A4.4/5.0
Scored across 3 tools
Disambiguation5/5
All three tools have clearly distinct purposes: one scans an entire repository, one scans only changed lines, and one reports tooling status. The descriptions explicitly clarify when to prefer scan_diff over scan, eliminating meaningful ambiguity.
Naming Consistency5/5
Every tool follows the same snake_case `semgrep_*` prefix pattern, making the family instantly recognizable. The verb-like suffixes `_scan`, `_scan_diff`, and `_status` are consistent and predictable.
Tool Count5/5
Three tools is well-scoped for a focused analysis server: two scanning modes plus a status endpoint cover the core workflow without redundancy. Each tool earns its place; adding more would likely dilute the server's purpose.
Completeness5/5
The tool surface covers full-repo scanning, PR/diff scanning, and availability reporting, with no obvious dead ends. The status tool fills the operational gap for diagnosing unavailable scans, making the workflow self-contained.
Maintenance
ActivityMaintained
ResponsivenessNo issues