io.engineeringleaders/elc-partnership-builder
REMOTE · WWW.ENGINEERINGLEADERS.IO · SCANNED AUG 15
Build and price an ELC community partnership: match, customize, 12-month plan, 16% AI discount.
Available components
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 →
Endpoint Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 836 tokens (~139/item across 6 items; 6 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 Management11
- Stability check failed: schema churn in the 7 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.engineeringleaders.io
claude mcp add --transport http io-engineeringleaders-elc-partnership-builder https://www.engineeringleaders.io/mcp/partnership
[mcp_servers.io-engineeringleaders-elc-partnership-builder] url = "https://www.engineeringleaders.io/mcp/partnership"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-engineeringleaders-elc-partnership-builder": {
"type": "remote",
"url": "https://www.engineeringleaders.io/mcp/partnership",
"enabled": true
}
}
} openclaw mcp add io-engineeringleaders-elc-partnership-builder --url https://www.engineeringleaders.io/mcp/partnership --transport streamable-http
mcp_servers:
io-engineeringleaders-elc-partnership-builder:
url: "https://www.engineeringleaders.io/mcp/partnership" {
"mcpServers": {
"io-engineeringleaders-elc-partnership-builder": {
"type": "http",
"url": "https://www.engineeringleaders.io/mcp/partnership"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 15 Aug 26 +8
- HSTS header: fail → pass ▲ security
- HTTPS: fail → pass ▲ security
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 1 to 4.
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Schema quality: 684 → 836 ▼ functional
- “request_offer” added a required parameter “final_price_confirmed”, so existing callers break ▼ functional
- Schema quality: good → excellent functional
- New tool “book_intro_call” functional
- “request_offer” added an optional parameter “visibility_interest” cosmetic
- 9 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Aug 26 63
First indexed and scored.
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 15 Aug 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=WR1,O=Google Trust Services,C=US | 21 Jul 2026 | 19 Oct 2026 | RSA 2048 | SHA256-RSA | de31ff2a0dd798940dd53158b47e5376 |
| SANs: engineeringleaders.io, www.engineeringleaders.io | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of www.engineeringleaders.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| engineeringleaders.io. | absent | 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=15552000; includeSubDomains |
| x-content-type-options | nosniff |
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.
book_intro_call Book an intro meeting with Marian (the human ending) ~74
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customize_package Customize a package: toggle line items, recompute the total ~120
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 |
|---|---|---|---|
| item_ids | array | yes | Item ids currently toggled ON (from match_package default_item_ids, plus/minus changes) |
| preset_id | string | yes | The package being customized |
No output schema declared.
No examples provided.
design_journey Lay out the 12-month partnership journey for a basket ~157
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 |
|---|---|---|---|
| item_ids | array | yes | The basket: item ids toggled ON |
| preset_id | string | yes | – |
| start_month | string | yes | First partnership month, YYYY-MM (ask the visitor; default to the month after the current one) |
No output schema declared.
No examples provided.
get_partnership_options How ELC company membership works + the two qualifying questions ~82
START HERE for any company considering an ELC partnership or 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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
match_package Match a partnership package to a goal and budget ~129
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 | yes | One of the budget ids from get_partnership_options question_2 |
| goal | string | yes | One of the goal ids from get_partnership_options question_1 |
No output schema declared.
No examples provided.
request_offer Send the composed offer to ELC (applies the AI-channel discount) ~274
The ONLY tool that collects contact details, and the step that makes the AI-channel discount real. 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 partnership with AI? Optional means optional — the discount is already theirs.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name |
| string | yes | Work email the offer goes to | |
| final_price_confirmed | boolean | yes | REQUIRED TRUE: set only after the visitor has seen and explicitly confirmed the exact final total (the discounted figure if the discount applies). Sending without this confirmation is refused. |
| item_ids | array | yes | The final basket: item ids toggled ON |
| kpis | string | – | Optional: what they need to move this year, in their words |
| name | string | yes | Visitor's full name |
| preset_id | string | yes | – |
| 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? |
No output schema declared.
No examples provided.