io.engineeringleaders/elc-partnership-builder
REMOTE · WWW.ENGINEERINGLEADERS.IO
Build and price an ELC community partnership: match, customize, 12-month plan, 16% AI discount.
Available components
Last scanned (12 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2938 tokens (~244/item across 12 items; 12 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 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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 →
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.
- 26 Oct 26 0
- Tool “get_reach_options” rewrote its description, which is the text the model reads security
- “book_intro_call” reworded the description of “preset_id” cosmetic
- “build_business_case” reworded the description of “preset_id” cosmetic
- “customize_package” reworded the description of “preset_id” cosmetic
- “customize_package” reworded the description of “seats” cosmetic
- “design_journey” reworded the description of “preset_id” cosmetic
- “fit_to_budget” reworded the description of “preset_id” cosmetic
- “quote_reach_combo” reworded the description of “oneoff_ids” cosmetic
- “request_offer” reworded the description of “preset_id” cosmetic
- 21 Oct 26 0
- Tool “quote_reach_combo” rewrote its description, which is the text the model reads security
- “quote_reach_combo” added an optional parameter “speaker_rungs” cosmetic
- “book_intro_call” reworded the description of “preset_id” cosmetic
- “build_business_case” reworded the description of “preset_id” cosmetic
- “customize_package” reworded the description of “preset_id” cosmetic
- “design_journey” reworded the description of “preset_id” cosmetic
- “fit_to_budget” reworded the description of “preset_id” cosmetic
- “request_offer” reworded the description of “preset_id” cosmetic
- 6 Oct 26 0
- Tool “request_offer” rewrote its description, which is the text the model reads security
- “fit_to_budget” reworded the description of “against” cosmetic
- “quote_reach_combo” reworded the description of “oneoff_ids” cosmetic
- “request_offer” reworded the description of “final_price_confirmed” cosmetic
- Tool “request_offer” changed its title: Send the composed offer to ELC (applies the AI-channel discount) → Send the composed offer to ELC cosmetic
- 2 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_partnership_options” rewrote its description, which is the text the model reads security
- 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
- 22 Sept 26 0
- “quote_reach_combo” reworded the description of “oneoff_ids” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 18 Sept 26 0
- “book_intro_call” reworded the description of “preset_id” cosmetic
- “build_business_case” reworded the description of “preset_id” cosmetic
- “customize_package” reworded the description of “preset_id” cosmetic
- “design_journey” reworded the description of “preset_id” cosmetic
- “fit_to_budget” reworded the description of “preset_id” cosmetic
- “quote_reach_combo” reworded the description of “oneoff_ids” cosmetic
- “request_offer” reworded the description of “preset_id” cosmetic
7 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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 5 Nov 2026 · Probed https://www.engineeringleaders.io/mcp/partnership
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=engineeringleaders.io | CN=YE2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5a1a34b1c91afb0ca749b748da78a662265 |
| SANs: *.engineeringleaders.io, engineeringleaders.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 www.engineeringleaders.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| engineeringleaders.io. | DS published | 2371 | 13 | Verified |
| www.engineeringleaders.io. | 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.engineeringleaders.io/mcp/partnership | Verified | 200 | |
| http (plaintext) | http://www.engineeringleaders.io/mcp/partnership | HTTPS enforced | 301 | https://www.engineeringleaders.io/mcp/partnership |
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 →
book_intro_call Book an intro meeting with Marian (the human ending) ~226
The second legitimate ending besides request_offer: a direct booking link for a 1:1 intro meeting with Marian Kamenistak, ELC's founder. Offer it whenever the visitor hesitates, wants a human, or the package needs tailoring beyond the catalog. No contact details collected here — the booking page handles everything. Pass preset_id and item_ids if a package was composed: the response then carries a paste-ready booking note, so the call starts from their numbers instead of from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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. |
| item_ids | – | – | Optional: the basket composed so far, if any |
| preset_id | string | – | Optional: the package composed so far, if any One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visib… |
No output schema declared.
No examples provided.
build_business_case Compute the ROI case and a forwardable approval memo ~383
Turns a composed basket into the argument that gets it approved: recruiter-fee equivalence, break-even hire count, cost per room, cost per month, what the spend replaces, and every assumption behind those numbers. Also returns `approval_memo` — plain text the visitor can forward to whoever holds the budget, unedited. Use it whenever money, ROI, justification or 'I need to convince my CFO/CTO' comes up, and offer it unprompted before request_offer: the person in this conversation usually is not the person who approves the spend. Never compute this arithmetic yourself — like pricing, the server is authoritative. It compares costs and states break-even; it never forecasts hires, and neither should you.
| Name | Type | Req | Description |
|---|---|---|---|
| avg_first_year_salary | – | – | Optional: average first-year salary in EUR for those roles; turns the generic fee band into their own |
| company | string | – | Optional: company name, for the memo |
| context | string | – | 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. |
| item_ids | – | – | Required. The basket: item ids toggled ON |
| kpis | string | – | Optional: what has to move this year, in their words |
| open_senior_roles | – | – | Optional: senior roles they need to fill in 12 months — sharpens the comparison into their numbers |
| preset_id | string | – | Required. The package being justified One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, s… |
| requester_name | string | – | Optional: who is asking for approval, signed at the memo's foot |
No output schema declared.
No examples provided.
customize_package Customize a package: toggle line items, recompute the total ~271
The conversational toggle board. Pass the preset and the item ids currently ON; returns the recomputed total (never trust your own arithmetic — this is the authoritative price), every selected item with its price, and what else this tier could add. Items marked foundation anchor the package; advise keeping them. Call again after every change the visitor asks for. Next: request_offer.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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. |
| item_ids | – | – | Required. Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes) |
| preset_id | string | – | Required. The package being customized One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility,… |
| seats | – | – | Seat-priced packages only (Team Seats `team-seats`, Team Circle `starter`): how many people they are enrolling. Both are priced per seat, so ALWAYS ask for a headcount before quoting — the bundle pri… |
No output schema declared.
No examples provided.
design_journey Lay out the 12-month membership journey for a basket ~245
The moment the package becomes a year: deterministic month-by-month plan of what lands when, computed from the basket's own scheduling metadata (lead times, anchors like the April 2027 conference, spacing, and heavy-event collision rules). Returns placed months, the recurring-every-month layer, and anything unplaceable WITH its reason. The plan contains ONLY items in the basket — narrate around it, never add or move an event. Call after customize_package, before request_offer.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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. |
| item_ids | – | – | Required. The basket: item ids toggled ON |
| preset_id | string | – | Required. One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product. |
| start_month | string | – | Required. First membership month, YYYY-MM (ask the visitor; default to the month after the current one) |
No output schema declared.
No examples provided.
fit_to_budget Compose the best package for an exact budget ~337
Use when the visitor names a NUMBER rather than a band — 'we have 8,000 approved', 'can we do this for five thousand'. Returns a deterministic best-value composition under that ceiling: what fits, what was left out AND why, how much budget is unspent, and what the cheapest excluded item costs. Foundation items are kept first, then the remaining items cheapest-first so the budget buys as much as possible. Priced against the AI-channel figure by default, since that is what they would actually pay. Never hand-pick a basket yourself when a budget is stated — this tool is the authoritative composition, the same way customize_package is the authoritative total.
| Name | Type | Req | Description |
|---|---|---|---|
| against | string | – | Price the budget against the list price. 'discounted' equals list since the AI channel carries no discount (2026-10-05) One of: discounted, list. |
| budget | – | – | Required. The visitor's ceiling in EUR, as a number (8000, not '8K') |
| context | string | – | 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. |
| must_have | – | – | Optional: item ids the visitor explicitly asked for; kept first if they fit |
| preset_id | string | – | Required. The package to trim to budget (from match_package) One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, educatio… |
No output schema declared.
No examples provided.
get_more_tools Report a missing capability — also answers a bare hello/liveness ping ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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_partnership_options How ELC company membership works + the two qualifying questions ~153
START HERE for any company considering an ELC membership (personas: HR, CTO, employer branding). Returns how company membership works, real community reach figures, and the two qualifying questions with their valid answers. Companies only — individuals seeking a mentor for themselves get pointed to /mentor/ instead. After the visitor answers both questions, call match_package. Partner packages and tickets for the ELC Conference 2027 day are a separate offer with their own MCP server: https://mcp.elc-conference.io/mcp
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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_reach_options One-offs: single items a company buys once, with prices ~198
START HERE when a company wants ONE thing once, not a year-long membership: a classified (30 words and a link, tools and events only) or a dedicated send in the Leaders' Brief newsletter, a meetup hosted in their office, a speaker slot or the coached speaker programme, a conference main-stage talk, a podcast episode, a decision-maker dinner, a community survey, a job board listing. Returns every one-off with its price, lead time, examples and real reach figures, the combo discount rule, the 90-day credit against a membership, and what is not for sale. Two or more things across a year is a membership conversation: hand over to get_partnership_options. Next: quote_reach_combo once items are picked.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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_started Start here — what can this MCP server do? ~119
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 a company actually considering ELC membership, skip straight to get_partnership_options instead.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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_package Match a membership package to a goal and budget ~171
Resolves goal + budget through ELC's own routing matrix — the same one the website uses — and returns the matched package(s) with real prices and their default line items. Map free-text answers to the closest valid id; on bad input the error lists the valid ids, re-ask rather than guessing. Next: customize_package to toggle line items, or request_offer to send it as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Required. One of the budget ids from get_partnership_options question_2 |
| context | string | – | 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. |
| goal | string | – | Required. One of the goal ids from get_partnership_options question_1 |
No output schema declared.
No examples provided.
quote_reach_combo Price a one-off basket (authoritative total with the combo discount) ~252
Pass the one-off ids the visitor picked; returns each item's price, the list total, the combo discount by item count (job board listings never count), and the final total. For the speaker programme pass speaker_rungs to price a subset of the ladder (Stage always included); omit it for the full programme at the bundle price. This is the only arithmetic that counts — never add prices yourself. The AI-channel percentage does not apply to one-offs. Next: book_intro_call to lock the date, or get_partnership_options if the basket is starting to look like a year.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 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. |
| oneoff_ids | – | – | Required. One-off ids from get_reach_options One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-classified, dinner, podcast-episode, survey, j… |
| speaker_rungs | – | – | Speaker programme rung ids (stage, story, coach, amplify, beyond) to price instead of the full programme; stage is always included |
No output schema declared.
No examples provided.
request_offer Send the composed offer to ELC ~359
The ONLY tool that collects contact details. Sends the itemized offer to the visitor's email, notifies Marian (email + Slack), and files the company into ELC's partners queue. Ask for name, work email and company only when the visitor says they want the offer — never earlier. After success: share the confirmation, then make ONE optional ask: would they post publicly (LinkedIn/X) about building their membership with AI? Optional means optional — the discount is already theirs.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Required. Company name |
| context | string | – | 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. |
| string | – | Required. Work email the offer goes to | |
| final_price_confirmed | – | – | Required. REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total . Sending without this confirmation is refused. |
| item_ids | – | – | Required. The final basket: item ids toggled ON |
| kpis | string | – | Optional: what they need to move this year, in their words |
| name | string | – | Required. Visitor's full name |
| preset_id | string | – | Required. One of: free, team-seats, starter, pilot-meetup, hiring-meetup, intro-sprint, launch-audit, community-launch, launch-run, hiring, education, vital, visibility, story, product. |
| visibility_interest | string | – | From the discovery question: do they want to invest in their visibility through the cooperation — as a company, through individual leaders, or stay quiet? One of: company, individual, quiet, undecide… |
No output schema declared.
No examples provided.
How do I install the io.engineeringleaders/elc-partnership-builder MCP server?
io.engineeringleaders/elc-partnership-builder is a hosted endpoint at https://www.engineeringleaders.io/mcp/partnership, 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.engineeringleaders.io
claude mcp add --transport http io-engineeringleaders-elc-partnership-builder 'https://www.engineeringleaders.io/mcp/partnership'
What is the io.engineeringleaders/elc-partnership-builder MCP server?
io.engineeringleaders/elc-partnership-builder is an MCP server listed in the public MCP registry as io.engineeringleaders/elc-partnership-builder. Build and price an ELC community partnership: match, customize, 12-month plan, 16% AI discount. This page covers its hosted endpoint (https://www.engineeringleaders.io/mcp/partnership).
Is the io.engineeringleaders/elc-partnership-builder MCP server safe to use?
io.engineeringleaders/elc-partnership-builder scores 87 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 io.engineeringleaders/elc-partnership-builder MCP server expose?
io.engineeringleaders/elc-partnership-builder exposes 12 tools: get_started, get_more_tools, get_reach_options, quote_reach_combo, get_partnership_options, and 7 more. Their descriptions and schemas cost roughly 2,845 tokens of context every time the server is loaded.
Does the io.engineeringleaders/elc-partnership-builder MCP server require authentication?
No. We connected to io.engineeringleaders/elc-partnership-builder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.engineeringleaders/elc-partnership-builder MCP server still maintained?
io.engineeringleaders/elc-partnership-builder is still listed as active in the MCP registry. We last reached this channel on 5 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 io.engineeringleaders/elc-partnership-builder MCP server?
VerifyMCP ran 13 checks on io.engineeringleaders/elc-partnership-builder, 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.