turva-mcp

Web-security scan evidence

get_security_evidence

Read-onlyIdempotent

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`scans`	Yes
`domain`	Yes
`measured_at`	Yes	Date of the scans, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

addedOutput schema / properties / scans / items / properties / measured_at

Added value: +{
+  "description": "Date of this reading, YYYY-MM-DD, when it differs from the top-level date.",
+  "type": "string"
+}

changedOutput schema / properties / scans / items / required

Previous value: -[
-  "provider"
-]New value: +[
+  "provider",
+  "url"
+]

Changed1 schema field changedOct 2, 2026
- changedOutput schema / properties / scans / items / required
```
Previous value: -[
-  "provider",
-  "url"
-]New value: +[
+  "provider"
+]
```

Changed3 schema fields changedSep 23, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "domain": {
+      "type": "string"
+    },
+    "measured_at": {
+      "description": "Date of the scans, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "scans": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "note": {
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "result": {
+            "type": "string"
+          },
+          "scale": {
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "provider",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "domain",
+    "measured_at",
+    "scans",
+    "note"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 29, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedJun 24, 2026

TDQS

A4.7/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new context beyond them: the JSON is static, compiled into the Worker, changes nothing, and updates only on deploy — which tells the agent the data can be stale relative to deploys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: content first, usage/alternative second, behavioral caveat third. No filler, and the most decision-relevant routing information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation in prose. Combined with full routing guidance and the static/deploy caveat, an agent has everything needed to select and call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly avoids inventing parameter-like filtering options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns the latest public web-security scan results (Hardenize, Internet.nl site and mail) for turva.dev's own domain, each with a scan date. It explicitly distinguishes itself from the sibling get_agent_readiness by naming the separate agent-readiness measurement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition (user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores) and names the alternative tool with the exact condition that routes to it (for the agent-readiness score, use get_agent_readiness instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All turva-mcp tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?