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.

NumeroClaw

REMOTE · API.NUMEROCLAW.COM

Order a personalized numerology reading, paid by the person and delivered by email.

+3 this week 71 Trust /100

Last scanned (12 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Entertainment and Games

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 Security66
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1377 tokens (~459/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

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

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

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

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

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 6 Nov 26 64

    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://api.numeroclaw.com/mcp/connect

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=numeroclaw.com CN=YE1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 5b73fe3598161308741680e4d12a7f0f181
SANs: *.numeroclaw.com, numeroclaw.com
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 secure

Validation of api.numeroclaw.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
numeroclaw.com. DS published 2371 13 Verified
api.numeroclaw.com. Verified address RRset verified with the apex keys
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 'self';base-uri 'self';font-src 'self' https: data:;style-src 'self' https: 'unsafe-inline';img-src 'self' https://numeroclaw.com data:;script-src 'self';script-src-attr 'none';object-src 'none';form-action 'self';frame-ancestors 'self';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.numeroclaw.com/mcp/connect Verified 200
http (plaintext) http://api.numeroclaw.com/mcp/connect HTTPS enforced 301 https://api.numeroclaw.com/mcp/connect
MCP tools · 3 exposed · ~1,278 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
create_order ~954

Creates an unpaid order for one NumeroClaw reading and returns a link to a NumeroClaw page where the person checks the order and pays. It is for when the person has seen and confirmed the product, the price, the email address and the details below. Creating the order charges nothing, and an unpaid order expires after 24 hours. Payment is taken at purchase and the reading is written afterwards. It is emailed to the address given: usually within a few hours and always within 6 hours. Readings are written for adults, so this is not for a reading about a child. One order covers one reading for one person, so a second order for the same person and reading is a second purchase. If a paid reading has not arrived in that time, the person can write to hello@numeroclaw.com with the order id. Inputs by product. theme: firstNames and lastNames exactly as on the birth record (middleNames optional), dateOfBirth and subjectGender. birthday_portrait: dateOfBirth, and optionally firstName to address the reading to. name_analysis: the birth name (firstNames, lastNames, middleNames optional) and no dateOfBirth; if the person uses a different name today, it goes in currentFirstNames, currentLastNames and currentMiddleNames, with currentNameContexts and currentNameScope. Every product needs email. Dates are YYYY-MM-DD. Names with the letter Y need yClassifications, one value per Y anywhere in the name, including at the end of a name, in reading order: first names, then middle names, then last names, and for name_analysis the birth name before the current name. A Y is a vowel sound when it sounds like the Y in Amy or Kelly, and a consonant sound when it starts a syllable and sounds like the Y in yes, as in Yolanda. The sound decides, not the position: Yvonne is said ee-von, so its Y is a vowel sound, and "Yolanda Kelly" gives ["consonant", "vowel"]. Each Y is worked out from how the name sounds and confirmed by the person in plain words, because most people cannot say whether a Y is a v…

NameTypeReqDescription
currentFirstNamesarray–name_analysis (optional): first names of the name used today, when it differs from the birth name.
currentLastNamesarray–name_analysis (optional): surnames of the name used today.
currentMiddleNamesarray–name_analysis (optional): middle names of the name used today.
currentNameContextsarray–name_analysis, with a current name: where that name is used.
currentNameScopestring–name_analysis, with a current name: how much it is used.
currentNameUsedSinceYearinteger–name_analysis (optional): the year the current name came into use.
dateOfBirthstring–Date of birth as YYYY-MM-DD. Required for theme and birthday_portrait; not used by name_analysis.
emailstringyesThe buyer's own email address, also for a gift. The payment confirmation and the private reading link are sent there.
firstNamestring–birthday_portrait (optional): the name the reading is addressed to.
firstNamesarray–theme and name_analysis: every birth first name, in order.
lastNamesarray–theme and name_analysis: every birth surname.
middleNamesarray–theme and name_analysis (optional): any additional birth names.
openingNotestring–Optional short personal note, up to 280 characters, printed at the start of the reading. It never changes the interpretation.
productstringyesWhich reading to buy: "theme", "birthday_portrait" or "name_analysis".
subjectGenderstring–theme only, where it is required: "female" or "male". Sets only the grammatical agreement in the written reading and changes no number.
yClassificationsarray–theme and name_analysis: one "vowel" or "consonant" per letter Y in the name, in reading order, confirmed by the person. Omitted when the name has no Y.

No output schema declared.

No examples provided.

get_order ~207

Returns the status of a NumeroClaw reading order. Use it when the person asks whether their order is paid or their reading is ready. Inputs: orderId and orderToken, both returned when the order is created. Returns the status (awaiting_payment, expired, paid, queued, processing, completed or failed), the amount, the payment link while the order is unpaid, how long it usually takes while it is being written, and a short message for the person. The reading itself is sent only by email, to the address given with the order. A reading that is still being written has not failed: it is usually ready within a few hours and always within 6 hours. A failed status means the reading could not be produced and the payment will be refunded after a person at NumeroClaw reviews it.

NameTypeReqDescription
orderIdstringyesThe order id returned when the order was created.
orderTokenstringyesThe private order token returned when the order was created.

No output schema declared.

No examples provided.

list_products ~117

Lists the numerology readings available from NumeroClaw: Theme, Name Analysis and Birthday Portrait. Use it when someone asks which readings are available, what they cost, or what details a reading needs. Takes no input. Returns, for each reading, its product id (theme, name_analysis or birthday_portrait), name, description, price in US dollars and any running sale, delivery time, refund terms, links to read about it and to a complete sample where one exists, whether it can be ordered now, and the details it requires.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the NumeroClaw MCP server?

NumeroClaw is a hosted endpoint at https://api.numeroclaw.com/mcp/connect, 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 · api.numeroclaw.com

# add to Claude Code
claude mcp add --transport http com-numeroclaw-readings 'https://api.numeroclaw.com/mcp/connect'
Common questions

What is the NumeroClaw MCP server?

NumeroClaw is an MCP server listed in the public MCP registry as com.numeroclaw/readings. Order a personalized numerology reading, paid by the person and delivered by email. This page covers its hosted endpoint (https://api.numeroclaw.com/mcp/connect).

Is the NumeroClaw MCP server safe to use?

NumeroClaw scores 71 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 NumeroClaw MCP server expose?

NumeroClaw exposes 3 tools: list_products, create_order, get_order. Their descriptions and schemas cost roughly 1,278 tokens of context every time the server is loaded.

Does the NumeroClaw MCP server require authentication?

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

Is the NumeroClaw MCP server still maintained?

NumeroClaw 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 NumeroClaw MCP server?

VerifyMCP ran 13 checks on NumeroClaw, 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.