Development on NTNINJA

dnre-mcp 0.1.0 — .NET Reverse Engineering via MCP

Thu, 05 Mar 2026 01:00:00 +0000

I just released dnre-mcp 0.1.0, a standalone MCP server for .NET assembly reverse engineering and decompilation.

What It Does
#

dnre-mcp lets AI assistants load, inspect, and decompile .NET assemblies directly through the Model Context Protocol. It exposes 10 tools covering assembly loading, type and method discovery, namespace browsing, and full C# source decompilation. Under the hood it uses ICSharpCode.Decompiler, the same engine that powers ILSpy.

WEDP 1.0.0-rc1 and dbgeng-mcp 0.1.0

Thu, 12 Feb 2026 01:00:00 +0000

Quick update on two projects that have been getting a lot of my attention lately.

WEDP 1.0.0-rc1
#

WEDP (Windows Exploit Development Plugin) has hit its first release candidate. If you are not familiar with it, WEDP is a native WinDbg extension I built for exploit development workflows. It provides ROP/SEH/stack-pivot gadget search, cyclic pattern utilities, module protection enumeration, inline assembly, and a bunch of other stuff you would normally need multiple tools for. I wrote a post recently on using it with an MCP server and that really pushed me to clean things up and get a proper release out.

WinDBG MCP with WEDP

Fri, 06 Feb 2026 09:00:00 -0500

I have been late to the game with adopting GenAI into my workflow, but we are at full steam now. I have slowly been adding it into my daily routines to see where I can gain efficiency leveraging this new tech. One of the big areas I am playing with right now is for writing Windows based CTF challenges, and now in the past few days, seeing how I can leverage GenAI for writing POCs for these new challenges. In this post we are going to walk through my initial setup for using the WinDbg EXT MCP to control a windbg instance that has the extension I wrote a long time ago, WEDP (Windows Exploit Development Plugin), to improve the process of going from crash to POC.

Protecting Repos with Encrypted GIT

Mon, 21 Nov 2022 15:00:00 -0500

Open source software development is great, and there exists an abundance of difference git solutions to create public and private repositories for collaboration and distribution. Private repos give you an extra layer of control by not allowing your code base to be seen by the public. Occasionally you may have a project that you want to be able to collaborate with a limited set of remote people, and want restrict the possiblity of your source being viewed, even by the git service provider. None of the commercial git providers have a good solution for this currently, at least that I know of.

rundll... more like fundll

Sun, 25 Sep 2022 09:00:00 -0500

Have you ever written a DLL that had standalone functionality and wasn’t meant to be used as a library? Considering that library is in the name, this idea seems contrary to what a library should be. Well, you can thank Microsoft for providing a way to execute standalone functionality from a DLL. Not only did they do that, they also provide DLLs with functionality that you need this utility to run!!! Say hello to rundll32, pronounced run dull all smashed as one word in some circles.