pulsemcp verified Safe content atomic mcp-remote

JMX Management

This JMX MCP server by itz4blitz bridges Java Management Extensions (JMX) with AI assistants, enabling natural language monitoring and management of Java applications through their exposed MBeans. The implementation provides comprehensive JMX operations as MCP tools (getAttribute, setAttribute, invoke operations) and exposes JMX attributes as dynamic resources, supporting both local JVM connections via the Attach API and remote JMX connections with authentication. Key differentiators include multi-connection support for managing multiple Java applications simultaneously, automatic MBean discovery with configurable filtering patterns, built-in security validation to prevent dangerous operations, and specialized configuration profiles for different deployment scenarios (STDIO for Claude Desktop, Docker for containerized environments, and production-ready remote monitoring setups), making it valuable for DevOps teams and Java developers who need AI-powered application monitoring, performance analysis, and operational management of JVM-based systems.

Cognium trust score

72%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/itz4blitz/jmx-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve JMX Management from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"