28 pay-per-event tools for regulatory, sanctions, procurement, and corporate-registry monitoring.
https://mcp.apify.com?tools=stefano_seggio/actor-18-b2b-lead-magnet,stefano_seggio/actor-19-maritime-sanctions-monitor,stefano_seggio/actor-20-mdb-procurement-monitor,stefano_seggio/actor-21-patent-ip-enforcement-monitor,stefano_seggio/actor-22-drug-safety-recalls-monitor,stefano_seggio/actor-24-clinical-trials-delta-engine,stefano_seggio/ai-crawler-content-signal-permission-monitor,stefano_seggio/aozora-bunko-public-domain-text-feed,stefano_seggio/australia-grantconnect-monitor,stefano_seggio/cordoba-compras-monitor,stefano_seggio/diario-oficial-cl-monitor,stefano_seggio/emerging-market-sovereign-debt-auction-monitor,stefano_seggio/entrerios-compras-monitor,stefano_seggio/eu-ted-procurement-delta-monitor,stefano_seggio/florida-tenders-monitor,stefano_seggio/kipris-patent-trademark-status-monitor,stefano_seggio/mendoza-compras-monitor,stefano_seggio/page-metadata-extractor,stefano_seggio/pba-tenders-monitor,stefano_seggio/regione-lombardia-grants-registry-monitor,stefano_seggio/salta-compras-monitor,stefano_seggio/santafe-compras-monitor,stefano_seggio/sec-enforcement-litigation-delta-feed,stefano_seggio/singapore-acra-registry-monitor,stefano_seggio/tucuman-compras-monitor,stefano_seggio/uae-corporate-registry-monitor,stefano_seggio/uk-hse-enforcement-monitor,stefano_seggio/uk-modern-slavery-statement-registry-monitorneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 41 ms, 95th 2038 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
[](https://referencesource.org/mcp-health/server/io-github-stefanoseggio-delta-registry/)
The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key.
One HTTP POST carrying a JSON-RPC initialize, and if
that succeeds, a tools/list. Nothing here is a score, a rating or a
judgement about whether the server is any good — only whether an ordinary MCP
client could complete a session with it on the day we asked.
“Needs credentials” is not a fault: it means the endpoint wants
an account, which is a perfectly reasonable thing for it to want.
The tool contract row is a digest of what
tools/list returned — each tool's name, description and input
schema, hashed — so that a rename, a newly-required field or a rewritten
description can be spotted even though none of them breaks the connection. We
keep the digests and nothing else: no tool name, description or schema of
anybody's is stored or republished here, which is also why this can say that a
contract moved and by how much, but not what it now says.
The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]