
Official MCP RegistryListed
dev.turva/turva-mcp
Read-only MCP server for turva.dev, an agent-readiness audit and advisory service.
First seen 2 Oct 2026. Evidence as of 21 Nov 2026.
5
Tools
From an anonymous probe
1
Source listings
Each with its own history
27
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| 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 asks how turva.dev scores, whether its claims are verifiable, or what proof backs the audit service. For web-security scan results, which are a separate measurement, use get_security_evidence instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy. | Read-only |
| get_contact | Returns who runs turva.dev and the official ways to reach it. The operator details give the legal form, Business ID, VAT ID and postal address. The rest gives the email address, the Signal link, the LinkedIn profile, the correspondence languages, the first-reply time, the access an audit needs, and links to the company page and to the legal page that states the terms, the privacy notice and how data is handled. Use this when a user asks who is behind turva.dev, for its legal or imprint details, how to contact it, how to start an audit or what access has to be granted. For what is sold and what it costs use get_services instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy. | Read-only |
| get_principles | Returns turva.dev's four engagement principles, each with its reason: async-only, least access, each fix checked with a scanner or a direct test, and open and verifiable. Use this when a user asks what turva.dev stands by or why it works the way it does, for example why there are no calls. For the terms of an engagement, its scope, access, dates, payment and prices, use get_services instead, and for how to start use get_contact. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy. | Read-only |
| 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, which is a separate measurement, use get_agent_readiness instead. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy. | Read-only |
| get_services | Returns turva.dev's service catalog: the agent-readiness audit, advisory, implementation, the MCP server security test, agent operations, and MCP server design, with pricing and the terms of an engagement: scope, access, dates and payment. Fixed list prices apply to the audit, advisory and implementation. The MCP server security test, agent operations and MCP server design are on request. The catalog also lists one implementation add-on that carries a fixed price and is sold only with the audit it follows, bought with it, with its report, or after the report and before implementation starts. It also lists active security testing, an add-on to the audit that is priced by quote for each written scope, under quoted_add_ons. The audit links a published sample report in sample_url, a fictional worked example of the deliverable. Use this when a user asks what turva.dev offers, what it costs, what the terms of an engagement are, or what a delivered report looks like. For the standing rules turva.dev keeps in every engagement use get_principles instead, and for how to reach turva.dev or start an audit use get_contact. Read-only: returns static JSON that is compiled into the Worker, so it changes nothing and updates only on deploy. | Read-only |
Change history
- get_services: description changed (+"the MCP server security test," +"The MCP server security test, agent" -"Agent")
- get_services: description changed (+"with pricing and" +"terms of an engagement: scope, access, dates" +"payment.")
- get_principles: description changed (+"four" +"principles, each with its reason:" +"what")
- get_contact: input schema changed
- get_contact: description changed (+"it. The operator details give" +"legal form, Business ID, VAT ID" +"postal address. The rest gives")
- server instructions changed (+"answers" +"the terms of" +"For the standing rules behind every engagement and the reason")
- get_services: input schema changed
- get_services: description changed (+"It also lists active security testing, an add-on to the audit that is priced by quote for each written scope, under quoted_add_ons.")
- get_services: input schema changed
- get_services: description changed (-"external domain check," -"external domain check," -"The external domain check links a sample report made from turva.dev's own domain, with real readings.")
- get_security_evidence: input schema changed
- get_contact: input schema changed
- server instructions changed (+"report." -"reports.")
- get_principles: description changed (+"each fix checked with a" +"or a direct test," -"the result shows up in")
- get_services: description changed (+"one" +"add-on" +"carries")
- get_services: description changed (+"external domain check, the" +"pricing. Fixed" +"apply to")
- get_services: description changed (+"The Shopify agent storefront check and the audit each link a published sample report in sample_url, a fictional worked example of the deliverable." +"works, or what a delivered report looks like." -"or")
- server instructions changed (+"prices," +"runs and the published sample reports." +"any site: for a fresh reading of a domain, turva.dev included, run the check on isitagentready.com itself.")
- get_services: input schema changed
- get_services: input schema changed
- get_security_evidence: input schema changed
- get_principles: input schema changed
- get_contact: input schema changed
- get_agent_readiness: input schema changed
- get_security_evidence: input schema changed
- get_security_evidence: description changed (+"each" +"its" -"the")
- get_agent_readiness: description changed (+"a link to the scanner's start page, where a new check can be run (the link does not open the recorded reading)." -"verification links.")
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | dev.turva/turva-mcp | 2 Oct 2026 | 21 Nov 2026 | 1 |