Sem runs on your own machine — the client starts it, so there is no endpoint to ping. 6 824 installs a week from npm. Last commit 13 Sep 2026.
Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents
We read the source, 19 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
postinstall: node ./scripts/postinstall.mjs
out = subprocess.run(cmd, cwd=cwd, capture_output=True, text=True, timeout=8).stdout
execFileSync(process.platform === 'win32' ? 'where' : 'which', [cmd], {
return vm.compileFunction(src, [], {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
sudo apt-get update
sudo apt-get install -y ${{ matrix.cross_package }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add sem -- npx -y @ataraxy-labs/sem
{
"mcpServers": {
"sem": {
"args": [
"-y",
"@ataraxy-labs/sem"
],
"command": "npx"
}
}
}
[mcp_servers.sem]
command = "npx"
args = ["-y", "@ataraxy-labs/sem"]
{
"mcpServers": {
"sem": {
"args": [
"-y",
"@ataraxy-labs/sem"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"sem": {
"args": [
"-y",
"@ataraxy-labs/sem"
],
"command": "npx"
}
}
}
Semantic code intelligence — call graphs, dependencies, impact analysis, and test coverage.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Code intelligence MCP server — impact analysis, semantic search, dependency graphs
Semantic code search and analysis from CodeAlive for AI assistants and agents.
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Local-first code context, impact analysis, and merge-readiness verdicts for AI agents.
Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents.
Python code intelligence for coding agents: call paths, control flow, and change impact.
Answers built from our own checks of this server.