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

jsymen1290

Explore the MCP servers published by jsymen1290, 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
2

Active servers with a recorded connection probe

Latest probe connected
2

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
POKT Agent tools

Pine Script backtest-trap checks, backtest reconciliation and official Korean finance data.

Developer ToolsCode & DevOps

Responded1528 ms14 / 22
POKT Agent Korea data (x402 paid)

Korean company due diligence, sanctions screening, Upbit/Bithumb events, HWP. Pay per call (x402).

Developer ToolsCode & DevOps

Responded64 ms11 / 22

Company & identity

About jsymen1290

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