# io.engineeringleaders/elc-trade

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

- name: io.engineeringleaders/elc-trade
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.engineeringleaders%2Felc-trade
- tools: https://api.protogrid.dev/v1/servers/io.engineeringleaders%2Felc-trade/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 98
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-95% ~updated-46d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,923 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 2,923 tokens to load them all
- tool set hash: cfe31be8fc231c686ad2b7a2e43c9b89
- tools last changed: 2026-10-20T18:32:30.147Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.engineeringleaders/elc-trade.svg)](https://protogrid.dev/servers/io.engineeringleaders/elc-trade)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-20 `buy_reach` changed (description, inputSchema)
  - before: Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's ten published one-off reach items — an ELC meetup, a speaker sprint, a conference main-stage talk, dedicated newsletter, newsletter section, decision-maker dinner, podcast episode, your name on three meetup evenings, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.
  - after: Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's ten published one-off reach items — an ELC meetup, the speaker programme (a ladder for one engineer, from a meetup slot to the full coached programme), a conference main-stage talk, dedicated newsletter, newsletter section, decision-maker dinner, podcast episode, your name on three meetup evenings, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.
- 2026-10-06 `buy_reach` changed (description, inputSchema)
  - before: 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.
  - after: Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's ten published one-off reach items — an ELC meetup, a speaker sprint, a conference main-stage talk, dedicated newsletter, newsletter section, decision-maker dinner, podcast episode, your name on three meetup evenings, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.

Full history: https://api.protogrid.dev/v1/servers/io.engineeringleaders%2Felc-trade/changes

## Remotes

- https://www.engineeringleaders.io/mcp/trade (streamable-http, auth none, reachable true, uptime30d 0.9478261)

## Packages

_none_

## Tools (8)

- `assess_community_launch_readiness`: 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.
- `assess_speaker_readiness`: 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.
- `benchmark_leadership_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.
- `build_partnership_business_case`: 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.
- `buy_reach`: Answers 'how do we get in front of 3,300+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's ten published one-off reach items — an ELC meetup, the speaker programme (a ladder for one engineer, from a meetup slot to the full coached programme), a conference main-stage talk, dedicated newsletter, newsletter section, decision-maker dinner, podcast episode, your name on three meetup evenings, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.
- `evaluate_meetup_topic`: 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.
- `get_more_tools`: 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.
- `get_started`: 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.