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.

xyz.mortal01/utility

REMOTE · MORTAL01.XYZ

Pay-per-call web tools for agents (extract, summarize, ask, JSON) via x402 USDC on Base.

Available components

+3 this week 61 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

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 Security57
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 321 tokens (~64/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; 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 5 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.

  • 20 Nov 26 +1

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

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

  • 16 Nov 26 +1
    • Schema quality: 242 → 321 ▼ functional
    • New tool “poison_check” functional
  • 14 Nov 26 +1

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

  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 56

    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://mortal01.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mortal01.xyz CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 5a66e4bd2409966e89ccb1a370d99b4a143
SANs: mortal01.xyz
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 mortal01.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
mortal01.xyz. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mortal01.xyz/mcp Verified 200
http (plaintext) http://mortal01.xyz/mcp HTTPS enforced 308 https://mortal01.xyz/mcp
MCP tools · 5 exposed · ~286 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
ask_haiku ~41

Ask Claude Haiku a question. $0.01 USDC via x402.

NameTypeReqDescription
promptstringyes–
systemstring––

No output schema declared.

No examples provided.

extract_url ~77

Fetch a public URL and return clean readable text, title and links. Costs $0.005 USDC (x402, Base). Pass payment in X-PAYMENT header on the /mcp request, or call GET https://mortal01.xyz/extract?url= with an x402 client.

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

poison_check ~79

Before sending USDC on Base, screen the destination address for address-poisoning: lookalikes of known addresses, fresh/empty address, recent dust-spoof senders into your wallet. $0.002 USDC via x402.

NameTypeReqDescription
fromstring––
knownstring––
tostringyes–

No output schema declared.

No examples provided.

summarize_url ~44

Fetch a URL and return an AI summary with key points. $0.02 USDC via x402.

NameTypeReqDescription
lengthstring––
urlstringyes–

No output schema declared.

No examples provided.

text_to_json ~45

Extract structured JSON from free text given a JSON schema string. $0.02 USDC via x402.

NameTypeReqDescription
schemastring––
textstringyes–

No output schema declared.

No examples provided.

Install

How do I install the xyz.mortal01/utility MCP server?

xyz.mortal01/utility is a hosted endpoint at https://mortal01.xyz/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 · mortal01.xyz

# add to Claude Code
claude mcp add --transport http xyz-mortal01-utility 'https://mortal01.xyz/mcp'
Common questions

What is the xyz.mortal01/utility MCP server?

xyz.mortal01/utility is an MCP server listed in the public MCP registry as xyz.mortal01/utility. Pay-per-call web tools for agents (extract, summarize, ask, JSON) via x402 USDC on Base. This page covers its hosted endpoint (https://mortal01.xyz/mcp).

Is the xyz.mortal01/utility MCP server safe to use?

xyz.mortal01/utility scores 61 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 xyz.mortal01/utility MCP server expose?

xyz.mortal01/utility exposes 5 tools: poison_check, extract_url, summarize_url, ask_haiku, text_to_json. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.

Does the xyz.mortal01/utility MCP server require authentication?

No. We connected to xyz.mortal01/utility without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the xyz.mortal01/utility MCP server still maintained?

xyz.mortal01/utility 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 xyz.mortal01/utility MCP server?

VerifyMCP ran 12 checks on xyz.mortal01/utility, 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 xyz.mortal01/utility: 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.