Lead enrichment, email/phone, hiring, news, new companies, contacts and RSS, via Apify.
https://mcp.apify.com/?tools=tudorlane/company-from-domain,tudorlane/lead-enrichment,tudorlane/email-verify,tudorlane/phone-validate,tudorlane/company-hiring-watch,tudorlane/job-title-salary,tudorlane/news-feed-search,tudorlane/adverse-media-watch,tudorlane/topic-trends,tudorlane/website-contact-details,tudorlane/rss-feed-watch,tudorlane/uk-new-companies-watchneeds credentials
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of our visits in the last 7 days · 0% in the last 30 |
| Handshake latency | median 41 ms, 95th 41 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 401 |
[](https://referencesource.org/mcp-health/server/io-github-tudorlane-tudorlane-leads-news/)
The badge shows the most recent probe. It is generated from the same file this page is, updates after each day's pass, 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 day-by-day totals · every server we probe, A–Z · feed.json · licence · corrections and removals: contact@referencesource.org