io.engineeringleaders/elc-trade

Est-ce que io.engineeringleaders/elc-trade est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.engineeringleaders/elc-trade » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• assess_community_launch_readiness≈ 466 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • answers · object · optionnel
    Answers to the five readiness questions. Omit to receive the questionnaire.
  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

  Exemple d'appel

  {"name": "assess_community_launch_readiness", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• assess_speaker_readiness≈ 621 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • talk_title · string · optionnel
    Required. The proposed talk title.
  • has_dry_run · boolean · optionnel
    Whether a rehearsal is scheduled.
  • prior_talks · integer · optionnel
    How many talks they have given.
  • has_recording · boolean · optionnel
    Whether a recording of them speaking exists. Pass it explicitly — inferring it from the background text cannot reliably read a denial like 'no recording'.
  • writes_publicly · boolean · optionnel
    Whether they publish writing — a blog, newsletter or regular posts.
  • speaker_background · string · optionnel
    Required. Role, seniority, and any prior speaking experience.

  Exemple d'appel

  {"name": "assess_speaker_readiness", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• benchmark_leadership_ratio≈ 515 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • managers · integer · optionnel
    Required. Managers and tech leads.
  • senior_ics · integer · optionnel
    Required. Senior and staff ICs. Leave out junior and mid ICs on both sides.

  Exemple d'appel

  {"name": "benchmark_leadership_ratio", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• build_partnership_business_case≈ 733 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • goal · string · optionnel
    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.
  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • buying_for · string · optionnel
    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' means one thing once, not a year, and routes to buy_reach.
  • sender_name · string · optionnel
    Who the approval email is signed by.
  • company_name · string · optionnel
    The company considering the membership.
  • approver_name · string · optionnel
    Who the approval email is addressed to.
  • proposed_budget_eur · number · optionnel
    A proposed budget in EUR. 0 is valid and routes to the free membership layer.

  Exemple d'appel

  {"name": "build_partnership_business_case", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• buy_reach≈ 678 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • budget_eur · number · optionnel
    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.
  • oneoff_ids · array · optionnel
    Required. Which one-off reach items to quote. One or more of: meetup-hosted, speaker-development, conference-main-stage, newsletter-dedicated, newsletter-section, dinner, podcast-episode, meetup-presence, survey, job-listing. Combo discount applies automatically.
  • speaker_rungs · array · optionnel
    Speaker programme rung ids to price instead of the full programme: stage, story, coach, amplify, beyond. Stage is always included. Omit for the whole programme at its bundle price.

  Exemple d'appel

  {"name": "buy_reach", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• evaluate_meetup_topic≈ 513 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • title · string · optionnel
    Required. The proposed meetup or talk title.
  • context · string · requis
    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). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
  • abstract · string · optionnel
    The abstract, if one exists yet.
  • audience · string · optionnel
    Who it is aimed at, e.g. 'CTOs and VPs', 'first-time engineering managers'.

  Exemple d'appel

  {"name": "evaluate_meetup_topic", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

• get_more_tools≈ 163 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • context · string · optionnel
    What you are trying to do. Omit it for the menu.

  Exemple d'appel

  {"name": "get_more_tools", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_started≈ 349 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • context · string · optionnel
    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.

  Exemple d'appel

  {"name": "get_started", "arguments": {"context": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"report": "texte", "source": "texte", "verdict": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.engineeringleaders.io/mcp/trade