Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Nalvorn Checks

REMOTE · TOOLS.NALVORN.TOP

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

69 Trust /100

Last scanned (18 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security69
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 911 tokens (~75/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +51
    • HTTPS: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
  • 19 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • HTTPS: fail → unverified ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tools.nalvorn.top/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nalvorn.top CN=YE1,O=Let's Encrypt,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA384 64e3807b262a509dc441051138dcf9eab16
SANs: *.nalvorn.top, nalvorn.top
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tools.nalvorn.top. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
nalvorn.top. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'none'; style-src 'unsafe-inline'; img-src 'self' data:; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tools.nalvorn.top/mcp Verified 200
http (plaintext) http://tools.nalvorn.top/mcp Served over HTTP 200
MCP tools · 12 exposed · ~864 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
domain_posture ~79

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.

NameTypeReqDescription
domainstringyesDomain name without scheme, for example example.com

No output schema declared.

No examples provided.

full_report ~74

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.

NameTypeReqDescription
urlstringyesFull URL with scheme, for example https://example.com/

No output schema declared.

No examples provided.

http_headers ~72

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.

NameTypeReqDescription
urlstringyesFull URL with scheme, for example https://example.com/

No output schema declared.

No examples provided.

json_schema_strict ~37

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

NameTypeReqDescription
schemaobjectyesJSON Schema document to validate against

No output schema declared.

No examples provided.

openapi_conformance ~75

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.

NameTypeReqDescription
openapi_urlstringyesPublic http(s) URL of an OpenAPI document to check

No output schema declared.

No examples provided.

package_check ~76

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.

NameTypeReqDescription
namestringyesPackage name as published, for example left-pad or requests

No output schema declared.

No examples provided.

payment_verdict ~113

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.

NameTypeReqDescription
expect_amountstring–expect_amount
expect_tostring–expect_to
min_confirmationsstring–min_confirmations
tokenstring–token
txstringyestx

No output schema declared.

No examples provided.

receipt_verify ~84

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.

NameTypeReqDescription
payloadobjectyesObject whose canonical JSON is the signed receipt payload
sha256stringyesExpected sha256 digest, hex, 64 characters

No output schema declared.

No examples provided.

ru_text_normalize ~47

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

NameTypeReqDescription
textstringyesText to normalise (Russian punctuation and spacing)

No output schema declared.

No examples provided.

site_ready ~77

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.

NameTypeReqDescription
urlstringyesFull URL with scheme, for example https://example.com/

No output schema declared.

No examples provided.

tls_cert ~70

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.

NameTypeReqDescription
hoststringyesHost name without scheme, for example example.com

No output schema declared.

No examples provided.

verify_manifest ~60

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

NameTypeReqDescription
filesobjectyesObject mapping file paths to actual sha256 digests
manifeststringyesObject mapping file paths to expected sha256 digests

No output schema declared.

No examples provided.

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.

remote · tools.nalvorn.top

# add to Claude Code
claude mcp add --transport http kerio-byte-nalvorn-checks 'https://tools.nalvorn.top/mcp'
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.