ADITUS Developer Portal MCP

com.aditus.developers/developer-portal · v1.0.0 · docs-and-knowledge

ADITUS Developer Portal MCP is healthy: it completed an MCP handshake in 3902 ms and exposes 5 tools. It scores 57/100.

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

Endpoint: https://developers.aditus.com/api/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Score 57/100

health17 / 25
authEase15 / 15
toolQuality15 / 15
maintenance5 / 15
adoption0 / 10
usage0 / 10
security5 / 10

Scoring v0.3, computed 2026-10-15T08:34:18.291Z.

Health history

Checked (UTC)StatusLatencyError
2026-10-14T17:50:43.938ZHealthy3902

Tools (5)

search_docsFull-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' →
list_modulesAll 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_endpointsEvery endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
get_endpointFull 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}',
get_guideMarkdown 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.