io.github.juliusgerman/entyrix-mcp
REMOTE · ENTYRIX.COM · 2 COMPONENTS
KYB data from 23 European business registries — company briefs, financials, ownership, AML screening
Available components
Last scanned (4 hours ago)
Scores higher than 82% of remote servers
Reachable. Last reached 23 Oct 2026.
Category CRM and Sales
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3496 tokens (~249/item across 14 items; 13 tools + 1 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 Management43
- Stability observed for 13 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
- 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “kyb_check” rewrote its description, which is the text the model reads security
- Tool “screen_companies” rewrote its description, which is the text the model reads security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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.
- 18 Oct 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- Tool “get_company_relations” rewrote its description, which is the text the model reads security
- Tool “company_brief” rewrote its description, which is the text the model reads security
- “advanced_search” reworded the description of “nace” cosmetic
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ 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 23 Oct 2026 · Probed https://entyrix.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=entyrix.com | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66f573d5af243966a2b6c57b7bc37124811 |
| SANs: *.entyrix.com, entyrix.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of entyrix.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| entyrix.com. | present | 2371 | 13 | Verified |
| entyrix.com. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self';form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self' 'unsafe-inline' cdn.jsdelivr.net challenges.cloudflare.com static.cloudflareinsights.com;script-src-attr 'unsafe-inline';style-src 'self' 'unsafe-inline';upgrade-insecure-requests;connect-src 'self' challenges.cloudflare.com cloudflareinsights.com;frame-src https://www.openstreetmap.org https://challenges.cloudflare.com;report-uri /csp-report |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | accelerometer=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), keyboard-map=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(self), publickey-credentials-create=(self), publickey-credentials-get=(self), screen-wake-lock=(), serial=(), sync-xhr=(), usb=(), web-share=(self), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://entyrix.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://entyrix.com/mcp/v1 | HTTPS enforced | 301 | https://entyrix.com/mcp/v1 |
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 →
advanced_search Filter companies (portfolio / market sizing) ~508
Structured company search for portfolio building and market sizing — NOT for finding one known company (use search_companies). Filters: country, NACE prefix, status, region, turnover range (EUR), employee range, founding date range, VAT payer, tax debt, sanctions. Results are paged (limit + offset); the response says how many matched. Only the listed arguments exist — anything else is rejected, never silently ignored.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| employees_max | integer | – | Maximum number of employees. |
| employees_min | integer | – | Minimum number of employees. |
| founded_from | string | – | Founded on or after (YYYY-MM-DD). |
| founded_to | string | – | Founded on or before (YYYY-MM-DD). |
| limit | integer | – | Page size (default 50). |
| nace | string | – | NACE code prefix, dotted or not: division '62' (IT services, same across all markets), group '62.0' / '620', class '62.01' / '6201'. Classes are national: SK, AT, SE, SI, BE, GR and LT store NACE Rev… |
| offset | integer | – | Rows to skip for the next page. |
| order | string | – | Sort order (default turnover_desc). |
| region | string | – | Region name exactly as the register spells it. |
| sanctioned | boolean | – | Only companies with (true) / without (false) a sanctions hit. |
| status | string | – | Company lifecycle status. |
| tax_debt | boolean | – | Only companies on (true) / off (false) the tax-debtor list. |
| turnover_max_eur | number | – | Maximum latest annual turnover in EUR. |
| turnover_min_eur | number | – | Minimum latest annual turnover in EUR. |
| vat_payer | boolean | – | Only VAT-registered (true) or only non-registered (false). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Matching companies for this page, plus total count and any unknownFilters. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
check_compliance Public compliance snapshot ~177
Lightweight public compliance snapshot for one company (works without an account): sanctions screening, insolvency, debtor registers, VAT reliability. For the full KYB picture use kyb_check. A null field means WITHHELD or not measured — it does NOT mean clean.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Public compliance signals. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
company_brief Company brief (Markdown, LLM-ready) ~318
Compact, deterministic Markdown brief of one company (≤12 KB): identity, address, industry, latest financials, credit score and recommended limit, cyber score, risk flags (insolvency, tax debt, sanctions), NIS2 status and key people where licensed. The best single call for 'tell me about company X'. Accepts every registry identifier shape we carry (SK/CZ IČO, AT Firmenbuch e.g. '033209m', PL REGON, FR SIREN, …); pass `country` for anything that is not an 8-digit IČO. Every fact comes from the database — missing data is marked, never invented.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| meta | object | – | – |
No examples provided.
find_suppliers Public-sector contracts ~216
Public procurement contracts this company is party to (SK CRZ + CZ Registr smluv), newest first, paged. HONEST SCOPE: this is business-to-government procurement, NOT a commercial supply chain — do not present it as one.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| limit | integer | – | Page size (default 50). |
| offset | integer | – | Rows to skip for the next page. |
| years | integer | – | Look-back window in years (default 5). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Contracts and totals. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
get_company_details Full company record ~276
Full record for one company: identity, address, legal form, status flags, NACE, and the whole enrichment layer we hold (web, tech stack, NIS2, EU funds, LEI, HU de minimis state aid granted, HU public procurement from EKR, …). Large — prefer company_brief unless you need a specific field. Natural-person fields are gated and may be withheld; a withheld field is not the same as an empty one.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | The full company record. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
get_company_network Companies connected through people ~214
Companies connected to this one through shared officers or owners (one hop). Use for group structure and beneficial-ownership tracing. Person names are gated like everywhere else.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Connected companies and the people linking them. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
get_company_relations Direct relations ~285
Direct relations of one company — statutory officers, owners, parents, subsidiaries, M&A events — without traversing the wider graph. `shareholders` are owners only; members of the supervisory board are in `supervisoryBoard`. SK M&A events: effectiveDate is the date stated by the register; when missing, derivedEffectiveDate may carry a date INFERRED from the absorbed firm's deregistration (effectiveDateSource: "derived") — present it as an estimate, never as a register fact.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Officers, owners and corporate relations. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
get_financials Financial statements by year ~264
Filed financial statements of one company, one row per fiscal year (newest first), with revenue, profit, assets, equity, liabilities and year-over-year trend. Amounts are EUR CENTS as integers (divide by 100 for euros). Use for trend and solvency questions; company_brief already carries the latest year.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| years | integer | – | How many fiscal years (default 10). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Per-year financial statements and trend summary. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
kyb_check KYB / AML summary ~314
One-call Know-Your-Business summary for one company: registry status, insolvency, liquidation, sanctions screening, debarment, tax/social/health debts, VAT reliability and the overall risk verdict. Use before onboarding a customer or supplier. Coverage differs by country: `checks[]` gives each check as hit / clear / not_covered, and `overall` is INSUFFICIENT_DATA when no risk was found but the insolvency or sanctions registers do not exist for that country — that is NOT a clean result. A null field means WITHHELD or NOT MEASURED — it does NOT mean clean; say so when you report it.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Consolidated KYB/AML signals and the register the answer refers to. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
list_rankings Published rankings ~59
A published ranking by its slug (e.g. largest employers, top taxpayers). Call WITHOUT a key first to list the available slugs — inventing one returns an error.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Ranking slug. Omit to list all. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Either the list of rankings or one ranking's rows. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
lookup_company Look up company by registry ID ~271
Resolve exactly one company by its national registry identifier in a given country. Handles every identifier shape we carry (SK/CZ/EE IČO, AT Firmenbuch e.g. '187a', SI/LV registry numbers, …). Returns the core record: identity, address, legal form, status, NACE. For an LLM-ready summary prefer company_brief; for the full enrichment layer use get_company_details.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| ico | string | yes | National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side. |
| purpose | string | – | Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | The company record. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
screen_companies Screen a list of companies ~101
Run kyb_check on up to 25 companies at once and get one compact row per company (status, insolvency, sanctions, debts, verdict, coverage). INSUFFICIENT_DATA = no findings but not covered by the core registers for that country — never report it as clean. Use for supplier lists or portfolios. Each company counts as one API request against your rate limit. Requires an authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | Companies to screen. |
| Name | Type | Req | Description |
|---|---|---|---|
| failed | integer | yes | – |
| results | array | yes | – |
| screened | integer | yes | – |
No examples provided.
search_companies Search companies by name ~173
Find companies by name (or name fragment) across the pan-European dataset. Returns ranked candidates with registry identifier, country, legal form and status. Use this FIRST when you only know a name; then pass the identifier + country to lookup_company or company_brief. Do not use it to filter by industry or size — that is advanced_search.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and w… |
| limit | integer | – | Max results (default 10). |
| query | string | yes | Company name or fragment. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Array of candidate companies, best match first. |
| meta | object | – | Request metadata: request_id (quote it in support requests), duration_ms, cached. |
No examples provided.
How do I install the io.github.juliusgerman/entyrix-mcp server?
io.github.juliusgerman/entyrix-mcp is a hosted endpoint at https://entyrix.com/mcp/v1, 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 · entyrix.com
claude mcp add --transport http juliusgerman-entyrix-mcp 'https://entyrix.com/mcp/v1'
What is the io.github.juliusgerman/entyrix-mcp server?
io.github.juliusgerman/entyrix-mcp is listed in the public MCP registry as io.github.juliusgerman/entyrix-mcp. KYB data from 23 European business registries, company briefs, financials, ownership, AML screening. This page covers its hosted endpoint (https://entyrix.com/mcp/v1).
Is the io.github.juliusgerman/entyrix-mcp server safe to use?
io.github.juliusgerman/entyrix-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 io.github.juliusgerman/entyrix-mcp server expose?
io.github.juliusgerman/entyrix-mcp exposes 13 tools: search_companies, lookup_company, company_brief, get_company_details, get_financials, and 8 more. Their descriptions and schemas cost roughly 3,176 tokens of context every time the server is loaded.
Does the io.github.juliusgerman/entyrix-mcp server require authentication?
No. We connected to io.github.juliusgerman/entyrix-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.juliusgerman/entyrix-mcp server still maintained?
io.github.juliusgerman/entyrix-mcp is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.