# `com.aditus.developers/developer-portal` 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/com.aditus.developers/developer-portal
- JSON: https://radar.anlyon.com/api/v1/servers/com.aditus.developers/developer-portal
- Version: 1.0.0 (active)
- Publisher: com.aditus.developers (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-10-21T17:48:19.044Z

Title and description, as the publisher wrote them:

```untrusted-server-text
ADITUS Developer Portal MCP
Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
```

Scanned 2026-11-12T12:18:01.138Z over streamable-http.

**5 tools: 5 only read.**

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

## Exfil surface

2 private-data -> untrusted-input -> outbound paths in this server alone. Denying 1 outbound tool breaks every one: `mcp__developer-portal__get_endpoint`.

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

| Private data | Untrusted input | Outbound |
| --- | --- | --- |
| `mcp__developer-portal__get_endpoint` | `mcp__developer-portal__get_endpoint` | `mcp__developer-portal__get_endpoint` |
| `mcp__developer-portal__search_docs` | `mcp__developer-portal__get_endpoint` | `mcp__developer-portal__get_endpoint` |

## Findings

No check matched anything in these tool definitions.


## Only reads (5)

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

### `get_endpoint`

- The name "get_endpoint" says "get": a word for reading.
- Tag private-data: The description's first sentence says "doc": it reads documents.
- Tag untrusted-input: The description's first sentence says "url": it reads web pages, which anyone can write. The input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- Tag outbound: The input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
- Claude Code: ask, because it is tagged outbound.

Description, as the server wrote it:

```untrusted-server-text
Full contract of one endpoint: method, URL, auth, query and header parameters, request body example, example responses (large bodies truncated, full text on the docs page). Accepts the endpoint id from search/list, or 'METHOD /path'. Path parameters may use any name or spelling (':cart', '{cartId}', a concrete value); a leading '/api' or '/v1' is ignored. Some routes are recorded several times with different query parameters: a reference without query string resolves to the recording without query parameters, a reference with a query string (e.g. '?$expand=All') to the recording with exactly (or at least) those keys. If that still leaves several recordings, the result is { ambiguous: true, candidates: [{ id, name, method, path }] } instead of the contract — call again with one of the candidate ids. When nothing matches, the error lists the nearest endpoints of that method.
```

### `get_guide`

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

Description, as the server wrote it:

```untrusted-server-text
Markdown of an integration guide. 'micro-frontend' is the compact Shop Micro Frontend contract for coding agents (mounting, sessions, styling, Web Component, lifecycle, security); 'micro-frontend-docs' is the complete Micro Frontend documentation as on the website; 'micro-frontend-overview' is the non-technical overview (what it is, purchase flow, base setup, add-on levels); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section.
```

### `list_endpoints`

- The name "list_endpoints" says "list": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
```

### `list_modules`

- The name "list_modules" says "list": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
All top-level ADITUS API modules with direction (inbound = your systems call ADITUS, outbound = ADITUS data into your systems), endpoint counts and documentation URLs. Also lists the integration guides.
```

### `search_docs`

- The name "search_docs" says "search": a word for reading.
- Tag private-data: The name "search_docs" says "search" and "doc": it reads documents.

Description, as the server wrote it:

```untrusted-server-text
Full-text search across API modules, endpoints (name, path, description) and the guides (Shop Micro Frontend agent contract, full documentation and overview; Guidelines; Webhooks). The reference is English; German search terms are understood as well (a generated language layer maps them onto the English vocabulary, e.g. 'aussteller' → exhibitor, 'gutschein' → voucher). Returns ranked hits with ids usable in get_endpoint / get_guide.
```

## Claude Code permissions

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

```json
{
  "permissions": {
    "allow": [
      "mcp__developer-portal__search_docs",
      "mcp__developer-portal__list_modules",
      "mcp__developer-portal__list_endpoints",
      "mcp__developer-portal__get_guide"
    ],
    "ask": [
      "mcp__developer-portal__get_endpoint"
    ],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__developer-portal__search_docs`: private-data
- `mcp__developer-portal__get_endpoint`: private-data, untrusted-input, outbound

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T18:33:13.880Z, unchanged since 2026-10-22T14:26:38.860Z. 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 | `0` |
| 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` |
