Other · Local MCP server
threadmine.dev
Analyze JVM thread dumps with ThreadMine: deadlocks, CPU spikes, pool exhaustion, health score.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.threadmine/mcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-14
- Updated
- 2026-07-14
- Publisher
- dev.threadmine
- Namespace
- Namespace verified by the MCP Registry via the domain threadmine.dev · how
- Repository
- github.com/maschiojv/threadmine-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @threadmine/mcp | 0.1.0 | stdio |
How to connect threadmine.dev
threadmine.dev runs locally from a Node.js package published to the npm registry: @threadmine/mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @threadmine/mcp@0.1.0. It reads these environment variables: THREADMINE_API_KEY (required, secret) and THREADMINE_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@threadmine/mcp@0.1.0"
],
"env": {
"THREADMINE_API_KEY": "<secret>",
"THREADMINE_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Threadkeep - Agent CheckpointsAgent checkpoints. Resume after context resets and handoffs with retry-safe, versioned saves. | Remote · HTTPLive check: ✓ handshake |
| Threadline MCPAgent-to-agent messaging relay. Discover agents, send messages, and receive replies. Zero-config. | Local · stdio |
| Threadmap MCPConversation drift visualization for Claude. Color-coded inflection points and one-click forking. | Local · stdio |
| ThreadminderPersistent context for Claude. Your AI always knows your projects and next actions across sessions. | Remote · HTTPLive check: sign-in required |
| ThreatclusterLive threat intel for agents: incidents, actors, CVEs with KEV/EPSS, ransomware leak-site victims. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ThreatfoxThreatFox MCP - abuse.ch indicator-of-compromise feed (free, key required) | Remote · HTTPLive check: ✓ handshake |
| ThreatLockerMCP server for ThreatLocker - zero-trust endpoint protection, allowlisting, and policies. | Local · stdio |
| ThreatLockerMCP server for ThreatLocker - zero-trust endpoint protection, allowlisting, and policies. | Local · stdio |