RRepoGEO

REPOGEO REPORT · LITE

modelcontextprotocol/inspector

Default branch main · commit f18775a1 · scanned 5/21/2026, 8:01:57 AM

GitHub: 9,825 stars · 1,318 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface modelcontextprotocol/inspector, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • hightopics#1
    Add relevant topics to improve categorization

    Why:

    COPY-PASTE FIX
    visual-testing, protocol-debugging, server-debugging, web-ui, developer-tools, model-context-protocol, observability, testing-tools, react, nodejs, docker
  • highreadme#2
    Reposition README opening to clarify its unique purpose and category

    Why:

    CURRENT
    # MCP Inspector

The MCP inspector is a developer tool for testing and debugging MCP servers.
    COPY-PASTE FIX
    # MCP Inspector: Interactive Web UI for Model Context Protocol Debugging

The MCP Inspector is an interactive, web-based developer tool designed specifically for visually testing and debugging Model Context Protocol (MCP) server implementations. It provides a dedicated UI to inspect message flows, understand server behavior, and streamline development, offering a specialized alternative to generic network tools or data visualization platforms.
  • mediumreadme#3
    Add a section to README clarifying the project's license

    Why:

    COPY-PASTE FIX
    ## License

This project's licensing terms are defined in the [LICENSE file](LICENSE) within this repository. Please refer to that file for complete details on usage and distribution.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface modelcontextprotocol/inspector
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Wireshark
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Wireshark · recommended 1×
  2. tcpdump · recommended 1×
  3. Postman · recommended 1×
  4. Insomnia · recommended 1×
  5. cURL · recommended 1×
  • CATEGORY QUERY
    What tools are available for interactively debugging server-side protocol implementations?
    you: not recommended
    AI recommended (in order):
    1. Wireshark
    2. tcpdump
    3. Postman
    4. Insomnia
    5. cURL
    6. Netcat
    7. Telnet

    AI recommended 7 alternatives but never named modelcontextprotocol/inspector. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Need a web UI for visually inspecting and testing server data flows.
    you: not recommended
    AI recommended (in order):
    1. Grafana (grafana/grafana)
    2. Kibana (elastic/kibana)
    3. Apache Superset (apache/superset)
    4. Tableau
    5. Looker

    AI recommended 5 alternatives but never named modelcontextprotocol/inspector. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of modelcontextprotocol/inspector?
    pass
    AI named modelcontextprotocol/inspector explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts modelcontextprotocol/inspector in production, what risks or prerequisites should they evaluate first?
    pass
    AI named modelcontextprotocol/inspector explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo modelcontextprotocol/inspector solve, and who is the primary audience?
    pass
    AI named modelcontextprotocol/inspector explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of modelcontextprotocol/inspector. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/modelcontextprotocol/inspector.svg)](https://repogeo.com/en/r/modelcontextprotocol/inspector)
HTML
<a href="https://repogeo.com/en/r/modelcontextprotocol/inspector"><img src="https://repogeo.com/badge/modelcontextprotocol/inspector.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

modelcontextprotocol/inspector — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite