Remote MCP · Endpoint

JPFreeSoft Catalog MCP server

No. JPFreeSoft Catalog answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://jpfreesoft.com/api/mcp/

The last check completed an MCP handshake.

Registry name
com.jpfreesoft/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.49 s
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Japanese software and AI tools; read recorded facts with source links. Read-only.
Listing
From the official MCP registry (active).
Recent checks of JPFreeSoft Catalog
CheckedResultHandshake
34 minutes agoHandshake completed1.49 s
9 days agoHandshake completed110 ms
10 days agoHandshake completed1.24 s
11 days agoHandshake completed1.01 s
12 days agoHandshake completed429 ms
14 days agoHandshake completed786 ms
14 days agoHandshake completed752 ms
15 days agoHandshake completed740 ms
17 days agoHandshake completed975 ms
19 days agoHandshake completed655 ms
21 days agoHandshake completed738 ms
24 days agoHandshake completed2.47 s
26 days agoHandshake completed3.26 s
28 days agoHandshake completed2.70 s

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

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 JPFreeSoft Catalog and makes no claim about it beyond what these checks measured.