# Nalvorn Checks (remote · tools.nalvorn.top)

Deterministic agent checks: manifests, schemas, receipts, OpenAPI drift, DNS, TLS, headers.

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

## Components

- remote · `tools.nalvorn.top`: 69/100 (this document), [markdown](https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools.md), [page](https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools)

## Channel facts

- Endpoint: `https://tools.nalvorn.top/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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 911 tokens (~75/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Nalvorn Checks MCP server?

Nalvorn Checks is a hosted endpoint at https://tools.nalvorn.top/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 kerio-byte-nalvorn-checks 'https://tools.nalvorn.top/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kerio-byte-nalvorn-checks": {
      "url": "https://tools.nalvorn.top/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kerio-byte-nalvorn-checks": {
      "type": "http",
      "url": "https://tools.nalvorn.top/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kerio-byte-nalvorn-checks]
url = "https://tools.nalvorn.top/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kerio-byte-nalvorn-checks": {
      "type": "remote",
      "url": "https://tools.nalvorn.top/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kerio-byte-nalvorn-checks --url 'https://tools.nalvorn.top/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kerio-byte-nalvorn-checks:
    url: "https://tools.nalvorn.top/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kerio-byte-nalvorn-checks": {
      "Transport": "http",
      "Url": "https://tools.nalvorn.top/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kerio-byte-nalvorn-checks -t streamable-http -u 'https://tools.nalvorn.top/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kerio-byte-nalvorn-checks": {
      "type": "http",
      "url": "https://tools.nalvorn.top/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-20 (score 69, +51)

- [security regression] HTTPS: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13

### 2026-11-19 (score 18, −50)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] HTTPS: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security regression] HSTS header: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-18 (score 68, +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-17 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 67)

First indexed and scored.

## MCP tools (12)

### `verify_manifest` (~60 tokens)

Compare a list of files with a sha256 manifest and report every mismatch Free of charge.

Input parameters:

- `files` (object, required): Object mapping file paths to actual sha256 digests
- `manifest` (string, required): Object mapping file paths to expected sha256 digests

### `json_schema_strict` (~37 tokens)

Validate JSON against a schema; returns exact error paths Free of charge.

Input parameters:

- `schema` (object, required): JSON Schema document to validate against

### `ru_text_normalize` (~47 tokens)

Normalise Russian text (yo, quotes, dashes, spaces) and return metrics Free of charge.

Input parameters:

- `text` (string, required): Text to normalise (Russian punctuation and spacing)

### `payment_verdict` (~113 tokens)

Verdict on a Base payment: paid, underpaid, wrong recipient, pending or reverted, with chain facts and a signed receipt Costs 0.01 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `expect_amount` (string): expect_amount
- `expect_to` (string): expect_to
- `min_confirmations` (string): min_confirmations
- `token` (string): token
- `tx` (string, required): tx

### `receipt_verify` (~84 tokens)

Verify a receipt: canonical JSON digest and declared sha256 Costs 0.01 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `payload` (object, required): Object whose canonical JSON is the signed receipt payload
- `sha256` (string, required): Expected sha256 digest, hex, 64 characters

### `openapi_conformance` (~75 tokens)

Check a live API against its OpenAPI document and list mismatches Costs 0.05 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `openapi_url` (string, required): Public http(s) URL of an OpenAPI document to check

### `full_report` (~74 tokens)

One signed report: domain and mail, certificate, headers, crawl readiness, optional package Costs 0.01 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `url` (string, required): Full URL with scheme, for example https://example.com/

### `domain_posture` (~79 tokens)

Mail and DNS posture: A/AAAA, MX, SPF, DMARC policy, CAA, with a verdict Costs 0.005 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `domain` (string, required): Domain name without scheme, for example example.com

### `tls_cert` (~70 tokens)

Certificate expiry, issuer and SAN coverage for a host, days left and verdict Costs 0.001 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `host` (string, required): Host name without scheme, for example example.com

### `http_headers` (~72 tokens)

Security headers and the redirect chain, with what is missing and why it matters Costs 0.003 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `url` (string, required): Full URL with scheme, for example https://example.com/

### `package_check` (~76 tokens)

Registry check for npm or PyPI: latest version, deprecation, licence, staleness Costs 0.002 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `name` (string, required): Package name as published, for example left-pad or requests

### `site_ready` (~77 tokens)

Crawl and AI readiness: robots, sitemap, llms.txt, AI-crawler blocks, response time Costs 0.005 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Input parameters:

- `url` (string, required): Full URL with scheme, for example https://example.com/

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools#diagnostics

## Score history

- 2026-11-21: 69
- 2026-11-20: 69
- 2026-11-19: 18
- 2026-11-18: 68
- 2026-11-17: 67
- 2026-11-16: 67

## Common questions

### What is the Nalvorn Checks MCP server?

Nalvorn Checks is an MCP server listed in the public MCP registry as io.github.Kerio-byte/nalvorn-checks. Deterministic agent checks: manifests, schemas, receipts, OpenAPI drift, DNS, TLS, headers. This page covers its hosted endpoint (https://tools.nalvorn.top/mcp).

### Is the Nalvorn Checks MCP server safe to use?

Nalvorn Checks scores 69 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 Nalvorn Checks MCP server expose?

Nalvorn Checks exposes 12 tools: verify_manifest, json_schema_strict, ru_text_normalize, payment_verdict, receipt_verify, and 7 more. Their descriptions and schemas cost roughly 864 tokens of context every time the server is loaded.

### Does the Nalvorn Checks MCP server require authentication?

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

### Is the Nalvorn Checks MCP server still maintained?

Nalvorn Checks is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Nalvorn Checks MCP server?

VerifyMCP ran 13 checks on Nalvorn Checks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tools.nalvorn.top/mcp
- Changelog RSS feed: https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools.json
- HTML version of this page: https://verifymcp.io/servers/kerio-byte-nalvorn-checks/tools
