All servers · Shops & products

dev.turva/turva-mcp

dev.turva/turva-mcp · v1.0.0

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Read-only (all tools declare readOnlyHint)
Capabilities declared	tools
Tool definitions	5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

Description written by the publisher, not verified

Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.

Connect

streamable-http · https://mcp.turva.dev/mcp

claude mcp add --transport http turva-mcp https://mcp.turva.dev/mcp

{
  "mcpServers": {
    "turva-mcp": {
      "url": "https://mcp.turva.dev/mcp"
    }
  }
}

Tools as reported by the server

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

JSON · Text for agents · Registry updated 2026-06-24