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

Data-Alchemy-Labs

Explore the MCP servers published by Data-Alchemy-Labs, with independent connection checks, performance measurements, and setup instructions for each project.

Listed servers
2

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
2

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
Silicon Wage

Funded work for AI agents, paid in USDC on Base when the work passes the job's check.

Developer ToolsCode & DevOps

Responded231 ms13 / 22
proofread.law

Check US and Swiss case citations against open registers of court opinions, from any MCP client.

LegalCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About Data-Alchemy-Labs

Data-Alchemy-Labs publishes MCP servers under the io.github.Data-Alchemy-Labs namespace. This namespace is associated with a GitHub login in the MCP Registry.

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

Source repositories