# SureCheck MCP (mcpb · surecheck-mcp-0.1.1.mcpb)

Local stdio phone metadata and email syntax/DNS checks. Not live carrier or mailbox verification.

- Trust score: 37/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- mcpb · `surecheck-mcp-0.1.1.mcpb`: 37/100 (this document), [markdown](https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp.md), [page](https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Killfear1/surecheck-mcp/releases/download/0.1.1/surecheck-mcp-0.1.1.mcpb`
- Transport: `stdio`
- SHA-256: `71a583e7e867882d6e40acbbe1855b3bb765b2b3586076b51dc9269762e978b3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-23.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 90 tokens (~45/item across 2 items; 2 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**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the SureCheck MCP server?

SureCheck MCP ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 71a583e7e867882d6e40acbbe1855b3bb765b2b3586076b51dc9269762e978b3; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Killfear1/surecheck-mcp/releases/download/0.1.1/surecheck-mcp-0.1.1.mcpb`
- SHA-256: `71a583e7e867882d6e40acbbe1855b3bb765b2b3586076b51dc9269762e978b3`

### Verify on macOS / Linux

```bash
echo "71a583e7e867882d6e40acbbe1855b3bb765b2b3586076b51dc9269762e978b3  surecheck-mcp-0.1.1.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\surecheck-mcp-0.1.1.mcpb).Hash -eq "71a583e7e867882d6e40acbbe1855b3bb765b2b3586076b51dc9269762e978b3"
```

## 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-23 (score 37, +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-10-22 (score 36, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-10-15 (score 33, +27)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 67
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-10-13 (score 6)

First indexed and scored.

## MCP tools (2)

### `check_phone` (~57 tokens)

Validate a phone number via SureCheck numbering-plan metadata. Not live carrier, reachability, or ownership.

Input parameters:

- `country_code` (string): Optional 2-letter region
- `phone_number` (string, required): Number, ideally E.164 (+...)

### `check_email` (~33 tokens)

Validate an email via SureCheck syntax and DNS. Does not prove mailbox existence or delivery.

Input parameters:

- `email` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp#diagnostics

## Score history

- 2026-10-23: 37
- 2026-10-22: 36
- 2026-10-21: 33
- 2026-10-20: 33
- 2026-10-19: 33
- 2026-10-18: 33
- 2026-10-17: 33
- 2026-10-16: 33
- 2026-10-15: 33
- 2026-10-14: 6
- 2026-10-13: 6

## Common questions

### What is the SureCheck MCP server?

SureCheck MCP is listed in the public MCP registry as io.github.Killfear1/surecheck-mcp. Local stdio phone metadata and email syntax/DNS checks. Not live carrier or mailbox verification. This page covers its MCPB bundle (https://github.com/Killfear1/surecheck-mcp/releases/download/0.1.1/surecheck-mcp-0.1.1.mcpb).

### Is the SureCheck MCP server safe to use?

SureCheck MCP scores 37 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 SureCheck MCP server expose?

SureCheck MCP exposes 2 tools: check_phone, check_email. Their descriptions and schemas cost roughly 90 tokens of context every time the server is loaded.

## Links

- Repository: https://github.com/Killfear1/surecheck-mcp
- Changelog RSS feed: https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp.json
- HTML version of this page: https://verifymcp.io/servers/killfear1-surecheck-mcp/surecheck-mcp