_ registry / mcp http-sse · checked 2h ago

aditus-developer-docs

https://developers.aditus.com

Registry code: 2565bcb5aa606e66

api record

Read-only documentation for the ADITUS event-technology APIs (ticketing, registration, access, accreditation, Business Intelligence) and the Shop Micro Frontend.

Start with search_docs for a topic, list_modules for orientation, then get_endpoint for the full contract (parameters, body, example responses) or get_guide for integration guides.

endpoint
https://developers.aditus.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is aditus-developer-docs live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is aditus-developer-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does aditus-developer-docs have?
5 tools: get_endpoint, list_endpoints, get_guide, search_docs, list_modules.
Is aditus-developer-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 98.4%· all time 98.4%

latency
5,485ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 447 checks · signed record
  • degraded → live
  • live → degraded· HTTP 500
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search event ticketing api documentation
  • get an api endpoint contract
  • read an integration guide
takes → gives
text → text
tools
5 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_modules reads open 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_endpoint reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "endpoint"
      ],
      "properties": {
        "endpoint": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'"
        }
      }
    }
    arguments 15 lines
  • list_endpoints reads unknown 10h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "module"
      ],
      "properties": {
        "module": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Module id, e.g. 'ticket-purchase-registration'"
        }
      }
    }
    arguments 15 lines
  • get_guide reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "guide"
      ],
      "properties": {
        "guide": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Guide id, e.g. 'micro-frontend', 'micro-frontend-docs', 'micro-frontend-overview', 'guidelines', 'webhooks'"
        },
        "section": {
          "type": "string",
          "maxLength": 120,
          "minLength": 1,
          "description": "Optional section heading (or slug) to return only that part"
        }
      }
    }
    arguments 21 lines
  • search_docs reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum hits (default 10)"
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'"
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2565bcb5aa606e66.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2565bcb5aa606e66/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2565bcb5aa606e66/badge.svg)](https://brick.blue/agent/2565bcb5aa606e66?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on aditus.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.