# `io.engineeringleaders/elc-trade` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/io.engineeringleaders/elc-trade
- JSON: https://radar.anlyon.com/api/v1/servers/io.engineeringleaders/elc-trade
- Version: 1.0.0 (active)
- Publisher: io.engineeringleaders (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/marian-kamenistak/elc-trade
- Metadata from the official MCP Registry, synced 2026-10-21T18:13:39.960Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Score a meetup topic, place a speaker on the right stage, price community reach. ELC data.
```

Scanned 2026-11-17T01:17:50.784Z over streamable-http.

**9 tools: 8 change things and 1 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 8 | ask |
| Only reads | read | 1 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | none |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `get_started` ([annotation-conflict](https://radar.anlyon.com/methodology#annotation-conflict))

```untrusted-server-text
The server marks "get_started" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_started" says "get": a word for reading.
```

- **info** The word "credentials" in `buy_reach` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **info** The word "credentials" in `benchmark_leadership_ratio` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **info** The word "credentials" in `assess_community_launch_readiness` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **info** The word "credentials" in `build_partnership_business_case` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **info** The word "credentials" in `evaluate_meetup_topic` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **warn** Annotations that disagree with the tool in `evaluate_meetup_topic` ([annotation-conflict](https://radar.anlyon.com/methodology#annotation-conflict))

```untrusted-server-text
The server marks "evaluate_meetup_topic" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "evaluate_meetup_topic" says "evaluate": a word for a change.
```

- **info** The word "credentials" in `assess_speaker_readiness` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```

- **info** The word "credentials" in `cite_benchmark` ([credentials-mention](https://radar.anlyon.com/methodology#credentials-mention))

```untrusted-server-text
The input schema at properties.context.description mentions "credentials".

inputSchema.properties.context.description: "...R include sensitive information such as credentials, passwords, or personal data. Example (..."
```


## Changes things (8)

Creates or changes something that can be changed back. Claude Code: ask.

### `assess_community_launch_readiness`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
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`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
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`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
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`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
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`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
Answers 'how do we get in front of 3,500+ CEE engineering leaders, and what does it cost?' Builds a cart from ELC's nine 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, a newsletter classified (30 words and a link, tools and events only, never jobs), decision-maker dinner, podcast episode, community survey, job listing — applies the published combo discount, and returns a decision-ready quote a human can sign.
```

### `cite_benchmark`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention

Description, as the server wrote it:

```untrusted-server-text
Answers 'where did that number come from?' Returns an ELC figure from the Data Points registry with its citation id, source and the date it was last verified, so an agent can quote the figure and show where it came from. An unknown id returns the three nearest ids instead of a guess.
```

### `evaluate_meetup_topic`

- The name "evaluate_meetup_topic" says "evaluate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: info credentials-mention, warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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_started`

- The name "get_started" says "get": a word for reading.
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Only reads (1)

Looks things up and changes nothing. Claude Code: allow.

### `get_more_tools`

- The name "get_more_tools" says "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `elc-trade`:

```json
{
  "permissions": {
    "allow": [
      "mcp__elc-trade__get_more_tools"
    ],
    "ask": [
      "mcp__elc-trade__get_started",
      "mcp__elc-trade__buy_reach",
      "mcp__elc-trade__benchmark_leadership_ratio",
      "mcp__elc-trade__assess_community_launch_readiness",
      "mcp__elc-trade__build_partnership_business_case",
      "mcp__elc-trade__evaluate_meetup_topic",
      "mcp__elc-trade__assess_speaker_readiness",
      "mcp__elc-trade__cite_benchmark"
    ],
    "deny": []
  }
}
```

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T19:22:52.248Z, unchanged since 2026-10-29T22:19:11.754Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `8` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://radar.anlyon.com/methodology#unauth-remote-writes))

```untrusted-server-text
The endpoint served tools/list without credentials, and the list has 8 tools that change things (8 write). Whether a call also works without credentials was not tested: tools are never called.

https://www.engineeringleaders.io/mcp/trade: tools/list returned 9 tools to an anonymous client, including get_started (write), buy_reach (write), benchmark_leadership_ratio (write), assess_community_launch_readiness (write), build_partnership_business_case (write) and 3 more
```

Posture changes:

- 2026-10-29T22:19:11.754Z: Tools that change things, listed without credentials `7` -> `8`
