MCP serverio.engineeringleaders/elc-trade
Score a meetup topic, place a speaker on the right stage, price community reach.
Read more
Score a meetup topic, place a speaker on the right stage, price community reach. ELC data.Overview
Score?
UNRATED 0.646
of what a free look can see, on 25 looks
Looks
31
last 12 hr ago
Tools
8
changed 26 days ago
More info
URL
www.engineeringleaders.io/mcp/trade
streamable-http
Says it is
elc-trade 1.0.0
protocol 2025-06-18
In the record since
29 days ago
Among servers18,413 with a card
0median 0.606 · this server 0.646 · highest on record 0.8561
Toolsfrom sha256:651de3d5d4…20d606 · +0 −0 26 days ago
| Tool | Schema |
|---|---|
| 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, |
input · output |
| 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 p |
input · output |
| 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), p |
input · output |
| 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 |
input · output |
| 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 nine published one-off reach items — newsletter section, dedicat |
input · output |
| 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 |
input · output |
| 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 |
input · no output |
| 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 |
input · output |
Verify it yourself
npx teppi-check https://www.engineeringleaders.io/mcp/tradecurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1RE4TXWRY8GVZ2FSF083DAA