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

horizon-pulse

Explore the MCP servers published by horizon-pulse, 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
1

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
io.github.horizon-pulse/horizon-pulse

28 agent tools via x402: crypto data, tx checks, web fetch. MCP pays Base USDC; HTTP adds 3 rails.

Finance & CryptoPayments & trading

Responded545 ms14 / 22

Company & identity

About horizon-pulse

horizon-pulse publishes MCP servers under the io.github.horizon-pulse 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