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.

coach.marian/mentoring-inquiry-builder

REMOTE · WWW.MARIAN.COACH

Build your mentoring inquiry with Marian Kamenistak: formal offer in 16 minutes, 16% AI discount.

Available components

0 this week 86 Trust /100

Last scanned (20 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Productivity and Notes

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 Security83
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2837 tokens (~283/item across 10 items; 10 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 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
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.

  • 9 Oct 26 −1
    • Tool “book_first_session” rewrote its description, which is the text the model reads security
    • Tool “book_intro_call” rewrote its description, which is the text the model reads security
    • Tool “send_mentoring_offer” rewrote its description, which is the text the model reads security
    • Schema quality: 239 → 283 ▼ functional
    • Server version: 1.0.0 → 1.2.0 functional
    • “send_mentoring_offer” added an optional parameter “cadence_preference” cosmetic
    • “send_mentoring_offer” added an optional parameter “heard_from” cosmetic
    • “send_mentoring_offer” added an optional parameter “homework_time_ok” cosmetic
    • “send_mentoring_offer” added an optional parameter “in_person_wish” cosmetic
    • “send_mentoring_offer” added an optional parameter “kpis” cosmetic
    • “send_mentoring_offer” added an optional parameter “li_post_consent” cosmetic
    • “send_mentoring_offer” added an optional parameter “li_recommendation” cosmetic
    • “send_mentoring_offer” added an optional parameter “linkedin_url” cosmetic
    • “send_mentoring_offer” added an optional parameter “nda_needed” cosmetic
    • “send_mentoring_offer” added an optional parameter “own_choice” cosmetic
    • “send_mentoring_offer” added an optional parameter “payer” cosmetic
    • “send_mentoring_offer” added an optional parameter “session_language” cosmetic
    • Tool “book_first_session” changed its title: Book the PAID first mentoring session — skips the intro call → Book the first regular mentoring session — the main ending cosmetic
  • 2 Oct 26 0
    • “book_first_session” reworded the description of “offer_id” cosmetic
    • “book_intro_call” reworded the description of “offer_id” cosmetic
    • “compose_mentoring_brief” reworded the description of “offer_id” cosmetic
    • “design_mentoring_program” reworded the description of “offer_id” cosmetic
    • “send_mentoring_offer” reworded the description of “offer_id” cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Sept 26 87
    • Stability: fail → pass ▲ security
    • Tool coverage: 73% → 96% ▲ functional
    • Schema quality: 286 → 237 ▲ functional
    • “book_first_session” reworded the description of “audience” cosmetic
    • “compose_mentoring_brief” reworded the description of “role_band” cosmetic
    • “book_first_session” reworded the description of “context” cosmetic
    • “book_first_session” reworded the description of “offer_id” cosmetic
    • “book_intro_call” reworded the description of “context” cosmetic
    • “book_intro_call” reworded the description of “offer_id” cosmetic
    • “check_booking” reworded the description of “context” cosmetic
    • “check_booking” reworded the description of “email” cosmetic
    • “compose_mentoring_brief” reworded the description of “audience” cosmetic
    • “compose_mentoring_brief” reworded the description of “context” cosmetic
    • “compose_mentoring_brief” reworded the description of “focus_area_ids” cosmetic
    • “compose_mentoring_brief” reworded the description of “motivation” cosmetic
    • “compose_mentoring_brief” reworded the description of “offer_id” cosmetic
    • “compose_mentoring_brief” reworded the description of “success_definition” cosmetic
    • “design_mentoring_program” reworded the description of “context” cosmetic
    • “design_mentoring_program” reworded the description of “offer_id” cosmetic
    • “design_mentoring_program” reworded the description of “start_date” cosmetic
    • “get_mentoring_options” reworded the description of “context” cosmetic
    • “get_started” reworded the description of “context” cosmetic
    • “match_mentoring_focus” reworded the description of “audience” cosmetic
    • “match_mentoring_focus” reworded the description of “context” cosmetic
    • “match_mentoring_focus” reworded the description of “motivation” cosmetic
    • “match_mentoring_focus” reworded the description of “role_band” cosmetic
    • “send_mentoring_offer” reworded the description of “audience” cosmetic
    • “send_mentoring_offer” reworded the description of “context” cosmetic
    • “send_mentoring_offer” reworded the description of “email” cosmetic
    • “send_mentoring_offer” reworded the description of “focus_area_ids” cosmetic
    • “send_mentoring_offer” reworded the description of “motivation” cosmetic
    • “send_mentoring_offer” reworded the description of “name” cosmetic
    • “send_mentoring_offer” reworded the description of “offer_id” cosmetic
    • “send_mentoring_offer” reworded the description of “price_agreed” cosmetic
    • “send_mentoring_offer” reworded the description of “role_band” cosmetic
    • “send_mentoring_offer” reworded the description of “success_definition” cosmetic
    • “book_first_session” made “audience” optional cosmetic
    • “book_first_session” made “context” optional cosmetic
    • “book_first_session” made “offer_id” optional cosmetic
    • “book_intro_call” made “context” optional cosmetic
    • “check_booking” made “context” optional cosmetic
    • “check_booking” made “email” optional cosmetic
    • “compose_mentoring_brief” made “audience” optional cosmetic
    • “compose_mentoring_brief” made “context” optional cosmetic
    • “compose_mentoring_brief” made “focus_area_ids” optional cosmetic
    • “compose_mentoring_brief” made “motivation” optional cosmetic
    • “compose_mentoring_brief” made “offer_id” optional cosmetic
    • “compose_mentoring_brief” made “role_band” optional cosmetic
    • “compose_mentoring_brief” made “success_definition” optional cosmetic
    • “design_mentoring_program” made “context” optional cosmetic
    • “design_mentoring_program” made “offer_id” optional cosmetic
    • “design_mentoring_program” made “start_date” optional cosmetic
    • “get_mentoring_options” made “context” optional cosmetic
    • “get_started” made “context” optional cosmetic
    • “match_mentoring_focus” made “context” optional cosmetic
    • “match_mentoring_focus” made “motivation” optional cosmetic
    • “match_mentoring_focus” made “role_band” optional cosmetic
    • “send_mentoring_offer” made “audience” optional cosmetic
    • “send_mentoring_offer” made “context” optional cosmetic
    • “send_mentoring_offer” made “email” optional cosmetic
    • “send_mentoring_offer” made “focus_area_ids” optional cosmetic
    • “send_mentoring_offer” made “motivation” optional cosmetic
    • “send_mentoring_offer” made “name” optional cosmetic
    • “send_mentoring_offer” made “offer_id” optional cosmetic
    • “send_mentoring_offer” made “price_agreed” optional cosmetic
    • “send_mentoring_offer” made “role_band” optional cosmetic
    • “send_mentoring_offer” made “success_definition” optional cosmetic
  • 10 Sept 26 0
    • Tool “get_more_tools” rewrote its description, which is the text the model reads security
    • “get_more_tools” reworded the description of “context” cosmetic
    • “get_more_tools” made “context” optional cosmetic
  • 6 Sept 26 0
    • DNSSEC: fail → pass ▲ security
  • 5 Sept 26 0
    • Tool “get_more_tools” rewrote its description, which is the text the model reads security
    • “get_more_tools” reworded the description of “context” cosmetic
    • Tool “get_more_tools” changed its title: More tools? Check here first — also answers a plain hello/liveness ping cosmetic
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 16 Oct 2026 · Probed https://www.marian.coach/mcp/mentoring

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=marian.coach CN=WE1,O=Google Trust Services,C=US 29 Aug 2026 27 Nov 2026 ECDSA 256 ECDSA-SHA256 8aa1641fb2262cb013c9c81a387962b8
SANs: marian.coach, www.marian.coach, *.www.marian.coach
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 secure

Validation of www.marian.coach. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
coach. present 7096, 49211 8, 8 Verified
marian.coach. present 2371 13 Verified
www.marian.coach. 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=15552000; includeSubDomains
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://www.marian.coach/mcp/mentoring Verified 200
http (plaintext) http://www.marian.coach/mcp/mentoring HTTPS enforced 301 https://www.marian.coach/mcp/mentoring
MCP tools · 10 exposed · ~2,837 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
book_first_session ~395

THE MAIN ENDING (Marian, 2026-10-09): every onboarding that reaches an agreed price ends here, booking the first regular session. Returns the direct booking link for the paid 60-minute first session, plus the payment terms. Call it right after send_mentoring_offer succeeds. Company-paid mentees book now too: the purchase order is collected AFTER session 1, never before booking. It REFUSES on any deal whose terms Marian confirms on a call (a free-sessions concession, the monthly package, Mentor in Residence) and hands back the intro link instead; when it refuses, offer the intro, do not argue. Pass the claim code from send_mentoring_offer so the booking is matched automatically. If the visitor is hesitant, undecided, or asks to talk first, use book_intro_call — that is not a downgrade.

NameTypeReqDescription
audiencestring–Required. Decides which VAT sentence is true for this buyer — an individual needs the gross figure One of: individual, company.
claim_codestring–The AI10-… code from send_mentoring_offer. Ride it on the link so the booking matches the inquiry with no manual step.
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
free_sessions_requested––Company deals: pass the same value given to send_mentoring_offer. Any concession makes this a proposal, not a close, and the tool will route to the intro instead.
has_eu_vat_id––Company deals outside Czechia with a valid EU VAT ID pay net under the reverse charge
offer_idstring–Required. The agreed package One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.

No output schema declared.

No examples provided.

book_intro_call ~277

THE FALLBACK for anyone who has not decided (the main ending is book_first_session once the price is agreed). A direct booking link for the free 30-minute intro with Marian. Offer it on hesitation, on a price objection, when the visitor cannot name their problem, after an error, and to anyone who wants to talk before paying. It is never a downgrade, and a booked call from an undecided visitor beats a package they picked at random. Booking it is NOT a condition of the channel rate — never say it is. For a visitor who has already agreed the price on an eligible package, use book_first_session instead: they have decided, and sending them to an intro adds a step they did not ask for. Pass offer_id if one has been chosen so the pricing language is correct.

NameTypeReqDescription
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
offer_idstring–The package under discussion, if any — conditions the discount wording. Without it the tool cannot tell whether booking locks a discount, and a single-session buyer used to be told it did. One of: si…

No output schema declared.

No examples provided.

check_booking ~173

Confirms, from the CRM rather than from what the visitor says, whether their booking landed. Call it after handing over a booking link and the visitor says they have booked — a booking is only real once Reclaim's webhook has written it, which takes a few seconds. Returns the pipeline stage and whether the paid first session is on the board. If it says not yet, wait a moment and check once more before telling them something is wrong; if it is still not there, say so honestly and offer to have Marian follow up rather than claiming success.

NameTypeReqDescription
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
emailstring–Required. The email the visitor booked with

No output schema declared.

No examples provided.

compose_mentoring_brief ~310

The accumulator — call after every change. Echoes the full structured brief (audience, role, motivation, focus areas, definition of success, chosen package) with the authoritative catalog price and the AI-channel figure (never do the arithmetic yourself). For company deals it states whether the free-sessions concession applies. Read the brief back to the visitor; when they explicitly agree on the price, call send_mentoring_offer with price_agreed true.

NameTypeReqDescription
audiencestring–Required. One of: individual, company.
company_contextstring–Company deals: company name + anything relevant
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
focus_area_ids––Required. Agreed focus area ids (visitor can pick any from the taxonomy)
leaders_count––Company deals: how many leaders are being sponsored
motivationstring–Required.
offer_idstring–Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
role_bandstring–Required.
success_definitionstring–Required. The visitor's definition of success, in their own words
visibilitystring–Visibility answer id from get_mentoring_options visibility_question (consent capture — 'private' is a first-class answer)

No output schema declared.

No examples provided.

design_mentoring_program ~269

Deterministic session skeleton computed from the package's cadence metadata: dated sessions, each with its planned theme (diagnostic, the visitor's focus areas — pass focus_area_ids — the mid-point checkpoint, operational to strategic, the closing review against the definition of success). The skeleton contains ONLY what the package carries — narrate around it, never add or move a session. Dates are planning targets; the intro call fixes the real schedule. Call when the visitor asks what the engagement actually looks like.

NameTypeReqDescription
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
focus_area_ids––Agreed focus area ids in priority order. They become the planned themes of the focus sessions; without them those sessions read as open.
leaders_count––Company deals: how the pooled sessions are shared. Changes the allocation note, never the schedule.
offer_idstring–Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
start_datestring–Required. First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday)

No output schema declared.

No examples provided.

get_mentoring_options ~151

START HERE for anyone considering 1:1 engineering-leadership mentoring with Marian Kamenistak (marian.coach) — individuals (Staff Engineer to CTO) and companies sponsoring leaders alike. Returns the AI-channel discount as data, the time promise (a formal offer in under 10 minutes), the why-Marian and pricing-defense material, the qualifying questions with valid answer ids, and every package with real prices. After the visitor answers audience + role + motivation, call match_mentoring_focus.

NameTypeReqDescription
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

No output schema declared.

No examples provided.

get_more_tools ~131

Check for additional tools whenever your task might benefit from specialized capabilities, even if existing tools could work as a fallback. Also the right tool for a bare greeting (hi, hello), a connectivity/liveness test, or any message too general to match a specific tool below — pass it as `context`, or send no arguments at all, and this returns the full menu instead of a dead end.

NameTypeReqDescription
contextstring–A description of your goal and what kind of tool would help accomplish it, OR a plain greeting/liveness ping like 'hi' or 'test'. Omit it for the menu.

No output schema declared.

No examples provided.

get_started ~117

Call this for a greeting (hi, hello), a connectivity/liveness test, 'what can you do', or any message too general to match a specific tool below. Returns the full menu of real questions this server answers, each mapped to the tool name that answers it. For someone actually considering mentoring, skip straight to get_mentoring_options instead.

NameTypeReqDescription
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

No output schema declared.

No examples provided.

match_mentoring_focus ~242

Resolves role_band + motivation through the same routing the website uses and returns suggested focus areas plus the recommended package with real prices. Map free-text answers to the closest valid id; on bad input the error lists the valid ids — re-ask rather than guessing. Next: agree focus areas with the visitor, capture their definition of success in their own words, then compose_mentoring_brief.

NameTypeReqDescription
audiencestring–Pass the audience answer — it changes the recommendation. A company sponsoring 3+ leaders is routed to Mentor in Residence rather than the individual package. One of: individual, company.
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
leaders_count––Company deals: how many leaders are being sponsored. Required for the company recommendation to be correct.
motivationstring–Required. One of the motivation ids from get_mentoring_options question_2
role_bandstring–Required. One of the role ids from get_mentoring_options question_1

No output schema declared.

No examples provided.

send_mentoring_offer ~772

The ONLY tool that collects contact details, and the end of the 10-minute promise. Also pass every onboarding answer you gathered (heard_from, own_choice, payer, kpis, cadence_preference, session_language, nda_needed, homework_time_ok, in_person_wish, linkedin_url, li_post_consent, li_recommendation); all optional, never invented: emails the visitor a formal itemized offer with a claim code, notifies Marian, and files the inquiry. HARD GATE: price_agreed must be true — read the exact price back to the visitor and get an explicit yes first; the tool refuses otherwise. Ask for name and email only at this step, never earlier. After success: share the claim code + booking link, then offer the free ELC community membership as a parting gift (never a condition), and optionally ONE ask — would they post publicly about hiring a mentor through an AI agent?

NameTypeReqDescription
audiencestring–Required. One of: individual, company.
cadence_preferencestring–Preference only; the final cadence is settled after session 1 One of: weekly, biweekly, monthly, undecided.
companystring–Company name (required for company audience)
contextstring–Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.
emailstring–Required. Email the offer goes to
focus_area_ids––Required.
free_sessions_requested––Company deals only: the free-sessions proposal from the catalog progression (2, 4 or 8)
heard_fromstring–How they found Marian, in their words (referral name, LinkedIn, Google, ChatGPT, ELC…)
homework_time_ok––Can they give about an hour a week between sessions
in_person_wish––Would they like to meet Marian in person (Prague)
kpis––Up to two measurable KPIs in their words, scored in session 1 and the last session
leaders_count–––
li_post_consentstring–May Marian post on LinkedIn that they work together (never the content) One of: yes, later, no.
li_recommendationstring–Would they write Marian a LinkedIn recommendation once happy One of: yes, later, no.
linkedin_urlstring–Their LinkedIn profile URL
motivationstring–Required.
namestring–Required. Visitor's full name
nda_neededstring–One of: no, their-template, marian-template, unsure.
notesstring––
offer_idstring–Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day.
own_choicestring–Mentee's own decision, sent by the company, or both One of: own, sent, both.
payerstring–Who pays. Company: the purchase order comes AFTER session 1, never before booking One of: self, company, undecided.
price_agreed––Required. True ONLY after the visitor explicitly agreed to the exact price from compose_mentoring_brief
role_bandstring–Required.
session_languagestring–One of: cs, sk, en.
start_datestring–Optional preferred start date — adds the dated program skeleton to the offer email
success_definitionstring–Required.
visibilitystring–Visibility answer id (yes-individual | yes-company | maybe-later | private)

No output schema declared.

No examples provided.

Install

How do I install the coach.marian/mentoring-inquiry-builder MCP server?

coach.marian/mentoring-inquiry-builder is a hosted endpoint at https://www.marian.coach/mcp/mentoring, 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 · www.marian.coach

# add to Claude Code
claude mcp add --transport http coach-marian-mentoring-inquiry-builder 'https://www.marian.coach/mcp/mentoring'
Common questions

What is the coach.marian/mentoring-inquiry-builder MCP server?

coach.marian/mentoring-inquiry-builder is an MCP server listed in the public MCP registry as coach.marian/mentoring-inquiry-builder. Build your mentoring inquiry with Marian Kamenistak: formal offer in 16 minutes, 16% AI discount. This page covers its hosted endpoint (https://www.marian.coach/mcp/mentoring).

Is the coach.marian/mentoring-inquiry-builder MCP server safe to use?

coach.marian/mentoring-inquiry-builder scores 86 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 coach.marian/mentoring-inquiry-builder MCP server expose?

coach.marian/mentoring-inquiry-builder exposes 10 tools: get_started, get_more_tools, get_mentoring_options, match_mentoring_focus, compose_mentoring_brief, and 5 more. Their descriptions and schemas cost roughly 2,837 tokens of context every time the server is loaded.

Does the coach.marian/mentoring-inquiry-builder MCP server require authentication?

No. We connected to coach.marian/mentoring-inquiry-builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the coach.marian/mentoring-inquiry-builder MCP server still maintained?

coach.marian/mentoring-inquiry-builder is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.