Home / MCP registry index / ai.example4/xmp4
xmp4 — Semantic code knowledge for your stack
ai.example4/xmp4 in the official MCP registry.
Endpoint https://mcp.example4.ai/mcp. Source: github.com/0ics-srls/lsai-xmp4.public.
The registry describes it as: OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.
We read its 16 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
xmp4_callees xmp4_callers xmp4_deps xmp4_grep xmp4_guide xmp4_hierarchy xmp4_info xmp4_outline xmp4_projects xmp4_search xmp4_server xmp4_source xmp4_symbol_at xmp4_tests_for xmp4_usages xmp4_view
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-example4-xmp4)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.