by.authorized/brands
REMOTE · APP.AUTHORIZED.BY · SCANNED SEP 21
Search brands and find authorized retailers on authorized.by
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1621 tokens (~270/item across 6 items; 6 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the by.authorized/brands MCP server?
by.authorized/brands is a hosted endpoint at https://app.authorized.by/api/public/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 · app.authorized.by
claude mcp add --transport http by-authorized-brands 'https://app.authorized.by/api/public/mcp'
{
"mcpServers": {
"by-authorized-brands": {
"url": "https://app.authorized.by/api/public/mcp"
}
}
} {
"servers": {
"by-authorized-brands": {
"type": "http",
"url": "https://app.authorized.by/api/public/mcp"
}
}
} [mcp_servers.by-authorized-brands] url = "https://app.authorized.by/api/public/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"by-authorized-brands": {
"type": "remote",
"url": "https://app.authorized.by/api/public/mcp",
"enabled": true
}
}
} openclaw mcp add by-authorized-brands --url 'https://app.authorized.by/api/public/mcp' --transport streamable-http
mcp_servers:
by-authorized-brands:
url: "https://app.authorized.by/api/public/mcp" {
"McpServers": {
"by-authorized-brands": {
"Transport": "http",
"Url": "https://app.authorized.by/api/public/mcp"
}
}
} assistant mcp add by-authorized-brands -t streamable-http -u 'https://app.authorized.by/api/public/mcp'
{
"mcpServers": {
"by-authorized-brands": {
"type": "http",
"url": "https://app.authorized.by/api/public/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.
- 15 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_brand” rewrote its description, which is the text the model reads security
- Tool “get_brand_retailers” rewrote its description, which is the text the model reads security
- Tool “get_brands” rewrote its description, which is the text the model reads security
- Tool “get_retailer” rewrote its description, which is the text the model reads security
- Tool “get_retailer_brands” rewrote its description, which is the text the model reads security
- Tool “get_retailers” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- MCP protocol: fail → pass ▲ functional
- Tool “get_brand” now declares an output schema ▲ functional
- Tool “get_brand_retailers” now declares an output schema ▲ functional
- Tool “get_brands” now declares an output schema ▲ functional
- Tool “get_retailer” now declares an output schema ▲ functional
- Tool “get_retailer_brands” now declares an output schema ▲ functional
- Tool “get_retailers” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- MCP protocol version: 2025-03-26 → 2026-07-28 functional
- Server version: 1.0.0 → 1.1.0 functional
- “get_brand” reworded the description of “id_or_alias” cosmetic
- “get_brand_retailers” reworded the description of “id_or_alias” cosmetic
- “get_retailer” reworded the description of “id_or_alias” cosmetic
- “get_retailer_brands” reworded the description of “id_or_alias” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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 Jul 26 0
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 21 Sept 2026 · Probed https://app.authorized.by/api/public/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.authorized.by | CN=GlobalSign GCC R3 DV TLS CA 2020,O=GlobalSign nv-sa,C=BE | 22 Aug 2025 | 23 Sept 2026 | RSA 2048 | SHA256-RSA | 1260f470724cccfdf3ef75c6 |
| SANs: *.authorized.by, authorized.by | ||||||
| CN=*.authorized.by | CN=GlobalSign GCC R3 DV TLS CA 2020,O=GlobalSign nv-sa,C=BE | 22 Aug 2025 | 23 Sept 2026 | RSA 2048 | SHA256-RSA | 1260f470724cccfdf3ef75c6 |
| SANs: *.authorized.by, authorized.by | ||||||
| CN=GlobalSign GCC R3 DV TLS CA 2020,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSign | 28 Jul 2020 | 18 Mar 2029 | RSA 2048 | SHA256-RSA | 77bd0e0742d5d9e9d049d774d02a6f9a |
| CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSign (CA) | CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSign | 18 Mar 2009 | 18 Mar 2029 | RSA 2048 | SHA256-RSA | 4000000000121585308a2 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.authorized.by. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| by. | present | 495 | 13 | Verified |
| authorized.by. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.authorized.by/api/public/mcp | Verified | 200 | |
| http (plaintext) | http://app.authorized.by/api/public/mcp | HTTPS enforced |
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_brand ~185
Get the public profile of one brand (manufacturer) on authorized.by. Read-only. Returns categories, website, headquarters country, description, registration date and the number of authorized retailers. Use get_brands first if you only know an approximate name. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_alias | string | yes | Brand numeric ID, slug or alias, e.g. 'deuter' or '16709'. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array|null | yes | Product categories. |
| details | object|null | yes | Extended profile details. |
| id | integer | yes | Numeric authorized.by ID. Accepted by the id_or_alias argument of the detail tools. |
| logo | string|null | yes | Logo image URL, or null. |
| name | string|null | yes | Display name. |
| product_count | integer | yes | Number of products registered on authorized.by; null when unknown. |
| retailer_count | integer | yes | Number of retailers currently authorized by this brand on authorized.by. |
| slug | string|null | yes | URL-safe identifier. Accepted by the id_or_alias argument of the detail tools. |
| website_url | string|null | yes | Brand website URL, or null. |
No examples provided.
get_brand_retailers ~345
List all retailers (shops) currently authorized by a brand on authorized.by. Read-only. Use this to answer 'is shop X an authorized retailer of brand Y?'. Sorted by subscription plan (PREMIUM, then START, then FREE) and then by brand-connection count descending. Each retailer includes shop_url, seal_implemented (whether the authorized.by seal is live on their shop), official_shop, partnership_date, and certificate_url / certificate_url_de: links to the public authorized.by certificate page (English / German) proving this specific brand-retailer authorization. Share the certificate link when a user needs verifiable proof. Only active partnerships are returned: confirmed by both the brand and the retailer, with both profiles public and the brand approved by authorized.by. Revoked or pending partnerships are never listed. Responses are cached and refreshed when the underlying profile or partnership changes, so a revocation may take a short time to disappear. partnership_date is the date the authorization STARTED, not the date it was last verified; a partnership listed here is currently active as of the response time. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_alias | string | yes | Brand numeric ID, slug or alias. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | integer | yes | Numeric ID of the brand the list belongs to. |
| premium_count | integer | yes | Number of listed retailers on the PREMIUM plan. |
| retailers | array|null | yes | – |
| total | integer | yes | Number of entries in the list. |
| tuv_certified_count | integer | yes | Number of listed retailers with a TÜV certification. |
No examples provided.
get_brands ~214
Search brands (manufacturers) registered on authorized.by, or list them all. Read-only. Returns for each brand: id, name, slug, logo and the number of retailers it has authorized. Omit 'search' to retrieve the full index; use 'page' and 'size' to paginate. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-based page number (default 0). |
| search | string | – | Filter by brand name or alias. Optional. |
| size | integer | – | Page size (default 500). |
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array|null | yes | – |
| meta | object|null | yes | Network-wide totals. |
| pagination | object|null | yes | Pagination of this response. |
No examples provided.
get_retailer ~225
Get the public profile of one retailer (shop) on authorized.by. Read-only. Returns address, contact details, opening hours, categories, subscription plan, TÜV certification, customer rating, registration date, seal_implemented (whether the authorized.by seal is live on their shop), and certificate_url / certificate_url_de: links to the retailer's public authorized.by certificate page (English / German) listing all brands that authorized it. These links are null when the retailer has no active authorization. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_alias | string | yes | Retailer numeric ID, slug or alias. |
| Name | Type | Req | Description |
|---|---|---|---|
| brand_count | integer | yes | Number of brands that currently authorize this retailer on authorized.by. |
| certificate_url | string|null | yes | Public authorized.by certificate page (English) that proves the authorization; null when there is no active authorization. |
| certificate_url_de | string|null | yes | Same certificate page in German; null when there is no active authorization. |
| details | object|null | yes | Extended profile details. |
| id | integer | yes | Numeric authorized.by ID. Accepted by the id_or_alias argument of the detail tools. |
| logo | string|null | yes | Logo image URL, or null. |
| name | string|null | yes | Display name. |
| plan | string|null | yes | authorized.by subscription plan of the retailer: PREMIUM, START or FREE. |
| seal_implemented | boolean | yes | Whether the authorized.by seal is live on the retailer's shop. |
| shop_url | string|null | yes | Retailer online-shop URL, or null. |
| slug | string|null | yes | URL-safe identifier. Accepted by the id_or_alias argument of the detail tools. |
| tuv_certified | boolean | yes | Whether the retailer holds a TÜV certification via authorized.by. |
No examples provided.
get_retailer_brands ~313
List all brands a retailer (shop) is currently authorized to sell, according to authorized.by. Read-only. Use this to answer 'which brands has shop X been authorized for?'. Sorted by brand name. Each entry includes official_shop, partnership_date, and certificate_url / certificate_url_de: links to the public authorized.by certificate page (English / German) proving this specific brand-retailer authorization. Share the certificate link when a user needs verifiable proof. Only active partnerships are returned: confirmed by both the brand and the retailer, with both profiles public and the brand approved by authorized.by. Revoked or pending partnerships are never listed. Responses are cached and refreshed when the underlying profile or partnership changes, so a revocation may take a short time to disappear. partnership_date is the date the authorization STARTED, not the date it was last verified; a partnership listed here is currently active as of the response time. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| id_or_alias | string | yes | Retailer numeric ID, slug or alias. |
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array|null | yes | – |
| retailer_id | integer | yes | Numeric ID of the retailer the list belongs to. |
| total | integer | yes | Number of entries in the list. |
No examples provided.
get_retailers ~234
Search retailers (shops) registered on authorized.by, or list them all. Read-only. Returns for each retailer: id, name, slug, shop URL, logo, the number of brands that authorized it, and seal_implemented (whether the authorized.by seal is live on their shop). Omit 'search' to retrieve the full index; use 'page' and 'size' to paginate. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the data.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Zero-based page number (default 0). |
| search | string | – | Filter by retailer company name or alias. Optional. |
| size | integer | – | Page size (default 500). |
| Name | Type | Req | Description |
|---|---|---|---|
| meta | object|null | yes | Network-wide totals. |
| pagination | object|null | yes | Pagination of this response. |
| retailers | array|null | yes | – |
No examples provided.
What is the by.authorized/brands MCP server?
by.authorized/brands is an MCP server listed in the public MCP registry as by.authorized/brands. Search brands and find authorized retailers on authorized.by. This page covers its hosted endpoint (https://app.authorized.by/api/public/mcp).
Is the by.authorized/brands MCP server safe to use?
by.authorized/brands scores 84 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 by.authorized/brands MCP server expose?
by.authorized/brands exposes 6 tools: get_brands, get_brand, get_brand_retailers, get_retailers, get_retailer, get_retailer_brands. Their descriptions and schemas cost roughly 1,516 tokens of context every time the server is loaded.
Does the by.authorized/brands MCP server require authentication?
No. We connected to by.authorized/brands without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the by.authorized/brands MCP server still maintained?
by.authorized/brands is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.