MCP.Market

Myopic MCP server

by SurajKGoyal·io.github.SurajKGoyal/myopic·v0.1.11
No reviews yet

Code-review MCP: review a GitLab MR or GitHub PR against the whole codebase, not just the diff.

A88/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

0 stars42 downloads/wk

Reviews

Write one

Nobody has reviewed Myopic yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Myopic tools (12, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • code_search

    Hybrid semantic + full-text search over an indexed local repository.

  • dependency_impact

    Find everywhere a symbol is used in a checked-out repo (the blast radius).

  • index_repo

    Build or incrementally refresh a semantic search index for a local repository.

  • index_status

    Report whether a repo's semantic index is fresh, stale, or absent.

  • mr_changed_files

    List the files changed in a merge request with stats — no diff content.

  • mr_diff_lines

    Fetch a merge request's diff as structured, line-numbered hunks.

  • mr_diff_sections

    Fetch a merge request's diff grouped by enclosing function/class, not raw hunks.

  • mr_post_commentswrite action

    Post inline review comments to a merge/pull request. WRITE — this mutates the review.

  • mr_review_context

    Graph-first review context: dependency impact per changed symbol, plus optional semantic enrichment.

  • mr_review_status

    Get a merge request's review status: metadata + discussions + resolution.

  • mr_verify_review

    Check whether each review thread was addressed by nearby diff changes.

  • trace_call_chain

    Trace a function's callers and callees across a checked-out repo (AST).

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan34 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 41 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Myopic compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 1,119 Developer tools servers
Tools
12
the typical Developer tools server has 7
Tools that change things
8%
typical: 5%. Fewer write tools means less an agent can break
Downloads a week
42
more than 30% of 442 Developer tools servers with a package

What its tools let an agent do: 11 read · 1 change

Install Myopic in Claude Code, Cursor or VS Code

claude mcp add myopic -- uvx myopic
Add to Cursor

What the publisher says

From the Myopic repository's README, as published. We do not edit it. Read it on GitHub

myopic

The code-review MCP with the most ironic name in the registry. It's anything but nearsighted — it reviews your merge request against the whole codebase, not just the diff in front of it.

Building in public. Reviews **GitLab merge requests and GitHub pull

requests** — pass either URL. Reads the change, reviews it against the whole

codebase, and can post the review back as inline comments. Issues and PRs welcome.

Why

The bugs that matter rarely live in the diff. They live in what it doesn't show: the caller three files away that now breaks, the convention every sibling file follows that this one quietly drops, the helper that already exists so this new one is a duplicate. A reviewer that only reads the patch is myopic.

myopic is an open-source MCP server that gives the AI client you already use (Claude, Cursor, …) the structured context to review like someone who knows the codebase. It runs on your machine — your code never leaves it, there's no per-PR bill, and the review happens in your own agent with your own standards:

function/class, token-safe on any MR size (a 10,000-line diff never overflows the context window).

  • Read the change precisely — the diff as line-numbered hunks or grouped by

radius), the caller/callee graph, and — optionally — semantically similar code so you catch broken conventions and duplication.

  • Review it against the whole codebase — who calls the changed code (blast

It pairs with amnesic, my MCP server that gives AI persistent memory of SQL databases.

Tools

Everything below works today unless marked planned.

Read the merge request (token-safe by construction):

On a large MR, the diff tools return a bounded page and list the rest under omittedfiles / truncated instead of failing; lockfiles, generated code, and binaries are listed but not expanded. Fetch the rest with filesfilter.

Review against the whole codebase (point at a local clone):

Semantic layer (built in — needs Ollama) — indexrepo, codesearch, and the semantic half of mrreviewcontext. See below.

Close the loop — verify, and (on request) comment:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Myopic: common questions

Is Myopic MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Myopic safety report
How do I install Myopic?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Myopic need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Myopic maintained?
The last commit was 61 days ago (2026-09-05). The latest release is v0.1.11.
What can I use instead of Myopic?
Servers from other publishers that do the same job: Grasp — Code Architecture & Dependency Analysis MCP server, Gk CLI MCP server and diffctx MCP server.
How does Myopic compare with other Developer tools MCP servers?
safety score 88/100 (higher than 75% of 1,119 Developer tools servers); tools 12 (the typical Developer tools server has 7); tools that change things 8% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Myopic

Same job from other publishers: the closest match first, then the best rated.

  • Grasp — Code Architecture & Dependency Analysis
    Codebase analysis: dependency graphs, security scanning, and refactor plans for GitHub and GitLab.
    C
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • diffctx
    Selects the minimum code an LLM needs to review a git diff
    A
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A