T32 Lsp MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 30 installs a week from npm. Last commit 18 Sep 2026.
TRACE32 CMM LSP via MCP — parse, diagnostics, completions, hover, symbols
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/download-binary.js
этот файл ставится пользователю, но в репозитории его нет
const child = spawn(childCmd, childArgs, {
return (long long)system(cmd);
const dir = path.join(corpusDir, sample);
self.proc = subprocess.Popen(
var attributes: posix_spawnattr_t?
appEl.innerHTML = event.payload;
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.
run: sudo apt-get update && sudo apt-get install -y ${{ matrix.pkg }}
--privileged \
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 t32-lsp-mcp-server -- npx -y @simple-lang/t32-lsp-mcp-server
{
"mcpServers": {
"t32-lsp-mcp-server": {
"args": [
"-y",
"@simple-lang/t32-lsp-mcp-server"
],
"command": "npx"
}
}
}
[mcp_servers.t32-lsp-mcp-server]
command = "npx"
args = ["-y", "@simple-lang/t32-lsp-mcp-server"]
{
"mcpServers": {
"t32-lsp-mcp-server": {
"args": [
"-y",
"@simple-lang/t32-lsp-mcp-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"t32-lsp-mcp-server": {
"args": [
"-y",
"@simple-lang/t32-lsp-mcp-server"
],
"command": "npx"
}
}
}
SpiderIQ Gate: SpiderGate LLM gateway (completions, models, usage, traces)
Monitor MCP, CI, and HTTP targets with health history, TLS expiry, assertions, and diagnostics
Host, Docker, Compose, SSH, logs, ZFS, and file operations over MCP and CLI.
Server operations MCP: HTTP health checks, log analysis, deploy dry-runs, mail diagnostics.
Lint Verilog and SystemVerilog files and projects with structured diagnostics.
Network diagnostics — ping, traceroute, DNS, port scanning, and connectivity testing.
Traces which neurons and attention heads drive a language model's output via MCP tools.
Network diagnostics from 6 global regions. SSL, DNS, ping, whois, traceroute, port scan, latency.
Answers built from our own checks of this server.