# io.engineeringleaders/elc-trade (remote · www.engineeringleaders.io)

Score a meetup topic, place a speaker on the right stage, price community reach. ELC data.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.engineeringleaders.io`: 81/100 (this document), [markdown](https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade.md), [page](https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade)

## Channel facts

- Endpoint: `https://www.engineeringleaders.io/mcp/trade`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1897 tokens (~237/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (88% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.engineeringleaders/elc-trade MCP server?

io.engineeringleaders/elc-trade is a hosted endpoint at https://www.engineeringleaders.io/mcp/trade, 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.

### Claude

```bash
claude mcp add --transport http io-engineeringleaders-elc-trade 'https://www.engineeringleaders.io/mcp/trade'
```

### Cursor

```json
{
  "mcpServers": {
    "io-engineeringleaders-elc-trade": {
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-engineeringleaders-elc-trade": {
      "type": "http",
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-engineeringleaders-elc-trade]
url = "https://www.engineeringleaders.io/mcp/trade"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-engineeringleaders-elc-trade": {
      "type": "remote",
      "url": "https://www.engineeringleaders.io/mcp/trade",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-engineeringleaders-elc-trade --url 'https://www.engineeringleaders.io/mcp/trade' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-engineeringleaders-elc-trade:
    url: "https://www.engineeringleaders.io/mcp/trade"
```

### Netclaw

```json
{
  "McpServers": {
    "io-engineeringleaders-elc-trade": {
      "Transport": "http",
      "Url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-engineeringleaders-elc-trade -t streamable-http -u 'https://www.engineeringleaders.io/mcp/trade'
```

### Other

```json
{
  "mcpServers": {
    "io-engineeringleaders-elc-trade": {
      "type": "http",
      "url": "https://www.engineeringleaders.io/mcp/trade"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 81, +1)

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

### 2026-09-19 (score 80, +1)

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

### 2026-09-17 (score 79, +1)

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

### 2026-09-15 (score 78, +1)

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

### 2026-09-13 (score 77, +1)

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

### 2026-09-11 (score 76, +1)

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

### 2026-09-09 (score 75, +1)

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

### 2026-09-08 (score 74, 0)

- [cosmetic] “assess_speaker_readiness” reworded the description of “speaker_background”
- [cosmetic] “assess_speaker_readiness” reworded the description of “talk_title”
- [cosmetic] “benchmark_leadership_ratio” reworded the description of “managers”
- [cosmetic] “benchmark_leadership_ratio” reworded the description of “senior_ics”
- [cosmetic] “build_partnership_business_case” reworded the description of “goal”
- [cosmetic] “buy_reach” reworded the description of “oneoff_ids”
- [cosmetic] “evaluate_meetup_topic” reworded the description of “title”
- [cosmetic] “get_more_tools” reworded the description of “context”
- [cosmetic] “assess_speaker_readiness” made “speaker_background” optional
- [cosmetic] “assess_speaker_readiness” made “talk_title” optional
- [cosmetic] “benchmark_leadership_ratio” made “managers” optional
- [cosmetic] “benchmark_leadership_ratio” made “senior_ics” optional
- [cosmetic] “build_partnership_business_case” made “goal” optional
- [cosmetic] “buy_reach” made “oneoff_ids” optional
- [cosmetic] “evaluate_meetup_topic” made “title” optional
- [cosmetic] “get_more_tools” made “context” optional

## MCP tools (8)

### `get_more_tools` (~73 tokens)

More tools? Check here first — also answers a plain hello

Check for additional specialised capabilities whenever your task might benefit from them. Also the right tool for a bare greeting or a liveness test — pass it as `context` and this returns the menu instead of a dead end.

Input parameters:

- `context` (string): What you are trying to do. Omit it for the menu.

### `get_started` (~139 tokens)

Start here — what is this, and which tool answers my question?

START HERE for a greeting (hi, hello), a connectivity or liveness test, 'what can you do', or any question too general to match a specific tool. Also the right call when the caller is a person rather than a company: ELC membership is free for engineering leaders and this says so. Pass their message as `context` and it routes to the tool that fits, or returns the full menu.

Input parameters:

- `context` (string): Optional: the caller's message in their own words — a greeting, a liveness test, or a plain description of what they are trying to do. Anything is accepted; there is no wrong value.

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `buy_reach` (~298 tokens)

Buy reach in the ELC community

Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's nine published one-off reach items — newsletter section, dedicated newsletter, hosted meetup, podcast episode, decision-maker dinner, community survey, demo session, LinkedIn post, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.

Input parameters:

- `budget_eur` (number): Optional: what you have to spend. Does not change any price — the quote will say whether the cart fits and what to drop if it does not.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `oneoff_ids` (array): Required. Which one-off reach items to quote. One or more of: newsletter-section, newsletter-dedicated, meetup-hosted, podcast-episode, dinner, survey, demo-session, linkedin-post, job-listing. Combo…

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `benchmark_leadership_ratio` (~234 tokens)

Benchmark your manager-to-senior-IC ratio

Answers 'what shape is my engineering org, and what should I ask about it?' Returns your manager-versus-senior-IC percentages and the resulting span (1 manager per N senior ICs), plus the question that shape usually raises. ELC's own community composition is shown alongside as context only — different denominator, so no delta and no score is computed against it.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `managers` (integer): Required. Managers and tech leads.
- `senior_ics` (integer): Required. Senior and staff ICs. Leave out junior and mid ICs on both sides.

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `assess_community_launch_readiness` (~194 tokens)

Should you start a meetup in your city?

Answers 'should I start an engineering-leadership meetup here?' A five-question readiness check taken from ELC's own new-city launch playbook — the one actually used to open Brno, Bratislava and Kraków — returning a verdict plus the specific gaps still open.

Input parameters:

- `answers` (object): Answers to the five readiness questions. Omit to receive the questionnaire.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `build_partnership_business_case` (~409 tokens)

Build the internal case for an ELC partnership

Answers 'how do I justify a community partnership budget internally?' Returns real reach numbers, the deliverables that serve the stated goal, where a proposed budget lands on the published ladder, and a forwardable approval email. Goals: hiring, brand_awareness, product_feedback, thought_leadership, people_development (developing your own engineering leaders — mentoring, Academy seats, the peer network). Set buying_for=individual if you are a person rather than a company: ELC membership is free for engineering leaders and no business case is needed.

Input parameters:

- `approver_name` (string): Who the approval email is addressed to.
- `buying_for` (string): Who is buying. 'company' (default) builds the annual membership case. 'individual' means a person spending their own money — returns the free-membership route instead of an approval email. 'one_off'…
- `company_name` (string): The company considering the membership.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `goal` (string): Required. The primary reason. people_development covers developing your own engineering leaders (mentoring, Academy seats, the peer network) — that is the one for retention and growth, not hiring.
- `proposed_budget_eur` (number): A proposed budget in EUR. 0 is valid and routes to the free membership layer.
- `sender_name` (string): Who the approval email is signed by.

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `evaluate_meetup_topic` (~246 tokens)

Evaluate a meetup topic before you commit to it

Answers 'will this topic fill a room?' Scores a proposed engineering-leadership meetup title and abstract against ELC's own topic-selection criteria — the ones behind 12 meetups a year at 120+ attendees since 2019 — and returns the specific failure modes, the title formulas that would fit, and the questions only the organiser can answer.

Input parameters:

- `abstract` (string): The abstract, if one exists yet.
- `audience` (string): Who it is aimed at, e.g. 'CTOs and VPs', 'first-time engineering managers'.
- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `title` (string): Required. The proposed meetup or talk title.

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

### `assess_speaker_readiness` (~304 tokens)

Assess whether a speaker is ready for the stage

Answers 'is this person ready to speak, and what will go wrong if they are not?' Checks a proposed speaker and talk against ELC's speaker vetting process — seven years of putting people in front of 120+ engineering leaders — and returns a readiness verdict with the specific gaps to close before the event.

Input parameters:

- `context` (string, required): Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVE…
- `has_dry_run` (boolean): Whether a rehearsal is scheduled.
- `has_recording` (boolean): Whether a recording of them speaking exists. Pass it explicitly — inferring it from the background text cannot reliably read a denial like 'no recording'.
- `prior_talks` (integer): How many talks they have given.
- `speaker_background` (string): Required. Role, seniority, and any prior speaking experience.
- `talk_title` (string): Required. The proposed talk title.
- `writes_publicly` (boolean): Whether they publish writing — a blog, newsletter or regular posts.

Output parameters:

- `report` (string): The full human-readable report.
- `source` (string): Canonical engineeringleaders.io page this answer derives from.
- `verdict` (string): Headline verdict, when the tool returns one.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade#diagnostics

## Score history

- 2026-09-21: 81
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 79
- 2026-09-17: 79
- 2026-09-16: 78
- 2026-09-15: 78
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 75
- 2026-09-09: 75
- 2026-09-08: 74
- 2026-09-07: 74
- 2026-09-06: 73
- 2026-09-05: 72

## Common questions

### What is the io.engineeringleaders/elc-trade MCP server?

io.engineeringleaders/elc-trade is an MCP server listed in the public MCP registry as io.engineeringleaders/elc-trade. Score a meetup topic, place a speaker on the right stage, price community reach. ELC data. This page covers its hosted endpoint (https://www.engineeringleaders.io/mcp/trade).

### Is the io.engineeringleaders/elc-trade MCP server safe to use?

io.engineeringleaders/elc-trade scores 81 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-trade MCP server expose?

io.engineeringleaders/elc-trade exposes 8 tools: get_more_tools, get_started, buy_reach, benchmark_leadership_ratio, assess_community_launch_readiness, and 3 more. Their descriptions and schemas cost roughly 1,897 tokens of context every time the server is loaded.

### Does the io.engineeringleaders/elc-trade MCP server require authentication?

No. We connected to io.engineeringleaders/elc-trade without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.engineeringleaders/elc-trade MCP server still maintained?

io.engineeringleaders/elc-trade is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.engineeringleaders.io/mcp/trade
- Repository: https://github.com/marian-kamenistak/elc-trade
- Website: https://www.engineeringleaders.io/agents/
- Changelog RSS feed: https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade.json
- HTML version of this page: https://verifymcp.io/servers/io-engineeringleaders-elc-trade/mcp-trade