MCP.Market

Endpoint AIops MCP server

by AIops-tools·io.github.AIops-tools/endpoint-aiops·v0.13.0

Governed managed-endpoint ops — login-storm & drift analysis, 13 MCP tools with audit/budget/undo.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

0 stars129 downloads/wk

Reviews

Write one

Nobody has reviewed Endpoint AIops yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Endpoint AIops tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Endpoint AIops compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Downloads a week
129
more than 68% of 12,191 servers with a package

Release history: 3 versions in the registry since 2026-09-15, latest 2026-10-30, typically one every 30 days.

Install Endpoint AIops in Claude Code, Cursor or VS Code

claude mcp add endpoint-aiops -- uvx endpoint-aiops
Add to Cursor

What the publisher says

From the Endpoint AIops repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: io.github.AIops-tools/endpoint-aiops -->

Endpoint AIops

Disclaimer: Community-maintained open-source project. Not affiliated with, endorsed by, or sponsored by any endpoint-management vendor. Product and trademark names belong to their owners. MIT licensed.

Governed AI-ops for managed-endpoint fleets — thin clients, VDI endpoints, and other centrally-managed devices — with a built-in governance harness: unified audit log, token/runaway budget guard, undo-token recording, and descriptive risk tiers. Vendor-neutral: it talks to an endpoint-management server's REST API (Bearer auth) through a configurable dialect — see Dialects. Self-contained: no dependencies beyond httpx and the MCP SDK. The test suite is mock-based; the endpoint-management REST paths have not yet been exercised against a live management server — see docs/VERIFICATION.md.

What it does

Two signature analyses, plus the guarded reads and writes around them:

detect the storm (bursts of concurrent logins in a sliding window) and rank the endpoints/users dragging login and boot times. Every flag is reported with its number, not a black-box verdict.

  • Login-storm analysis — during a "everyone logs in at 9am" incident,

(outdated patch level, stray agent version, divergent OS build or config profile). With no declared baseline it derives one by fleet majority, so it works before a gold image exists.

  • Patch / config drift — find endpoints that have drifted from the fleet

What works

  • CLI (endpoint-aiops ...): init, overview, endpoint list/get/assign-profile/reboot, session list/storm, drift report/patch, secret set/list/rm/migrate/rotate-password, doctor, mcp.
  • MCP server (endpoint-aiops mcp or endpoint-aiops-mcp): 13 tools (10 read, 3 write), every one wrapped with the bundled @governed_tool harness.
  • Encrypted credentials: the management-server API key lives in an encrypted store ~/.endpoint-aiops/secrets.enc (Fernet + scrypt) — never plaintext on disk. Unlock with a master password from ENDPOINTAIOPSMASTER_PASSWORD (MCP/CI) or an interactive prompt (CLI).
  • Reversibility: endpointassignprofile (high risk) captures the prior profile and records an inverse "reassign the prior profile" undo descriptor. endpoint_reboot (medium risk) captures the prior online state for the audit record but declares no undo (a reboot has no safe inverse).
  • Safety: state-changing CLI ops (endpoint assign-profile, endpoint reboot) require double confirmation and support --dry-run.

Capability matrix (13 MCP tools)

The analysis tools (loginstormanalysis, driftreport, patchstatus, patchcompliance, endpointhealthscore) accept injected records for pure/offline analysis; endpointhealthscore and patchcompliance are injected-only, the others also pull live from a configured target.

What this tool does, and does not, decide

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Endpoint AIops: common questions

Is Endpoint AIops MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Endpoint AIops safety report
How do I install Endpoint AIops?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Endpoint AIops need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Endpoint AIops maintained?
The last commit was 49 days ago (2026-09-16). The latest release is v0.13.0.
How does Endpoint AIops compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); downloads a week 129 (more than 68% of 12,191 servers with a package). Full comparison.

More from AIops-tools →