# dev.turva/turva-mcp (remote · mcp.turva.dev)

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

- Trust score: 78/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.turva.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/dev-turva-turva-mcp/mcp.md), [page](https://verifymcp.io/servers/dev-turva-turva-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.turva.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 312 tokens (~78/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

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

### Codex

```toml
[mcp_servers.dev-turva-turva-mcp]
url = "https://mcp.turva.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-turva-turva-mcp": {
      "type": "remote",
      "url": "https://mcp.turva.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-turva-turva-mcp --url https://mcp.turva.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-turva-turva-mcp:
    url: "https://mcp.turva.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-turva-turva-mcp": {
      "type": "http",
      "url": "https://mcp.turva.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 77, 0)

- [functional] Server version: 1.3.0 → 1.3.3

### 2026-08-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 76, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

- [functional] Server version: 1.2.9 → 1.3.0
- [cosmetic] Tool “get_agent_readiness” changed its title: Agent-readiness score
- [cosmetic] Tool “get_principles” changed its title: Engagement principles
- [cosmetic] Tool “get_security_evidence” changed its title: Web-security scan evidence
- [cosmetic] Tool “get_services” changed its title: Service catalog and pricing

### 2026-07-28 (score 71, 0)

- [functional] Server version: 1.2.8 → 1.2.9

### 2026-07-27 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `get_services` (~91 tokens)

Service catalog and pricing

Returns turva.dev's service catalog: agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for audit, advisory and implementation; agent operations and MCP server design on request). Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. Read-only: returns static JSON and changes nothing.

### `get_agent_readiness` (~82 tokens)

Agent-readiness score

Returns turva.dev's own agent-readiness score from an independent public scanner (isitagentready.com), including category sub-scores, with the measurement date and verification links. Use this when a user asks how turva.dev scores, whether its claims are verifiable, or what proof backs the audit service. Read-only: returns static JSON and changes nothing.

### `get_security_evidence` (~71 tokens)

Web-security scan evidence

Returns the latest public web-security scan results for turva.dev's own domain (Hardenize, Internet.nl), with the scan date. Use this when a user asks about turva.dev's own security posture or wants evidence beyond agent-readiness scores. Read-only: returns static JSON and changes nothing.

### `get_principles` (~68 tokens)

Engagement 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. Read-only: returns static JSON and changes nothing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-turva-turva-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 77
- 2026-08-01: 77
- 2026-07-31: 76
- 2026-07-30: 73
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 71
- 2026-07-26: 70

## Links

- Remote endpoint: https://mcp.turva.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-turva-turva-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-turva-turva-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-turva-turva-mcp/mcp