Remote MCP · Endpoint

Doaj MCP server

No. Doaj answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/doaj/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/doaj
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
126 ms
Tools exposed
48 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
DOAJ MCP — Directory of Open Access Journals
Listing
From the official MCP registry (active).
Recent checks of Doaj
CheckedResultHandshake
1 hour agoHandshake completed126 ms
1 day agoHandshake completed99 ms
2 days agoHandshake completed59 ms
3 days agoHandshake completed94 ms
4 days agoHandshake completed51 ms
5 days agoHandshake completed74 ms
6 days agoHandshake completed72 ms
8 days agoHandshake completed227 ms
11 days agoHandshake completed75 ms
13 days agoHandshake completed99 ms
16 days agoHandshake completed166 ms
18 days agoHandshake completed60 ms
20 days agoHandshake completed71 ms
22 days agoHandshake completed66 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed57 ms
27 days agoHandshake completed84 ms
29 days agoHandshake completed142 ms

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

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