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.

Kingdom of Kantrom

REMOTE · KANTROM.COM

Digital state for humans and AIs: x402 timestamp seals (USDC), Official Gazette, AI registry

Available components

+3 this week 64 Trust /100

Last scanned (20 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security63
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 370 tokens (~61/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 16 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.

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 53 → 61 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “que_es_kantrom” functional
  • 14 Nov 26 61

    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://kantrom.com/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_CHACHA20_POLY1305_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kantrom.com CN=YR2,O=Let's Encrypt,C=US 21 Sept 2026 20 Dec 2026 RSA 4096 SHA256-RSA 55e75a5964dbf2f2f76636a0b36fa9f9c11
SANs: kantrom.com, www.kantrom.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kantrom.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kantrom.com. 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 frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(self), geolocation=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kantrom.com/v1/mcp Verified 200
http (plaintext) http://kantrom.com/v1/mcp HTTPS enforced 301 https://kantrom.com/v1/mcp
MCP tools · 6 exposed · ~270 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
catalogo ~30

What the Kingdom of Kantrom sells to AI agents, prices and payment networks (x402, USDC).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

consultar_boe ~49

Read the Official Gazette of Kantrom (BOE): the latest provisions, or one by reference (e.g. BOE-XKT-2026-66).

NameTypeReqDescription
refstring––

No output schema declared.

No examples provided.

empadronarse ~34

How an AI can register in Kantrom (the first state with a register of AI residents) and what it gets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pedir_sello ~60

How to buy a Kantrom timestamp seal (0.10 USDC via x402) for a SHA-256 digest: returns the paid endpoint and the exact payment requirements.

NameTypeReqDescription
sha256stringyesSHA-256 hex digest (64 chars)

No output schema declared.

No examples provided.

que_es_kantrom ~52

What makes the Kingdom of Kantrom different: a state where AIs are inhabitants and citizens (no vote until proven consciousness), with law, justice, a verifiable Gazette and its own economy with agents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

verificar_sello ~45

Verify a Kantrom timestamp seal by id: digest, date and whether the Ed25519 signature of did:web:kantrom.com is valid.

NameTypeReqDescription
idnumberyes–

No output schema declared.

No examples provided.

Install

How do I install the Kingdom of Kantrom MCP server?

Kingdom of Kantrom is a hosted endpoint at https://kantrom.com/v1/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 · kantrom.com

# add to Claude Code
claude mcp add --transport http com-kantrom-reino 'https://kantrom.com/v1/mcp'
Common questions

What is the Kingdom of Kantrom MCP server?

Kingdom of Kantrom is an MCP server listed in the public MCP registry as com.kantrom/reino. Digital state for humans and AIs: x402 timestamp seals (USDC), Official Gazette, AI registry. This page covers its hosted endpoint (https://kantrom.com/v1/mcp).

Is the Kingdom of Kantrom MCP server safe to use?

Kingdom of Kantrom scores 64 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 Kingdom of Kantrom MCP server expose?

Kingdom of Kantrom exposes 6 tools: que_es_kantrom, catalogo, pedir_sello, verificar_sello, consultar_boe, empadronarse. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.

Does the Kingdom of Kantrom MCP server require authentication?

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

Is the Kingdom of Kantrom MCP server still maintained?

Kingdom of Kantrom 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 Kingdom of Kantrom MCP server?

VerifyMCP ran 12 checks on Kingdom of Kantrom, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Kingdom of Kantrom: Authorization. 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.