Dome Systems has published the most practical MCP security review this series has read. In Review a remote MCP server before connecting it, the post starts from one concrete case: a support assistant that needs to search tickets and add internal notes, connected to a server that also offers a customer-export tool. “Should the assistant be able to call it?” The rule that follows is the right one: “A successful connection tells you the server works. Before using it in production, you also need to know what the agent can do, whose permissions it uses, and what happens when a call fails.”
There are no figures, and every item is a test, not a principle. Checking that export is missing from the tool list “isn’t enough; try calling it directly.” Ask whose account the ticketing system sees, the employee or a shared service account, because “an email address supplied as a tool argument isn’t proof of identity.” Confirm the server validates that a token was issued for it, not passed through from the ticketing API. Run a test with synthetic contact details and inspect what the agent actually receives, because “a saved configuration doesn’t tell you whether a nested field survived.” The sharpest item is the retry: the note is saved but the response never arrives, and “retrying immediately could create the same note twice.” Reproduce it, and if the application cannot tell whether the write happened, “keep note creation disabled until there’s a safe recovery procedure.” It also flags server-side request forgery during OAuth setup, before the first tool call.
The catalog holds Dome as a gateway vendor with almost no contract of its own. The Dome Systems provider page lists no API pages. On the Agent Readiness score, the MCP server and auth clarity are lit; spec presence and agentic access are unlit.
The Kin Score is 42.3, developing band, carried by access clarity at 76.3 and developer ergonomics at 71.4 against contract quality at 0.0. The Agent Readiness score is 9.9, agent-aware. The retry test is the post’s gift to everyone else, and it is the idempotency dimension this series checks on every provider: a contract that lets a caller repeat a write safely, usually with an idempotency key. Most providers in this series have it unlit. Dome has written the test that would show which of them a support assistant can safely retry. Its own record should publish the contract that would pass it.