También en español: rosmarops.com/es/blog/rosmarops-0-4-0/ · També en català: rosmarops.com/ca/blog/rosmarops-0-4-0/
An MCP server is a door your agent uses to reach something else: a database, a service, a folder. When you add one, you look at where it goes. The question is what happens next week, when it points somewhere else and nothing on your screen tells you.
That’s what RosmarOps 0.4.0 is about.
What’s new
- It records where each MCP server sends data: the domain of a remote server, or the program behind a local one. The report tells you when a server is new.
- It warns you when an MCP server points somewhere else since the last run: a new address, a different program or arguments, a changed setting that isn’t a secret, or an edited local script. Rotating a key doesn’t count as a change.
- It reads the
headersof MCP servers in Cursor, Cline and Claude Desktop as credentials, and the MCP servers in Claude Code’smanaged-mcp.json. - An MCP server you accepted in your allow list stops being accepted if it starts pointing somewhere else. Accepting a server means accepting where it goes, not its name.
Harder to fool
- A setting written with unexpected capital letters is a red finding, because the agent and RosmarOps could be reading different values.
- A source RosmarOps couldn’t read never leaves the report green.
- Text read from your files is cleaned before it reaches the report and the text for your AI, and that text tells your AI to treat paths and names as data.
- If RosmarOps’s memory of past findings is missing, the report says so.
- The report counts the warnings your own configuration hides.
What it can’t see
A server that runs a package downloaded on every start, such as npx package@latest, can change at its source without anything changing on your disk. RosmarOps doesn’t see that, because it has no network access. And the first run of this version has nothing to compare destinations with, so it can only start counting from there.
It doesn’t block anything, and it doesn’t check domains against any list. It tells you where your servers point, and when that changes. What you do about it is up to you.
Still no networking code and no telemetry.
Get it
Download it for Windows from GitHub. The download is attested and the build is reproducible: how to check it. If you used an earlier version, RosmarOps asks you to confirm the new one the first time.
I wrote this with AI assistants. The machine, the findings and the decision to publish are mine.