# MCP security checks — WARDEN and HISTOR (remote · modelmarket.dev)

Scan MCP tool definitions for poisoning, look up server history, count tool-list tokens. Free.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

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

## Channel facts

- Endpoint: `https://modelmarket.dev/tools/mcp/security`
- 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-10-22.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 572 tokens (~143/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MCP security checks — WARDEN and HISTOR server?

MCP security checks — WARDEN and HISTOR is a hosted endpoint at https://modelmarket.dev/tools/mcp/security, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-modelmarket-mcp-security 'https://modelmarket.dev/tools/mcp/security'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-modelmarket-mcp-security": {
      "url": "https://modelmarket.dev/tools/mcp/security"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-modelmarket-mcp-security": {
      "type": "http",
      "url": "https://modelmarket.dev/tools/mcp/security"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-modelmarket-mcp-security]
url = "https://modelmarket.dev/tools/mcp/security"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev-modelmarket-mcp-security --url 'https://modelmarket.dev/tools/mcp/security' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-modelmarket-mcp-security:
    url: "https://modelmarket.dev/tools/mcp/security"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-modelmarket-mcp-security": {
      "Transport": "http",
      "Url": "https://modelmarket.dev/tools/mcp/security"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-modelmarket-mcp-security -t streamable-http -u 'https://modelmarket.dev/tools/mcp/security'
```

### Other

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

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-10-22 (score 71, +1)

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

### 2026-10-21 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 70)

First indexed and scored.

## MCP tools (4)

### `warden_scan` (~110 tokens)

Scan tool definitions (WARDEN)

Scan an MCP server's tools/list with WARDEN, the open-source MCP firewall: static rules and a threat list over every name, description, schema and annotation. Returns allow or block and each finding with its rule and severity. Quoted fragments of the scanned text are left out of the answer.

Input parameters:

- `server` (object): Optional {name, url} to label the verdict
- `tools` (array, required): The server's tools/list result: [{name, description, inputSchema, ...}]

### `histor_check` (~92 tokens)

Server history (HISTOR)

Look up an MCP server in HISTOR, a public append-only log of MCP tool sets: when its tool set was first pinned, how often it changed, and what the pattern scan found. HISTOR answers from its own observations and never contacts the server.

Input parameters:

- `endpoint` (string): https URL of the MCP server
- `name` (string): Or its registry name, e.g. io.github.owner/server

### `tool_list_cost` (~110 tokens)

Tool list token cost

How many tokens an MCP server's tool list adds to every model request, what that costs per 1,000 requests, the heaviest tools, and where it sits among 18,204 packages and 16,170 remote servers. Send a tools/list or name a server HISTOR observes.

Input parameters:

- `server` (string): Or a server HISTOR observes: https endpoint, npm:<package>, pypi:<package> or registry name
- `tools` (array): A tools/list result

### `x402_check` (~183 tokens)

x402 payment check

Check a signed x402 USDC payment before submitting it: recovers the EIP-712 signer, runs USDC's own checks and the seller's terms, and when the signature fails names the domain it was really made for (e.g. Base Sepolia's 'USDC' used on Base, where USDC is 'USD Coin').

Input parameters:

- `authorization` (object): Instead of x_payment: from, to, value, validAfter, validBefore, nonce
- `network` (string): With authorization: base, base-sepolia, … or eip155:<id>
- `requirements` (object): The 402's accepts entry: payTo, amount, asset, network
- `signature` (string): With authorization: the 65-byte hex signature
- `x_payment` (string): The X-PAYMENT header (base64)

## Diagnostics

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

## Score history

- 2026-10-22: 71
- 2026-10-21: 70
- 2026-10-20: 70

## Common questions

### What is the MCP security checks — WARDEN and HISTOR server?

MCP security checks — WARDEN and HISTOR is listed in the public MCP registry as dev.modelmarket/mcp-security. Scan MCP tool definitions for poisoning, look up server history, count tool-list tokens. Free. This page covers its hosted endpoint (https://modelmarket.dev/tools/mcp/security).

### Is the MCP security checks — WARDEN and HISTOR server safe to use?

MCP security checks — WARDEN and HISTOR scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MCP security checks — WARDEN and HISTOR server expose?

MCP security checks — WARDEN and HISTOR exposes 4 tools: warden_scan, histor_check, tool_list_cost, x402_check. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.

### Does the MCP security checks — WARDEN and HISTOR server require authentication?

No. We connected to MCP security checks — WARDEN and HISTOR without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MCP security checks — WARDEN and HISTOR server still maintained?

MCP security checks — WARDEN and HISTOR is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://modelmarket.dev/tools/mcp/security
- Repository: https://github.com/alexar76/warden
- Website: https://modelmarket.dev/tools/
- Changelog RSS feed: https://verifymcp.io/servers/dev-modelmarket-mcp-security/tools-mcp-security.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-modelmarket-mcp-security/tools-mcp-security.json
- HTML version of this page: https://verifymcp.io/servers/dev-modelmarket-mcp-security/tools-mcp-security