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

vibgrate.com

Explore the MCP servers published by vibgrate.com, 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
1

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
com.vibgrate/mcp

Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.

SecurityMonitoring & observability

Requires authNot measured4 / 22
com.vibgrate/ai-context

Local-first MCP server: version-correct library docs, code map, and offline drift for your repo.

Developer ToolsCode & DevOps

Not measuredNot measured4 / 6Not checked yet

Company & identity

About vibgrate.com

vibgrate.com publishes MCP servers under the com.vibgrate namespace. This namespace uses a reverse-domain identity in the directory.

Namespace verification connects the publisher to its registry identity. It does not certify the security of individual servers.

Source repositories