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

Pact-Community-Organization

Explore the MCP servers published by Pact-Community-Organization, 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
0

Active servers with a recorded connection probe

Latest probe connected
0

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
Chainweb API

Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Pact Tooling

Pact 5 tooling: REPL test runs, trap scanning, gas estimation, interface diff, format checks.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About Pact-Community-Organization

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