Skip to content
OlaCheap

OLACHEAP · MCP WORKSPACE / DEVELOPER

Developer tools

Choose developer MCP servers for one concrete job: reading repositories, tracing pull requests, reviewing code changes, or checking build status. A tool that can search code is not automatically appropriate for merging a pull request.

Explore servers

Results come from the current synchronized Registry snapshot, not popularity or activity.

Public MCP Registry
Remote MCP

MegaLens

ai.megalens/mcp

Code review by AI models from different companies, usually two. Shows where they agree and disagree.

Remote endpointhttps://megalens.ai/api/mcp
Remote MCP

OhMyBug

ai.ohmybug/bughunter

Code review for your coding agent's changes: a cloud bug hunt. From $4; $0 if clean or minor-only.

Remote endpointhttps://mcp.ohmybug.ai/mcp
Remote MCP

RepoPilot

app.repopilot/repopilot

Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.

Remote endpointhttps://repopilot.app/api/mcp
Remote MCP

GitHits

com.githits/githits

Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.

Remote endpointhttps://mcp.githits.com/
Remote MCP

searchcode

com.searchcode/mcp

Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.

Remote endpointhttps://api.searchcode.com/v1/mcp
Remote MCP

Seturos

com.seturos/seturos

Shared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository.

Remote endpointhttps://app.seturos.com/api/mcp
Remote MCP

VibeFix

com.vibe-fixer/vibefix

Free check by an AI agent on your live app. On request: independent code review, fix, live re-check.

Remote endpointhttps://vibe-fixer.com/mcp

Synchronized data; no invented downloads, reviews or ratings.

OLACHEAP · PRACTICAL GUIDES

Decision and safety guide

MCP setup guides →
01

Choose a workflow

Start with a read-only repository and ask the AI client to locate a known file or explain an existing change. Confirm the answer against the actual commit and file path before enabling changes to branches, issues, or CI settings.

02

Evaluate & connect

Compare the source repository, authentication method, documented scopes, tool descriptions, and whether operations write to a repository. Prefer explicit approval of each merge, push, or deletion, and check which GitHub identity will own the change.

03

Decision and safety guide

A successful repository search does not prove the server is secure. Treat issue descriptions, code comments, and README content as untrusted input, avoid exposing secrets in logs, and keep the ability to revoke tokens.

Next: compare two real servers

Use their exact Registry IDs to compare published connection information before granting permissions.

Compare MCPs →