Uidwatch is listed as active in the registry but did not answer our last check. It exposes 12 tools.
Swiss bankruptcy, liquidation and register alerts for a UID list. Source: SHAB. Webhook, API, email.
Uptime history
27 days of history · worst day 0%
27 days agonow
0.0%
Uptime 24h
0 of 91 checks
12
Tools
read from the server
193 ms
Response time
average over 24h
open, no key
Access
streamable-http
Uidwatch does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
run in your terminal
claude mcp add uidwatch --transport http https://uidwatch.tollwyn.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://uidwatch.tollwyn.com/mcp~/.codex/config.toml
[mcp_servers.uidwatch]
url = "https://uidwatch.tollwyn.com/mcp".cursor/mcp.json
{
"mcpServers": {
"uidwatch": {
"url": "https://uidwatch.tollwyn.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"uidwatch": {
"type": "http",
"url": "https://uidwatch.tollwyn.com/mcp"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
watchlist
watchlist_add
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.
watchlist_list
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).
watchlist_remove
Remove one entry from the watchlist; name its group if it has one.
watchlist_replace
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.
webhook
webhook_create
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.
webhook_delete
Delete a webhook endpoint; no more events are posted to it.
webhook_list
The webhook endpoints of the account with their kinds.
webhook_test
Post a sample event marked "test": true to a webhook endpoint now and tell how it answered (10 per minute).
account
account_status
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.
billing
billing_checkout
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.
events
events_list
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.
uidwatch
uidwatch_signup
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://uidwatch.tollwyn.com/mcp | streamable-http | answering | 193 ms | 13 min ago |
Alternatives to Uidwatch
same job, measured the same wayHookpulse
by hookpulse
Dead-man switch for cron and webhooks: ingest URL, miss detection, alerts and a status feed.
formcarry
by formcarry
Set up form handling for your site (email alerts, auto replies, webhooks) and query submissions.
Meridian
by the-meridian
Plans, deploys, logs, webhooks and API alerts for Shopify apps built on Meridian.
Sendora
by sendora
Sendora's docs and API for coding agents: send test mail, read the log, set up webhooks.
A
AI Deprecations
by aideprecations
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
AI Deprecations
by val-web-aideprecations-89b1777ed29f11f1a12e1607ee4eb77e
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Ask the Grid
by parisi-labs
Live U.S. electric-grid data, forecasts, alerts, and analysis across major grid regions.
Ironflow: Hyperliquid data
by ironflowsh
Hyperliquid data and liquidation alerts for AI agents: fills, candles, funding, wallet analytics.
Uidwatch — questions
Answers built from our own checks of this server.
What can Uidwatch do?
It exposes 12 tools, read directly from the server on our last check. Among them: account_status, billing_checkout, events_list, uidwatch_signup, watchlist_add, watchlist_list and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Uidwatch mostly used for?
Its tools cluster around watchlist and webhook. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Uidwatch working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 193 ms. The bar chart above shows every period we have measured.
The registry lists Uidwatch as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Uidwatch?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Uidwatch need an API key?
No. Uidwatch completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.