Skip to content
MCP server

Ntobjmanager MCP

MCP server for stateful Windows RPC attack-surface research by security analysts

Pricing
Open source
Platforms
Windows, CLI
Version
1.0.0
Listing updated
today

Similar MCP servers

About Ntobjmanager MCP

Ntobjmanager MCP is an open-source MCP server for security. It is available on Windows and CLI.

The README describes this server as a way to give an AI agent persistent, stateful access to Windows RPC research, built on James Forshaw's NtObjectManager library. A persistent PowerShell engine keeps parsed RPC server objects and connected RPC clients alive across tool calls, so an agent can connect once and issue many calls while keeping authentication state and handle chains intact.

The server exposes 24 tools grouped into a core stateful pipeline, a lab VM bridge for running PowerShell inside a guest with persistent state, and a set of tools that wrap fixed hunting workflows drawn from recent public Windows RPC vulnerability research. Each tool call is written to an audit log, and fuzzing defaults to a dry run.

The README is explicit that it is intended for authorized security research and testing inside an isolated VM, since invoking RPC methods can crash services. It also lists limits, such as that it cannot automatically confirm type confusion bugs and that it currently targets Windows PowerShell 5.1.

Tools this server provides (24)

Taken from the project documentation; the running server may differ.

rpc_parse
Parse a PE for RPC servers and cache them.
rpc_state
List cached servers and live sessions.
rpc_get_interface
Show procedures, NDR parameters, and context handles for an interface.
rpc_query_endpoints
Query the endpoint mapper locally or remotely.
rpc_running_servers
Enumerate live processes or services hosting RPC.
rpc_connect
Generate and connect a stateful RPC client.
rpc_methods
List method signatures with opnum mapping.
rpc_call
Invoke an RPC method via reflection with stored object support.
rpc_disconnect
Drop an RPC session.
rpc_vm_exec
Run PowerShell inside a lab VM with persistent state.
rpc_vm_start_listener
Deploy and start the persistent guest HTTP engine.
rpc_scan_context_handles
Scan for context-handle type confusion patterns.
rpc_inventory
Build an attack-surface inventory with endpoint mapper cross-check.
rpc_fuzz
Primitive-only default-value fuzzing, dry-run by default.
rpc_find_hijackable
List unregistered interfaces of stopped services.
rpc_etw_unreachable
Capture clients calling dead servers via ETW; requires admin.
rpc_interface_security
Audit ALPC security descriptors and anonymous ACEs.
rpc_decode_flags
Decode RpcServerRegisterIf3 flag bitmasks.
rpc_format_client
Export generated C# client source.
rpc_new_struct
Build NDR complex types as session variables.
rpc_alpc_squat
Squat an ALPC port and capture connections.
rpc_accessible_tasks
List user-startable tasks.
rpc_vars
Show session variables.
rpc_clear_cache
Clear the server cache.

What it does

Stateful RPC clients
A persistent PowerShell engine keeps connected RPC clients and session variables alive between tool calls.
Context handle chaining
Return objects can be stored as session variables and passed to later calls without serialization.
Parsed interface inspection
Parses PE files for RPC servers and reports procedures, NDR parameters, and context handles.
Dry-run fuzzing
Primitive-only default-value fuzzing that runs in dry-run mode unless explicitly changed.
Lab VM execution
Runs PowerShell inside a lab virtual machine with state kept in one guest runspace.
Audit logging
Appends every tool call to an audit log file.

Good for

  • Auditing Windows RPC interfaces for context-handle misuse in an isolated lab
  • Mapping RPC endpoints and stopped services with unregistered interfaces
  • Driving multi-step RPC call sequences from an AI agent without re-authenticating each step
  • Inventorying user-startable Windows tasks as part of a security review

Pricing

Open source

Free and open source under MIT license.

Ntobjmanager MCP FAQ

Does it run on non-Windows systems?

The README says it runs on Windows PowerShell 5.1, and that running elsewhere is not yet supported; pwsh 7 is untested.

Can it confirm exploitable vulnerabilities automatically?

No. The README states that NDR cannot prove distinct handle types, so type confusion findings must be verified through reverse engineering.

What does it require to run?

The README lists the NtObjectManager PowerShell module and Python with the mcp package, installed via pip from requirements.txt.

What license is it under?

The README states the project is licensed under MIT.

Is Ntobjmanager MCP free?

Yes. Ntobjmanager MCP is open source, so you can use and self-host it for free.

What are the best alternatives to Ntobjmanager MCP?

The closest alternatives to Ntobjmanager MCP are MCP Tool Poisoning Scanner, mcp-agent-template, MCPSense, Cybersec Toolkit and MCP security checks — WARDEN and HISTOR.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.

How AIPoweredBot checks servers