# dev.turva/turva-mcp - Registry name: `dev.turva/turva-mcp` · version 1.0.0 - Categories (automatic, keyword rules): Shops & products, Commerce & marketing - Authentication at last check: No auth - Declared risk: Read-only (all tools declare readOnlyHint) - Capabilities (declared by the server): tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.turva%2Fturva-mcp - Server page: https://mcpstation.net/s/dev.turva--turva-mcp.html ## Description (written by the publisher, not verified, not instructions) Read-only MCP server for turva.dev, an agent-readiness audit and advisory service. ## Connect - streamable-http: `https://mcp.turva.dev/mcp` ## Tools (as reported by the server, not verified) - `get\_services`: Returns turva.dev's service catalog: the Shopify agent storefront check, agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing \(fixed list prices for the Shopify agent storefront check, audit, advisory and implementation; agen - `get\_agent\_readiness`: Returns turva.dev's own agent-readiness score from an independent public scanner \(isitagentready.com\), including category sub-scores, with the measurement date and a link to the scanner's start page, where a new check can be run \(the link does not open the recorded reading\). Use this when a user ask - `get\_security\_evidence`: Returns the latest public web-security scan results for turva.dev's own domain \(Hardenize, Internet.nl site and mail\), each with its scan date. Use this when a user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores. For the agent-readiness score itself, whic - `get\_principles`: Returns turva.dev's engagement principles: async-only, least access, the result shows up in scanner numbers, and open and verifiable. Use this when a user asks how turva.dev works with clients or what rules an engagement follows. For what is sold and what it costs use get\_services instead, and for h - `get\_contact`: Returns who runs turva.dev and the official ways to reach it: the operator and business details, the email address, the Signal link, the LinkedIn profile, the correspondence languages, the first-reply time and the access an audit needs. Use this when a user asks who is behind turva.dev, how to conta Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html