Audit an MCP config, price a model, size a GPU, explain network config drift. Key-free.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Four things I kept doing by hand while running AI in production, turned into tools an agent can call: price a model before committing a budget, size a GPU before ordering one, review an MCP config before trusting it, and explain what changed in a network device config.
Free, MIT, no account, no telemetry.
Pin the version β see audit_mcp_config for why.
Claude Code
Claude Desktop, Cursor, or any client with a JSON config
Docker
Node 18 or newer for the npx route; nothing else to configure either way. The server is also in the
official MCP registry as io.github.labaccessnow/aiops-field-notes-mcp.
| Tool | What it answers |
|---|---|
estimate_llm_cost | What does this workload cost per month on each model, cheapest first? |
check_vram_fit | Does a 70B model at Q4 fit on my 4090 with a 32K context? |
audit_mcp_config | Is this MCP config safe to trust β what can each server actually reach? |
lookup_mcp_server | What is this server, who maintains it, and is it reference, vendor or community? |
explain_config_diff | What changed on this router between two snapshots, and how bad is it? |
check_config_compliance | Does this device config pass the CIS/PCI basics? |
latest_field_note | What happened in AI ops this week? |
The one I use most. Paste a client config and it reads it the way a reviewer would β every server entry is an access grant, so the questions are what it can reach, who publishes it, and what happens the next time it auto-updates:
It also flags shell entrypoints, privileged containers, host-root mounts, credentials on the command line, database access that is not read-only, unauthenticated remote servers, and anything reached over plain HTTP.
audit_mcp_config takes the config as text, so the server never reads your disk.latest_field_note fetches a public RSS feed. Skip that tool
and this server never opens a socket.The cost table, GPU list and server directory match the calculators at aiopsfieldnotes.com/tools and get re-verified with each weekly episode. Pricing moves β check the vendor's page before you commit a budget to it.
explain_config_diff and check_config_compliance are the read-only core of
DriftWatch, which runs the same rules nightly across a fleet and
keeps the history. Here you get the single-shot version, on two snapshots you paste, with no storage and
no scheduler. That is deliberate: the rules are the useful part, and they work fine on their own.
MIT. Written by James Son β network, security, and automation engineer β and tested in a live multi-vendor lab. Contributions and corrections welcome.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/aiops-field-notes)<a href="https://allmcps.com/mcp/aiops-field-notes"><img src="https://allmcps.com/api/badge/aiops-field-notes?style=directory" alt="AIOps Field Notes on AllMCPs" /></a>