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.

com.nomadorix-holdings/growth-desk

REMOTE · MCP.NOMADORIX-HOLDINGS.COM

Read-only funnel diagnosis, revenue KPI planning and business assumption calculations.

68 Trust /100

Last scanned (22 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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 Usability53
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1227 tokens (~409/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 Management20
  • Stability observed for 6 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 (12)

  • TLS certificate
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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

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

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 65

    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://mcp.nomadorix-holdings.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nomadorix-holdings.com CN=WE1,O=Google Trust Services,C=US 15 Nov 2026 13 Feb 2027 ECDSA 256 ECDSA-SHA256 2ebbd3052de64783130201cf1cd5195e
SANs: nomadorix-holdings.com, mcp.nomadorix-holdings.com, *.mcp.nomadorix-holdings.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nomadorix-holdings.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
nomadorix-holdings.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
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nomadorix-holdings.com/mcp Verified 200
http (plaintext) http://mcp.nomadorix-holdings.com/mcp Inconclusive 405
MCP tools · 3 exposed · ~1,192 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
check_business_plan_assumptions ~610

Review unit economics using acquisition cost, monthly customer revenue, gross margin and churn; optionally include growth and cash runway pairs. Returns lifetime gross profit, acquisition-cost multiple, payback months, optional projections and general reference cautions. 計画の前提を見直すために獲得単価・月売上・粗利率・月解約率と任意の成長・資金を入力し、粗利・倍率・回収月数・注意点を返します。 Set language to 'en' for English output.

NameTypeReqDescription
cash_on_handnumber–Available cash, 0–1 trillion; same currency unit as all other monetary inputs. Specify together with monthly_burn. / 手元資金。0〜1兆。金額はすべて同じ通貨単位。monthly_burnと対で指定。
customer_acquisition_costnumberyesAcquisition cost per customer, 0–1 trillion; all monetary inputs use the same currency unit. / 顧客獲得単価。0〜1兆。金額はすべて同じ通貨単位。
gross_margin_percentnumberyesGross margin percentage, 0–100; 10 means 10%. / 粗利率。0〜100の百分率。10は10%。
growth_monthsinteger–Growth duration, 1–60 months; specify together with monthly_growth_percent. / 成長の月数(1〜60)。monthly_growth_percentと対で指定。
languagestring–Output language: ja (default) or en. / 出力言語。既定は日本語(ja)、英語はen。
monthly_burnnumber–Monthly net cash outflow, 0–1 trillion; same currency unit as all other monetary inputs. Specify together with cash_on_hand. / 月の純資金流出。0〜1兆。金額はすべて同じ通貨単位。cash_on_handと対で指定。
monthly_churn_percentnumberyesMonthly churn percentage, greater than 0 and at most 100; 10 means 10%. / 月解約率。0より大きく100以下の百分率。10は10%。
monthly_growth_percentnumber–Relative monthly growth percentage, -100–1000; 10 means 10%. Specify together with growth_months. / 月の相対成長率。−100〜1000の百分率。10は10%。growth_monthsと対で指定。
monthly_revenue_per_customernumberyesMonthly revenue per customer, 0–1 trillion; all monetary inputs use the same currency unit. / 顧客1人の月売上。0〜1兆。金額はすべて同じ通貨単位。
NameTypeReqDescription
acquisition_cost_multiple–yesLifetime gross profit divided by acquisition cost, or null. / 生涯粗利を獲得単価で割った倍率。算出不可はnull。
cash_runway_months––Cash divided by monthly net cash outflow, or null. / 手元資金を月の純資金流出で割った月数。算出不可はnull。
growth_multipliernumber–Compound growth multiplier over the specified duration. / 指定月数の複利成長倍率。
lifetime_gross_profitnumberyesLifetime gross profit per customer, in the input currency unit. / 入力と同じ通貨単位での顧客生涯の粗利。
monthly_gross_profitnumberyesMonthly gross profit per customer, in the input currency unit. / 入力と同じ通貨単位での顧客1人の月粗利。
payback_months–yesAcquisition cost divided by monthly gross profit, or null. / 獲得単価を月粗利で割った回収月数。算出不可はnull。
summarystringyesCalculation assumptions and interpretation. / 計算の前提と結果の説明。
warningsarrayyesData cautions and general reference thresholds. / データの注意点と一般的な目安。

No examples provided.

diagnose_funnel_bottleneck ~209

Diagnose conversion bottlenecks using 2–10 named stage counts and an optional relative improvement percentage. Returns conversion rates, the lowest-rate transition, ranked final-stage gains and data cautions. 集客の改善候補を選ぶために段の名前・人数と改善率を入力し、通過率・最低の段・最後の人数の増分・注意点を返します。 Set language to 'en' for English output.

NameTypeReqDescription
improvement_percentnumber–Relative improvement percentage, 1–100; 10 means a 10% relative increase. / 相対改善率(1〜100)。10は現在の率を相対で10%改善。
languagestring–Output language: ja (default) or en. / 出力言語。既定は日本語(ja)、英語はen。
stagesarrayyesOrdered funnel stages. / 上流から順に並べた段。
NameTypeReqDescription
bottleneck–yesLowest-rate transition; earliest on ties, null if unavailable. / 最低通過率の段。同率は先の段。算出不可はnull。
improvement_percentnumberyesRelative improvement percentage used. / 試算に使った相対改善率。
improvementsarrayyesIndependent improvement scenarios ranked by gain or reduction. / 増分または減少数の大きい順の独立した改善試算。
summarystringyesCalculation assumptions and interpretation. / 計算の前提と結果の説明。
transitionsarrayyesConversion rates between adjacent stages. / 隣接する段の通過率。
warningsarrayyesData cautions and general reference thresholds. / データの注意点と一般的な目安。

No examples provided.

reverse_kpi_from_revenue_target ~373

Plan required volumes from a positive revenue target, unit price, 1–36 months and 1–8 ordered conversion rates. The target is for the whole period, not monthly. Returns rounded-up stage requirements, monthly averages and upstream reductions when each rate improves by 10% relatively. 売上目標の達成に必要な人数を整理するために目標・単価・期間・上流からの率を入力し、段ごとの必要数と改善時の減少数を返します。 Set language to 'en' for English output.

NameTypeReqDescription
languagestring–Output language: ja (default) or en. / 出力言語。既定は日本語(ja)、英語はen。
period_monthsinteger–Whole-period duration in months, 1–36. / 対象期間の月数(1〜36)。
ratesarrayyesOrdered, connected stage conversion rates; no repeated stages. / 上流から連続する段の通過率。同じ段の繰り返しは不可。
target_revenuenumberyesRevenue target for the whole period, not monthly; greater than 0 and at most 1 trillion. All monetary inputs use the same currency unit. / 期間全体の売上目標(月額ではない)。0より大きく1兆以下。金額はすべて同じ通貨単位。
unit_pricenumberyesRevenue per sale, greater than 0 and at most 1 trillion; all monetary inputs use the same currency unit. / 成約単価。0より大きく1兆以下。金額はすべて同じ通貨単位。
NameTypeReqDescription
improvementsarrayyesIndependent improvement scenarios ranked by gain or reduction. / 増分または減少数の大きい順の独立した改善試算。
period_monthsintegeryesWhole-period duration in months. / 対象期間の月数。
required_salesintegeryesSales required for the whole period, rounded up. / 期間全体に必要な成約数(切り上げ)。
stagesarrayyesRequired counts by stage. / 段ごとの必要人数。
summarystringyesCalculation assumptions and interpretation. / 計算の前提と結果の説明。

No examples provided.

Install

How do I install the com.nomadorix-holdings/growth-desk MCP server?

com.nomadorix-holdings/growth-desk is a hosted endpoint at https://mcp.nomadorix-holdings.com/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 · mcp.nomadorix-holdings.com

# add to Claude Code
claude mcp add --transport http com-nomadorix-holdings-growth-desk 'https://mcp.nomadorix-holdings.com/mcp'
Common questions

What is the com.nomadorix-holdings/growth-desk MCP server?

com.nomadorix-holdings/growth-desk is an MCP server listed in the public MCP registry as com.nomadorix-holdings/growth-desk. Read-only funnel diagnosis, revenue KPI planning and business assumption calculations. This page covers its hosted endpoint (https://mcp.nomadorix-holdings.com/mcp).

Is the com.nomadorix-holdings/growth-desk MCP server safe to use?

com.nomadorix-holdings/growth-desk scores 68 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 com.nomadorix-holdings/growth-desk MCP server expose?

com.nomadorix-holdings/growth-desk exposes 3 tools: diagnose_funnel_bottleneck, reverse_kpi_from_revenue_target, check_business_plan_assumptions. Their descriptions and schemas cost roughly 1,192 tokens of context every time the server is loaded.

Does the com.nomadorix-holdings/growth-desk MCP server require authentication?

No. We connected to com.nomadorix-holdings/growth-desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.nomadorix-holdings/growth-desk MCP server still maintained?

com.nomadorix-holdings/growth-desk 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 com.nomadorix-holdings/growth-desk MCP server?

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