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

sapph1re

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

Listed servers
3

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

Sampled servers
2

Active servers with a recorded connection probe

Latest probe connected
0

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

Repositories
3

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
Feedback Synthesis MCP

Synthesize GitHub Issues, HN and App Store reviews into ranked pain clusters. Pay-per-call x402.

Developer ToolsCode & DevOps

UnreachableNot measured5 / 22
MCP Billing Gateway

Billing proxy for MCP servers. Adds Stripe and x402 crypto payments without writing billing code.

Finance & CryptoPayments & trading

UnreachableNot measured5 / 22
FinData MCP

Stocks, fundamentals, FRED economics, SEC filings & crypto. x402 micropayments, $0.01/call.

Finance & CryptoCode & DevOps

Not measuredNot measured3 / 6Not checked yet

Company & identity

About sapph1re

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