Skip to main content
aspex-scan mcp serves Aspex over the Model Context Protocol on stdin/stdout. The point is a workflow like this:
Aspex does not block the edit. It makes the consequence visible before the edit, to the thing about to make it.

Tools

Read-only by construction

There are no write, exec, fix or configuration tools. The server cannot modify files, run commands, or change Aspex’s own policy, lockfile or baseline. aspex_verify reads only lockfiles. The environment is computed once per process and cached; restart the server to rescan. The tool list is fixed in code and covered by a test that fails if a tool name ever looks like a write or exec action.