Skip to content
LSAI + xmp4 logo

LSAI + xmp4 MCP server

Which MCP servers are LSAI + xmp4's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-23

← Back to LSAI + xmp4

Whose server it is
  • Registry nameai.example4/xmp4verified in the MCP registry

The registry name sits under example4.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-23
  • Stateanswerschecked 2026-10-23
  • Tools16
  • Server calls itselfxmp4
  • Server version1.2.7
  • Protocol version2025-03-26

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 611 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: find every caller of a function in your codebase; trace a library call into its implementation source.
  • Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-23
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • What an agent can do with it2 of 2 use cases
  • Use1 GitHub stars
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer549 ms
  • Space in an agent's context≈ 4,747 tokensthe definitions of all its tools (16), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 16 of 16

What an agent can do with it

  • can do · find every caller of a function in your codebase
  • not sure · check which tests break before changing a method
  • can do · trace a library call into its implementation source

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers16 tools · read 2026-10-23
  • xmp4_callees

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

  • xmp4_callers

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

  • xmp4_deps

    List external dependencies of a project.

  • xmp4_grep

    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…

  • xmp4_guide

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

  • xmp4_hierarchy

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

  • xmp4_info

    Get detailed information about a symbol in a project.

  • xmp4_outline

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

  • xmp4_projects

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

  • xmp4_search

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

  • xmp4_server

    Get server information, version, and capabilities

  • xmp4_source

    Extract source code for a symbol in a project.

  • xmp4_symbol_at

    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…

  • xmp4_tests_for

    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…

  • xmp4_usages

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

  • xmp4_view

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "xmp4": {
      "type": "http",
      "url": "https://mcp.example4.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http example4 https://mcp.example4.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.example4.ai/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.