1820.ch – Telefonbuch Schweiz
REMOTE · MCP.1820.CH
Swiss phone directory: search people and businesses, reverse number lookup, business categories.
Available components
Last scanned (13 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Search and Retrieval
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. 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
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 660 tokens (~165/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 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
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 7 Nov 2026 · Probed https://mcp.1820.ch/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=1820.ch | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8a19c1b51f18f4281301f03c0c5d3aa7 |
| SANs: 1820.ch, *.1820.ch | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.1820.ch. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ch. | DS published | 58745 | 13 | Verified |
| 1820.ch. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.1820.ch/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.1820.ch/mcp | HTTPS enforced | 301 | https://mcp.1820.ch/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 →
browse_business_category Browse a business category ~176
Lists public directory entries in one business category, optionally narrowed to a locality/postcode/canton. Use search_swiss_directory instead for a free-text query.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The business category slug (e.g. "restaurant", "coiffeur", "sanitaer"). Valid slugs are the slug values in categories, as returned by get_directory_entry, or a top-level group slug such as "bau-handw… |
| lang | string | – | Response language: de, fr, it, or en. Defaults to de. |
| limit | integer | – | Maximum number of results, 1-20. |
| location | string | – | Locality, postcode, or canton (e.g. "Baden", "5400", "ZH") to narrow the category to. Always put a place name here. |
| Name | Type | Req | Description |
|---|---|---|---|
| advertising_block_note | string | yes | – |
| results | null|array | yes | – |
| retrieved_at | string | yes | – |
| source | object | yes | – |
No examples provided.
get_directory_entry Get a directory entry ~121
Fetches the full public detail for one directory entry by its entry_id (public_id), including phone numbers, opening hours, and links when the entry has them. Use get_directory_entry for phone numbers and opening hours; use search_swiss_directory or browse_business_category to find an entry_id first.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | The entry's public_id, as returned by search_swiss_directory, browse_business_category, or reverse_phone_lookup. |
| lang | string | – | Response language: de, fr, it, or en. Defaults to de. |
| Name | Type | Req | Description |
|---|---|---|---|
| advertising_block_note | string | yes | – |
| entry | object | yes | – |
| retrieved_at | string | yes | – |
| source | object | yes | – |
No examples provided.
reverse_phone_lookup Reverse phone lookup ~118
Looks up the public directory entry (or entries) associated with a Swiss phone number. Accepts national ("079 123 45 67"), E.164 ("+41791234567"), or compact notation. Returns an empty result list when the number has no findable public listing.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Response language: de, fr, it, or en. Defaults to de. |
| phone_number | string | yes | The phone number to look up, in any common Swiss notation (national, E.164, or compact). |
| Name | Type | Req | Description |
|---|---|---|---|
| results | null|array | yes | – |
| retrieved_at | string | yes | – |
| source | object | yes | – |
No examples provided.
search_swiss_directory Search the Swiss directory ~245
Full-text search over the Swiss public phone/business directory (1820.ch). Matches ALL words in query, so a short keyword works best; put any place name in location, not query. For "business type X in place Y", browse_business_category with a category slug is an alternative. Use get_directory_entry for phone numbers and opening hours of a specific result.
| Name | Type | Req | Description |
|---|---|---|---|
| entry_type | string | – | Restrict results to person, business, or all entries. |
| lang | string | – | Response language: de, fr, it, or en. Defaults to de. |
| limit | integer | – | Maximum number of results, 1-20. |
| location | string | – | Locality, postcode, or canton (e.g. "Baden", "5400", "ZH") to narrow the search. Always put a place name here, never in query. |
| query | string | yes | One short keyword: a person's or company name, or ONE business type (e.g. "Müller", "Migros", "Coiffeur"). Every word must match, so no sentences or extra adjectives. Never put a place name here — us… |
| Name | Type | Req | Description |
|---|---|---|---|
| advertising_block_note | string | yes | – |
| results | null|array | yes | – |
| retrieved_at | string | yes | – |
| source | object | yes | – |
No examples provided.
How do I install the 1820.ch – Telefonbuch Schweiz MCP server?
1820.ch – Telefonbuch Schweiz is a hosted endpoint at https://mcp.1820.ch/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 · mcp.1820.ch
claude mcp add --transport http ch-1820-telefonbuch 'https://mcp.1820.ch/mcp'
What is the 1820.ch – Telefonbuch Schweiz MCP server?
1820.ch – Telefonbuch Schweiz is an MCP server listed in the public MCP registry as ch.1820/telefonbuch. Swiss phone directory: search people and businesses, reverse number lookup, business categories. This page covers its hosted endpoint (https://mcp.1820.ch/mcp).
Is the 1820.ch – Telefonbuch Schweiz MCP server safe to use?
1820.ch – Telefonbuch Schweiz scores 85 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 1820.ch – Telefonbuch Schweiz MCP server expose?
1820.ch – Telefonbuch Schweiz exposes 4 tools: browse_business_category, get_directory_entry, reverse_phone_lookup, search_swiss_directory. Their descriptions and schemas cost roughly 660 tokens of context every time the server is loaded.
Does the 1820.ch – Telefonbuch Schweiz MCP server require authentication?
No. We connected to 1820.ch – Telefonbuch Schweiz without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 1820.ch – Telefonbuch Schweiz MCP server still maintained?
1820.ch – Telefonbuch Schweiz is still listed as active in the MCP registry. We last reached this channel on 7 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 1820.ch – Telefonbuch Schweiz MCP server?
VerifyMCP ran 13 checks on 1820.ch – Telefonbuch Schweiz, 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.