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

g-digital-by-Garrigues

Explore the MCP servers published by g-digital-by-Garrigues, 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
0

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
io.github.g-digital-by-Garrigues/ead-factory

MCP server for EAD Factory: qualified evidence, signature, notifications and chat via AI agents.

Developer ToolsCommunication & messaging

Not measuredNot measured4 / 6Not checked yet
io.github.g-digital-by-Garrigues/gocertius

MCP server for GoCertius: certified evidence, dossiers, notifications and chats via AI agents.

Developer ToolsCommunication & messaging

Not measuredNot measured4 / 6Not checked yet
io.github.g-digital-by-Garrigues/ead-enterprise-suite

MCP server for EAD Enterprise Suite - signatures, evidence, notifications, dossiers via AI agents.

Developer ToolsCommunication & messaging

Not measuredNot measured4 / 6Not checked yet

Company & identity

About g-digital-by-Garrigues

g-digital-by-Garrigues publishes MCP servers under the io.github.g-digital-by-Garrigues 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