MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

Publisher portfolio

api.ransomware-tracker.com

Explore the MCP servers published by api.ransomware-tracker.com, with independent connection checks, performance measurements, and setup instructions for each project.

Listed servers
1

Active projects in this portfolio. Deleted and deprecated registry rows are excluded.

Sampled servers
1

Active servers with a recorded connection probe

Latest probe connected
1

Latest stored probe connected. This is not a live guarantee.

Repositories
0

Distinct source repositories linked by the active listings

Portfolio overview

MCP servers

Compare connection status and measurements. Open a server for its tools, check results, and client configuration.

Dated server measurements. The status describes the last probe or a listed authentication requirement. Checks that have not been measured are not failures. Open a server to inspect the evidence.
Server / capabilityLast probeMedian latencyChecks passedLast checked
Dragons Eye Ransomware Claims

Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC).

Finance & CryptoPayments & trading

Responded103 ms13 / 22

Company & identity

About api.ransomware-tracker.com

api.ransomware-tracker.com publishes MCP servers under the com.ransomware-tracker.api namespace. This namespace uses a reverse-domain identity in the directory.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.

Source repositories

No source repositories listed yet.