MCP.Market

xmp4 — Semantic code knowledge for your stack MCP server

online · 100% uptime
by example4.ai·ai.example4/xmp4·v1.2.6
No reviews yet

OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.

A87/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A87/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed xmp4 — Semantic code knowledge for your stack yet.

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

xmp4 — Semantic code knowledge for your stack tools (16)

write = sends, deletes, buys or posts
  • xmp4_calleesFree

    Find direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.

  • xmp4_callersFree

    Find direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.

  • xmp4_depsFree

    List external dependencies of a project.

  • xmp4_grepFree

    Server-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).

  • xmp4_guideFree

    Usage guide for xmp4 tools — read this first to learn the correct workflow

  • xmp4_hierarchyFree

    Get type hierarchy (base, interfaces, derived) for a symbol in a project.

  • xmp4_infoFree

    Get detailed information about a symbol in a project.

  • xmp4_outlineFree

    Get outline (all symbols) for a file in a project.

  • xmp4_projectsFree

    Search and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.

  • xmp4_searchFree

    Search symbols in a project. Use xmp4_projects first to find the project identifier.

  • xmp4_serverFree

    Get server information, version, and capabilities

  • xmp4_sourceFree

    Extract source code for a symbol in a project.

  • xmp4_symbol_atFree

    LSP-style position→symbol lookup. Given (file_path, line, column) returns the symbol whose occurrence covers that cursor position. line is 1-based; column is 0-based. Use after xmp4_outline/xmp4_view when you know coordinates and want the canonical symbol.

  • xmp4_tests_forFree

    Find direct tests that exercise a given symbol (direct callers filtered to test-file candidates per language pattern: CSharp/Java/PHP: *Test(s).<ext>; Python: test_*.py / *_test.py; TypeScript/JavaScript: *.spec/test.{ts,js}; Rust: *_tests.rs / tests/; etc.).

  • xmp4_usagesFree

    Find all usages/references of a symbol in a project.

  • xmp4_viewFree

    Read a raw file excerpt from an indexed project by line range. Use after xmp4_search/xmp4_outline locates the region of interest, or to expand a truncated xmp4_source snippet. Hard cap of 500 lines per call.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1761ms20/20
  • Tool poisoning16 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 67 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Overall 87/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How xmp4 — Semantic code knowledge for your stack compares

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

Safety score
87/100
higher than 73% of 48,255 servers
Tools
16
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
644 ms
faster than 22% of 30,031 servers

What its tools let an agent do: 16 read

Install xmp4 — Semantic code knowledge for your stack in Claude Code, Cursor or VS Code

claude mcp add --transport http xmp4 https://mcp.example4.ai/mcp
Add to Cursor

What the publisher says

From the xmp4 — Semantic code knowledge for your stack repository's README, as published. We do not edit it. Read it on GitHub

xmp4

Stop grepping library source.

Your AI gets the compiler's view of 856 OSS libraries via MCP.

Real callers. Real source. Real hierarchy. In 3 tool calls.

→ Landing page · → Benchmark whitepaper · → Connect in 30 seconds

The 30-second pitch

Your AI coding agent is burning tokens grepping OSS libraries it will barely use. xmp4 is a hosted MCP server that pre-indexes 856 popular open-source libraries with SCIP — the semantic code format Sourcegraph uses — and serves them through 17 tools. No clone. No grep. No false positives.

ASK: "Who calls Flask.wsgi_app in the flask repo and what does it do?"

with grep + local clone:
  git clone flask/flask          ~40 MB,   ~2 min
  grep -rn "wsgi_app" .          200+ matches, mostly noise
  cat src/flask/app.py | sed ... read 1000+ lines to find the body
  filter false positives         model spends tokens deciding what's real
  ──────────────────────────────────────
  total:                         ~15,000 tokens + disk + wall time

with xmp4:
  xmp4_info(symbol_name="Flask",    file_path="src/flask/app.py")         → signature,  20 tok
  xmp4_source(symbol_name="wsgi_app", file_path="src/flask/app.py")       → body,      180 tok
  xmp4_callers(symbol_name="wsgi_app", file_path="src/flask/app.py")      → 1 caller,   50 tok
  ──────────────────────────────────────
  total:                                                                    ~250 tokens

xmp4 is 60× cheaper here — and every result is SCIP-resolved, not text-matched.

The measured numbers (4 big OSS libs · reproducible)

Same realistic question on spring-boot · tokio · django · efcore: "give me the signature, body, and real callers of X."

GitMCP and Context7 look cheaper per call because they return less. To reach the same answer, GitMCP balloons to 42× more tokens — and still can't produce the semantic caller list. Context7 can't at any cost. Full whitepaper with Python harness →

Connect in 30 seconds

// Claude Code / Cursor / Claude Desktop — project `.mcp.json` or client config
{
  "mcpServers": {
    "xmp4": {
      "type": "http",
      "url": "https://mcp.example4.ai/mcp"
    }
  }
}

(The ready-to-paste config also lives at .mcp.json in this repo.)

Teach Claude how to use xmp4 (optional but recommended)

Install the xmp4 skill once per version — Claude will pick the cheapest tool path automatically (tests_for + view over grep):

# Claude Code
mkdir -p ~/.claude/skills/xmp4 && \
  curl -sfL https://example4.ai/xmp4-skill.md -o ~/.claude/skills/xmp4/SKILL.md

Shortened. The full README is on GitHub.

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

xmp4 — Semantic code knowledge for your stack: common questions

Is xmp4 — Semantic code knowledge for your stack MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the xmp4 — Semantic code knowledge for your stack safety report
How do I install xmp4 — Semantic code knowledge for your stack?
It runs remotely at mcp.example4.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does xmp4 — Semantic code knowledge for your stack need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is xmp4 — Semantic code knowledge for your stack maintained?
The last commit was 105 days ago (2026-07-22). The latest release is v1.2.6.
Is xmp4 — Semantic code knowledge for your stack up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does xmp4 — Semantic code knowledge for your stack compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); tools 16 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.