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

Weavatrix

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

Listed servers
4

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
4

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.Weavatrix/weavatrix-online

Weavatrix Online extension: guarded sync, advisories, malware review, architecture contracts.

LegalCode & DevOps

Not measuredNot measured4 / 6Not checked yet
io.github.Weavatrix/weavatrix-refactor

Transactional refactoring extension with 11 evidence-backed tools, previews, and rollback.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Weavatrix

Native Weavatrix MCP: 65 read-only tools for code, local CI, n8n, Dify, agents, Mermaid, Web3.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet
Weavatrix Quality

Revision-bound quality planning, execution, evidence, proof, and Playwright authoring.

Developer ToolsBrowser & web scraping

Not measuredNot measured4 / 6Not checked yet

Company & identity

About Weavatrix

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