Ntobjmanager MCP server
io.github.lupingQAQ/ntobjmanager-mcp·v1.0.0·13 starsStateful Windows RPC attack-surface research for AI agents: 22 tools on NtObjectManager.
13 stars
Reviews
Write oneNobody has reviewed Ntobjmanager yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Ntobjmanager tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualityno auth information5/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Ntobjmanager compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
- GitHub stars
- 13
- more than 89% of 28,688 servers
Install Ntobjmanager in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Ntobjmanager repository's README, as published. We do not edit it. Read it on GitHub
🛰️ NtObjectManager-MCP
Stateful Windows RPC Research MCP — 2024–2026 CVE methodologies as one-click tools
🌐 中文版
What is NtObjectManager-MCP?
A Model Context Protocol server that gives an AI agent live, stateful access to Windows RPC attack-surface research, built on James Forshaw's NtObjectManager (NtCoreLib).
Three things a generic PowerShell MCP cannot do — and the reason this exists:
RpcServer objects and connected RPC clients alive across tool calls: rpcconnect once, rpccall many times (auth handshakes, context-handle chains, session variables survive).
- Stateful RPC connections — a persistent PowerShell engine keeps parsed
2024–2026 public research are one-click, not prompt-engineering.
- CVE methodology as fixed tools — the standard hunting workflows from
in the guest: rpcvmexec keeps variables and connected RPC clients alive across calls through a single persistent guest runspace, never a fresh shell per call (the vmrun fallback is reported as stateful: false).
- Stateful execution inside a lab VM — the same one-engine principle applied
┌────────────────────────────────────────────────────────────────────┐
│ AI Agent (Claude Code / OpenCode / any MCP client) │
│ │ MCP (stdio, 24 tools) │
│ ▼ │
│ server.py ── snippets.py (PS templates, @@TOKEN@@ + ps_str escape)│
│ │ │
│ ▼ │
│ ps_engine.py ── persistent powershell.exe (base64 + __MCP_DONE__) │
│ │ state: $RPCMCP = @{ Servers; Clients; vars } │
│ ▼ │
│ NtObjectManager / NtCoreLib ──► RPC runtime (ALPC / pipe / TCP) │
└────────────────────────────────────────────────────────────────────┘Tool Matrix (24)
Core stateful pipeline
VM lab bridge (stateful guest execution)
2024–2026 CVE methodology tools
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Ntobjmanager: common questions
- Is Ntobjmanager MCP server safe?
- Mostly: it is graded B (70/100). Read the Ntobjmanager safety report
- Does Ntobjmanager need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Ntobjmanager maintained?
- The last commit was 35 days ago (2026-09-30). The latest release is v1.0.0.
- How does Ntobjmanager compare with other MCP servers?
- safety score 70/100 (higher than 35% of 48,255 servers); github stars 13 (more than 89% of 28,688 servers). Full comparison.