ADITUS Developer Portal MCP
REMOTE · DEVELOPERS.ADITUS.COM · SCANNED SEP 23
Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · developers.aditus.com
claude mcp add --transport http com-aditus-developers-developer-portal 'https://developers.aditus.com/api/mcp'
{
"mcpServers": {
"com-aditus-developers-developer-portal": {
"url": "https://developers.aditus.com/api/mcp"
}
}
} {
"servers": {
"com-aditus-developers-developer-portal": {
"type": "http",
"url": "https://developers.aditus.com/api/mcp"
}
}
} [mcp_servers.com-aditus-developers-developer-portal] url = "https://developers.aditus.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aditus-developers-developer-portal": {
"type": "remote",
"url": "https://developers.aditus.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-aditus-developers-developer-portal --url 'https://developers.aditus.com/api/mcp' --transport streamable-http
mcp_servers:
com-aditus-developers-developer-portal:
url: "https://developers.aditus.com/api/mcp" {
"McpServers": {
"com-aditus-developers-developer-portal": {
"Transport": "http",
"Url": "https://developers.aditus.com/api/mcp"
}
}
} assistant mcp add com-aditus-developers-developer-portal -t streamable-http -u 'https://developers.aditus.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 19 Sept 26 −1
- 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 security
- Schema quality: pass → fail ▼ functional
- “search_docs” reworded the description of “query” cosmetic
- 18 Sept 26 +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.
- 16 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 14 Sept 26 +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.
- 13 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Sept 2026 · Probed https://developers.aditus.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=developers.aditus.com | CN=YE2,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 58603585d132305c10cd06ccdcd5622516c |
| SANs: developers.aditus.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of developers.aditus.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aditus.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'self' https://replit.com |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://developers.aditus.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://developers.aditus.com/api/mcp | HTTPS enforced | 301 | https://developers.aditus.com:443/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_endpoint Get endpoint details ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart' |
No output schema declared.
No examples provided.
get_guide Get an integration guide ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | yes | Guide id, e.g. 'micro-frontend', 'guidelines', 'webhooks' |
| section | string | – | Optional section heading (or slug) to return only that part |
No output schema declared.
No examples provided.
list_endpoints List endpoints of a module ~54
Every endpoint of one module (id, method, path, sub-group, one-line summary). Use the module id from list_modules.
| Name | Type | Req | Description |
|---|---|---|---|
| module | string | yes | Module id, e.g. 'ticket-purchase-registration' |
No output schema declared.
No examples provided.
list_modules List API modules ~51
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_docs Search ADITUS documentation ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum hits (default 10) |
| query | string | yes | Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import' |
No output schema declared.
No examples provided.
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 79 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 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.