PerformanceMonitor — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of github.com/erikdarlingdata/PerformanceMonitor: Does the tool surface now include configuration writes or powerful SQL beyond informational monitoring?

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Troubleshoot database performance

What we know

PerformanceMonitor includes an optional local Streamable HTTP MCP service for SQL Server monitoring.

Maintenance / activity evidence

PerformanceMonitor repository recorded commit c5fbd52 and v3.5.0 release work on 2026-08-19.

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Built-in MCP exposes monitoring store, does not execute AI-generated SQL on production DB (per author); DB monitoring permissions still apply. Writes: Modify monitoring configuration or monitored connections where settings tools are enabled.
Authentication not yet verified.
Mostly read-only diagnostics against monitored DB, but configuration-changing tools can edit alerts, views and monitored server settings.

Mostly read-only diagnostics against monitored DB, but configuration-changing tools can edit alerts, views and monitored server settings.
Advisory/security review not completed; no safety badge.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

517 repository stars

Stars observed Oct 9, 2026.

Repository total for erikdarlingdata/PerformanceMonitor.

All limitations / Review context

Does the tool surface now include configuration writes or powerful SQL beyond informational monitoring?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

Mostly read-only diagnostics against monitored DB, but configuration-changing tools can edit alerts, views and monitored server settings.
Advisory/security review not completed; no safety badge.
Built-in MCP exposes monitoring store, does not execute AI-generated SQL on production DB (per author); DB monitoring permissions still apply.
Reviewed write actions: Modify monitoring configuration or monitored connections where settings tools are enabled
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Can access production database performance contents and modify local monitoring configuration; not certified read-only.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
verified install or launch command
exact authentication contract
first-party data processing and retention
transport verification
data retention and permission scope
Do not present as a standalone npm server; embedded mode requires app installation and MCP enablement.
Some tools modify PerformanceMonitor configuration; do not label the entire MCP read-only.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

PerformanceMonitor repository recorded commit c5fbd52 and v3.5.0 release work on 2026-08-19.

Technical identity

github.com/erikdarlingdata/PerformanceMonitor

Exact implementation source: https://github.com/erikdarlingdata/PerformanceMonitor ↗
Reviewed resource type: MCP Server
Repository identity: erikdarlingdata/PerformanceMonitor
Service endpoint: http://localhost:5151/

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
erikdarlingdata/performancemonitor
Recorded repository material and project history.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

MCP port 5151 is documented for PerformanceMonitorLite; Darling uses a different default endpoint and startup method.
MCP access exposes server telemetry; do not expose this HTTP port publicly.
the separate PerformanceMonitorLite-Data directory contains monitoring history and must be intentionally retained or exported.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Not a typical standalone MCP server installation; the product documentation does not establish a universal MCP host setup. Do not infer one.
Publisher UI / connection instruction, not a shell command.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
Connection / UI instruction · Publisher instructions
Enable MCP server in PerformanceMonitor Settings (default port 5151).
Configure / authenticate
Publisher instructions
Register `claude mcp add --transport http --scope user sql-monitor http://localhost:5151/`. The app must be installed/running.
Check connection
Suggested check
In a new Claude Code session ask which SQL servers are being monitored (read-only).
Remove / uninstall / revoke
MCP100 setup guide
`claude mcp remove sql-monitor`; disable MCP server in PerformanceMonitor Settings to stop exposing its endpoint.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove sql-monitor

Official Documentation & Sources

What it does

PerformanceMonitor includes an optional local Streamable HTTP MCP service for SQL Server monitoring.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Troubleshoot database performance

Representative uses

read performance tools
config-write abilities in Darling mode
localhost default

Limitations

Do not present as a standalone npm server; embedded mode requires app installation and MCP enablement.
Some tools modify PerformanceMonitor configuration; do not label the entire MCP read-only.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Built-in MCP exposes monitoring store, does not execute AI-generated SQL on production DB (per author); DB monitoring permissions still apply.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: Mostly read-only diagnostics against monitored DB, but configuration-changing tools can edit alerts, views and monitored server settings.

Access scope and cautions

Write actions: Modify monitoring configuration or monitored connections where settings tools are enabled
Risk level: moderate
Security notes: Advisory/security review not completed; no safety badge.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: read performance tools; config-write abilities in Darling mode; localhost default.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded endpoint: http://localhost:5151/. Recorded transport: streamable_http. Client notes: Verify embedded MCP tooling after application collection is configured. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Local HTTP listener on configured port; downstream database access via monitoring login with read-only query scope.

Can it modify data or perform write operations?

Documented write actions include: Modify monitoring configuration or monitored connections where settings tools are enabled. Recorded permission boundary: Built-in MCP exposes monitoring store, does not execute AI-generated SQL on production DB (per author); DB monitoring permissions still apply.

What limitations and risks should I check before use?

Mostly read-only diagnostics against monitored DB, but configuration-changing tools can edit alerts, views and monitored server settings. Not a standalone npm server; embedded mode requires app installation and MCP enablement. Some tools modify PerformanceMonitor configuration; the entire MCP is not established as read-only. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Can access production database performance contents and modify local monitoring configuration; not certified read-only. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.