Remote MCP · Endpoint

Asia Pulse MCP server

No. Asia Pulse answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://asia-pulse.com/mcp

The last check completed an MCP handshake.

Registry name
com.asia-pulse/asia-pulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
619 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Korea & Japan market records for agents. x402 payment inside MCP, Base USDC.
Listing
From the official MCP registry (active).
Recent checks of Asia Pulse
CheckedResultHandshake
1 hour agoHandshake completed619 ms
2 days agoHandshake completed625 ms
4 days agoHandshake completed625 ms
6 days agoHandshake completed610 ms
8 days agoHandshake completed644 ms
10 days agoHandshake completed609 ms
11 days agoHandshake completed616 ms
13 days agoHandshake completed636 ms
14 days agoHandshake completed616 ms
15 days agoHandshake completed625 ms
18 days agoHandshake completed647 ms
19 days agoHandshake completed612 ms
21 days agoHandshake completed612 ms
22 days agoHandshake completed602 ms
23 days agoHandshake completed603 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Asia Pulse and makes no claim about it beyond what these checks measured.