com.tollwyn/uidwatch
REMOTE · UIDWATCH.TOLLWYN.COM
Swiss bankruptcy, liquidation and register alerts for a UID list. Source: SHAB. Webhook, API, email.
Available components
Last scanned (10 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Finance and Payments
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (watchlist_replace). See how to fix → View diagnostics → Fail
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1185 tokens (~98/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 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.
- 17 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.
- 15 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.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
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 17 Oct 2026 · Probed https://uidwatch.tollwyn.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tollwyn.com | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6ca8dc4e906c3ac863a1e2f26838ad791b5 |
| SANs: *.tollwyn.com, tollwyn.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 insecure
Validation of uidwatch.tollwyn.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tollwyn.com. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://uidwatch.tollwyn.com/mcp | Verified | 200 | |
| http (plaintext) | http://uidwatch.tollwyn.com/mcp | HTTPS enforced | 308 | https://uidwatch.tollwyn.com/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 →
account_status Account status ~59
The account: plan (trial, monitor or paused), whether the list is monitored, the limit and usage in entries, the end of the trial, whether the email address is confirmed, and last_scan_at, the last successful check of the gazette.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
billing_checkout Subscribe ~73
A Stripe Checkout link for the subscription: CHF 33 per month per package of 2500 entries, 1 to 10 packages, cancel monthly. A person, or an agent with its own payment method, opens the link and pays there.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | integer | – | Packages to start with; adjustable in Checkout |
No output schema declared.
No examples provided.
events_list List events ~144
Events for the watchlist after a cursor, oldest first: bankruptcies, compositions, debt enforcement, liquidations, deletions, register deficiencies and changes, and new entries published in the Swiss Official Gazette of Commerce (SHAB), each with a link to the notice and its signed PDF. Keep next_cursor and pass it as cursor next time: every event comes exactly once. historical "true" filters the findings of the initial check, published before the entry was added.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| group | string | – | – |
| historical | string | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| uid | string | – | – |
No output schema declared.
No examples provided.
uidwatch_signup Sign up ~228
Create a UIDWatch account and get its API key. The key is shown only in this answer: keep it and send it as "Authorization: Bearer <key>" in the configuration of the MCP client, which every other tool needs. accept_terms must be true: it accepts the terms of service (https://uidwatch.tollwyn.com/terms?via=mcp-registry), including the data processing terms in section 8, on behalf of the business that signs up. The trial lasts 30 days and watches 20 entries until a person confirms the email address from the mail UIDWatch sends, then 2500. via is an optional partner id; without one the account counts as signed up through MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | yes | Accepts the terms at https://uidwatch.tollwyn.com/terms?via=mcp-registry, including the data processing terms in section 8, on behalf of the business that signs up. |
| string | yes | – | |
| via | string | – | Optional partner id: lower-case words joined by hyphens |
No output schema declared.
No examples provided.
watchlist_add Add to the watchlist ~123
Add entries to the watchlist, or change the reference of entries already on it. UIDs are accepted as CHE-123.456.789, CHE123456789 or with MWST/TVA/IVA; the check digit must match. Each entry may carry your reference (e.g. a customer number) and a group (e.g. the client a debtor belongs to). All or nothing: one invalid UID rejects the call with every problem listed. New entries get an initial check of the history in the gazette.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
watchlist_list List the watchlist ~73
A page of the watchlist, oldest entry first, optionally of one group. Each entry tells whether its initial check is done (checked_at) and whether it is within the limit of the plan (monitored).
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
watchlist_remove Remove from the watchlist ~39
Remove one entry from the watchlist; name its group if it has one.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | – |
| uid | string | yes | – |
No output schema declared.
No examples provided.
watchlist_replace Replace the watchlist ~141
Replace the whole watchlist with these entries, e.g. to sync it from an ERP every night: entries missing from items are removed, entries that stay keep their date. UIDs are accepted as CHE-123.456.789, CHE123456789 or with MWST/TVA/IVA; the check digit must match. Each entry may carry your reference (e.g. a customer number) and a group (e.g. the client a debtor belongs to). All or nothing: one invalid UID rejects the call with every problem listed. New entries get an initial check of the history in the gazette.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
webhook_create Add a webhook ~92
Add a webhook endpoint (https on a public address, at most 5): every new event of the chosen kinds (default: all) is posted to it as JSON, signed with HMAC-SHA256 in the UIDWatch-Signature header. The signing secret is returned only in this answer.
| Name | Type | Req | Description |
|---|---|---|---|
| kinds | array | – | Default: all kinds |
| url | string | yes | https on a public address |
No output schema declared.
No examples provided.
webhook_delete Delete a webhook ~28
Delete a webhook endpoint; no more events are posted to it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
webhook_list List webhooks ~18
The webhook endpoints of the account with their kinds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
webhook_test Test a webhook ~39
Post a sample event marked "test": true to a webhook endpoint now and tell how it answered (10 per minute).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the com.tollwyn/uidwatch MCP server?
com.tollwyn/uidwatch is a hosted endpoint at https://uidwatch.tollwyn.com/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 · uidwatch.tollwyn.com
claude mcp add --transport http com-tollwyn-uidwatch 'https://uidwatch.tollwyn.com/mcp'
What is the com.tollwyn/uidwatch MCP server?
com.tollwyn/uidwatch is an MCP server listed in the public MCP registry as com.tollwyn/uidwatch. Swiss bankruptcy, liquidation and register alerts for a UID list. Source: SHAB. Webhook, API, email. This page covers its hosted endpoint (https://uidwatch.tollwyn.com/mcp).
Is the com.tollwyn/uidwatch MCP server safe to use?
com.tollwyn/uidwatch scores 63 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 com.tollwyn/uidwatch MCP server expose?
com.tollwyn/uidwatch exposes 12 tools: uidwatch_signup, watchlist_replace, watchlist_add, watchlist_list, watchlist_remove, and 7 more. Their descriptions and schemas cost roughly 1,057 tokens of context every time the server is loaded.
Does the com.tollwyn/uidwatch MCP server require authentication?
No. We connected to com.tollwyn/uidwatch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.tollwyn/uidwatch MCP server still maintained?
com.tollwyn/uidwatch is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.