https://app.authorized.by/api/public/mcp
| Connection type | Remote MCP server |
| Transport | Streamable HTTP, stateless |
| Authentication | None |
| Protocol version | 2026-07-28 |
| Rate limit | 20 requests per minute per IP address |
| Cost | Free |
The server provides access to the same public data as the authorized.by Brands API.
What can you ask?
Once connected, you can ask questions such as:
- “Which brands have authorized feuerdepot.de? Include the certificate links.”
- “Show me five authorized Deuter retailers and their shop domains.”
- “Find a brand and show its public profile.”
- “Which brands is this retailer authorized to sell?”
Results reflect the data returned at the time of your query and may change.
Connect your client
Any client that supports remote MCP servers over Streamable HTTP can use the endpoint above. Select no authentication and follow your client’s documentation for the exact configuration format.
ChatGPT
Custom MCP connections require developer mode. Availability depends on your account and workspace settings.
- Open Settings → Security and login and enable Developer mode.
- Open ChatGPT Plugins and select the plus button.
- Enter authorized.by as the name.
- Select Server URL and paste the endpoint shown above.
- Set authentication to None.
- Review the notice and create the connection.
- Start a new conversation and select the authorized.by connection from the tools menu.
Adding this connection makes the tools available in your account. It does not make authorized.by automatically available in every ChatGPT conversation or to other users.
Claude
Workspace policies may require an administrator to add the connector first.
- Open Customize → Connectors.
- Select + → Add custom connector.
- Enter authorized.by as the name.
- Paste the server URL shown above.
- Leave optional OAuth credentials empty and finish adding the connector.
- Enable the connector for your conversation.
Try this first
After connecting, paste this prompt to see a full lookup end to end:
Use the authorized.by plugin to check which brands have authorized feuerdepot.de. Match the shop domain and include the certificate links.
Available tools
The server exposes six tools for exploring the network in both directions: from brands to their authorized retailers, and from retailers to their authorizing brands.
| Tool | Purpose | Parameters |
|---|---|---|
get_brands | Search brands and manufacturers. Returns names, slugs, logos and authorized-retailer counts. | Optional: search, page, size |
get_brand | Retrieve a brand’s public profile, including its website, categories and description. | Required: id_or_alias |
get_brand_retailers | Retrieve retailers authorized by a specific brand. | Required: id_or_alias |
get_retailers | Search retailers by company name or alias. Returns shop URLs and authorized-brand counts. | Optional: search, page, size |
get_retailer | Retrieve a retailer’s public profile and available details. | Required: id_or_alias |
get_retailer_brands | Retrieve the brands a retailer is authorized to sell, including available certificate links. | Required: id_or_alias |
For search tools, page numbering starts at 0. The documented default page size is 500. Use pagination information to determine whether more results are available. Profile fields may be empty where information is unavailable.
How to check a retailer
For a reliable authorization lookup:
- Search for the retailer using
get_retailers. - Compare the returned
shop_urlwith the domain being checked. - Use the returned retailer ID or slug with
get_retailer_brands. - Report the specific brand relationships returned by the server.
- Link to the available authorization certificates.
If a domain search does not return a match, try the retailer’s company name or alias and confirm the returned shop domain. Do not assume that similarly named shops are the same business.
Understanding the results
A confirmed relationship with one brand does not establish authorization for every brand in a retailer’s assortment.
It means that no matching record was found through the lookup. Authorizations may exist outside the authorized.by directory.
It should be considered alongside other relevant information when assessing a retailer.
| Field or attribute | How to interpret it |
|---|---|
partnership_date | The recorded start date of the authorization relationship, not the date of its latest update. |
certificate_url | The public English certificate link for the specific relationship, where available. |
certificate_url_de | The public German certificate link for the specific relationship, where available. |
| Subscription plan | The retailer’s package level. It is not a quality or safety score. |
tuv_certification_date | A recorded TÜV certification date. The date alone should not be interpreted as proof of current validity or scope. |
Retailer lists returned by get_brand_retailers are sorted by subscription plan — PREMIUM, START, FREE — and then by the number of brand connections. This ordering is not a ranking of retailer quality.
Technical details
The server uses JSON-RPC 2.0 over HTTP POST with Content-Type: application/json. Supported methods:
tools/list
tools/call
The server is stateless: requests do not require a persistent session. Notifications without an id, such as notifications/initialized, are acknowledged with HTTP 202 Accepted and an empty body.
Tool results are returned as JSON encoded inside a text content block. Clients should inspect isError before interpreting a result. A failed request or server error must not be presented as “no authorization found”.
Rate limits and responsible use
The server allows 20 requests per minute per IP address. Exceeding this limit returns HTTP 429 Too Many Requests.
Use targeted queries, avoid unnecessary repeated calls and apply backoff when rate-limited. If you cache results, retain the retrieval time and do not present cached information as a current lookup.
Prefer REST?
The same public data is available through the REST API:
https://app.authorized.by/api/public/v1/
/brands/{id}
/brands/{id}/retailers
/retailers
/retailers/{id}
/retailers/{id}/brands
The REST API caps the page size at 100 records.
About authorized.by
authorized.by enables brands to confirm their retail partners and makes those relationships accessible through public profiles, authorization certificates and machine-readable data.
authorized.by GmbH is part of the TÜV Saarland Group.
What the server returns
- Brand-confirmed retailer relationships, maintained by the brands themselves
- Public authorization certificates in English and German
- Brand and retailer profiles with shop domains and connection counts
- The same public data as the authorized.by Brands API
- Free access without an account or API key