# McpStamp Check (remote · mcp.zovo.one)

Score any remote MCP server for Claude, ChatGPT, Gemini and MCP Registry readiness.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.zovo.one`: 75/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-mcpstamp-check/stamp-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-mcpstamp-check/stamp-mcp)

## Channel facts

- Endpoint: `https://mcp.zovo.one/stamp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-05.

- **Endpoint Security**: 80/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 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 343 tokens (~171/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 McpStamp Check MCP server?

McpStamp Check is a hosted endpoint at https://mcp.zovo.one/stamp/mcp, 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 theluckystrike-mcpstamp-check 'https://mcp.zovo.one/stamp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-mcpstamp-check": {
      "url": "https://mcp.zovo.one/stamp/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-mcpstamp-check": {
      "type": "http",
      "url": "https://mcp.zovo.one/stamp/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-mcpstamp-check]
url = "https://mcp.zovo.one/stamp/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-mcpstamp-check": {
      "type": "remote",
      "url": "https://mcp.zovo.one/stamp/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-mcpstamp-check --url 'https://mcp.zovo.one/stamp/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-mcpstamp-check:
    url: "https://mcp.zovo.one/stamp/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-mcpstamp-check": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/stamp/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-mcpstamp-check -t streamable-http -u 'https://mcp.zovo.one/stamp/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-mcpstamp-check": {
      "type": "http",
      "url": "https://mcp.zovo.one/stamp/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-11-04 (score 75, +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-11-03 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 74)

First indexed and scored.

## MCP tools (2)

### `check_mcp_server` (~140 tokens)

Check MCP server readiness

Check a public remote MCP server URL (Streamable HTTP) for readiness for the Claude Directory, ChatGPT Apps, Gemini Connected Apps and the MCP Registry. Returns the 0-100 score, A-F grade, readiness per store, every failing or warning check with its fix, the report URL and README badge markdown. Results are cached for 10 minutes; set fresh to true to force a new check.

Input parameters:

- `fresh` (boolean): Run a new check even when a result from the last 10 minutes exists. Default false.
- `url` (string, required): The https URL of the MCP endpoint, for example https://example.com/mcp

Output parameters:

- `auth` (string)
- `badge_markdown` (string)
- `badge_url` (string)
- `cached` (boolean)
- `checked_at` (string)
- `grade` (string)
- `issues` (array)
- `report_url` (string)
- `score` (number)
- `stores` (object)
- `url` (string)

### `explain_check` (~84 tokens)

Explain a McpStamp check

Explain one McpStamp Check rule by its id (for example tool_annotations or auth_prm): what it tests, why stores need it, which stores it blocks, its weight and the store or spec documents it comes from. Use it after check_mcp_server to understand a failing check.

Input parameters:

- `check_id` (string, required): Check id from a check_mcp_server result.

Output parameters:

- `blocks` (array)
- `counts_for` (array)
- `group` (string)
- `id` (string)
- `meaning` (string)
- `rule` (string)
- `sources` (array)
- `sources_file` (string)
- `title` (string)
- `weight` (number)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 74
- 2026-11-02: 74

## Common questions

### What is the McpStamp Check MCP server?

McpStamp Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/mcpstamp-check. Score any remote MCP server for Claude, ChatGPT, Gemini and MCP Registry readiness. This page covers its hosted endpoint (https://mcp.zovo.one/stamp/mcp).

### Is the McpStamp Check MCP server safe to use?

McpStamp Check scores 75 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 McpStamp Check MCP server expose?

McpStamp Check exposes 2 tools: check_mcp_server, explain_check. Their descriptions and schemas cost roughly 224 tokens of context every time the server is loaded.

### Does the McpStamp Check MCP server require authentication?

No. We connected to McpStamp Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the McpStamp Check MCP server still maintained?

McpStamp Check is still listed as active in the MCP registry. We last reached this channel on 5 November 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://mcp.zovo.one/stamp/mcp
- Repository: https://github.com/theluckystrike/mcpstamp-check
- Website: https://www.mcpstamp.com/check/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-mcpstamp-check/stamp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-mcpstamp-check/stamp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-mcpstamp-check/stamp-mcp