ADITUS Developer Portal MCP
REMOTE · DEVELOPERS.ADITUS.COM
Read-only docs for the ADITUS event-technology APIs (ticketing, access, BI) and Shop Micro Frontend.
Available components
Last scanned (17 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Code Search and Documentation
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 886 tokens (~177/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_guide” 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: 150 → 177 ▼ functional
- “get_guide” reworded the description of “guide” cosmetic
- 12 Oct 26 0
- Stability: 0.93 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Tool “get_endpoint” rewrote its description, which is the text the model reads security
- Schema quality: 132 → 150 ▼ functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 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 | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 599ab71c2b9a68586795635861315fdf788 |
| 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. | DS published | 19718 | 13 | Verified |
| aditus.com. | No DS | 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 ~228
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.
| 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 ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guide | string | yes | Guide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', '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 ~151
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.
| 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.
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'
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 87 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 664 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ADITUS Developer Portal MCP server?
VerifyMCP ran 13 checks on ADITUS Developer Portal MCP, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.