# ADITUS Developer Portal MCP (remote · developers.aditus.com)

Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `developers.aditus.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp.md), [page](https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp)

## Channel facts

- Endpoint: `https://developers.aditus.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 660 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ADITUS Developer Portal MCP server?

ADITUS Developer Portal MCP is a hosted endpoint at https://developers.aditus.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-aditus-developers-developer-portal 'https://developers.aditus.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aditus-developers-developer-portal": {
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-aditus-developers-developer-portal": {
      "type": "http",
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-aditus-developers-developer-portal]
url = "https://developers.aditus.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aditus-developers-developer-portal": {
      "type": "remote",
      "url": "https://developers.aditus.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aditus-developers-developer-portal --url 'https://developers.aditus.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aditus-developers-developer-portal:
    url: "https://developers.aditus.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-aditus-developers-developer-portal": {
      "Transport": "http",
      "Url": "https://developers.aditus.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-aditus-developers-developer-portal -t streamable-http -u 'https://developers.aditus.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-aditus-developers-developer-portal": {
      "type": "http",
      "url": "https://developers.aditus.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, −1)

- [security] Tool “get_endpoint” rewrote its description, which is the text the model reads
- [security] Tool “search_docs” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “search_docs” reworded the description of “query”

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `search_docs` (~145 tokens)

Search ADITUS documentation

Full-text search across API modules, endpoints (name, path, description) and the integration guides (Shop Micro Frontend, 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.

Input parameters:

- `limit` (integer): Maximum hits (default 10)
- `query` (string, required): Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'

### `list_modules` (~51 tokens)

List API modules

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.

### `list_endpoints` (~54 tokens)

List endpoints of a module

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

Input parameters:

- `module` (string, required): Module id, e.g. 'ticket-purchase-registration'

### `get_endpoint` (~138 tokens)

Get endpoint details

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' and a query string are ignored. When nothing matches, the error lists the nearest endpoints of that method.

Input parameters:

- `endpoint` (string, required): Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'

### `get_guide` (~115 tokens)

Get an integration guide

Markdown of an integration guide. 'micro-frontend' is the Shop Micro Frontend contract (mounting, sessions, styling, Web Component, lifecycle, security); module guides such as 'guidelines' or 'webhooks' come from the API reference. Pass a section heading to fetch only that section.

Input parameters:

- `guide` (string, required): Guide id, e.g. 'micro-frontend', 'guidelines', 'webhooks'
- `section` (string): Optional section heading (or slug) to return only that part

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75

## Common questions

### What is the ADITUS Developer Portal MCP server?

ADITUS Developer Portal MCP is listed in the public MCP registry as com.aditus.developers/developer-portal. Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend. This page covers its hosted endpoint (https://developers.aditus.com/api/mcp).

### Is the ADITUS Developer Portal MCP server safe to use?

ADITUS Developer Portal MCP scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ADITUS Developer Portal MCP server expose?

ADITUS Developer Portal MCP exposes 5 tools: search_docs, list_modules, list_endpoints, get_endpoint, get_guide. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.

### Does the ADITUS Developer Portal MCP server require authentication?

No. We connected to ADITUS Developer Portal MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ADITUS Developer Portal MCP server still maintained?

ADITUS Developer Portal MCP is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://developers.aditus.com/api/mcp
- Website: https://developers.aditus.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-aditus-developers-developer-portal/api-mcp