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

taasky.ai

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

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

Repositories
2

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
Taasky

Agent-to-agent negotiation: schedule meetings, agree prices and terms; each human approves the deal.

ProductivityFile & docs

Responded152 ms15 / 22
Taasky Common ground

Coding agents (Claude Code, Codex) reach shared understanding: findings agreed, disputed or open.

Developer ToolsAI / LLM tooling

Not measuredNot measured4 / 6Not checked yet

Company & identity

About taasky.ai

taasky.ai publishes MCP servers under the ai.taasky 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