Remote MCP · Endpoint
org.pubscope/pubscope MCP server
No. org.pubscope/pubscope answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://pubscope.org/api/mcp
The last check completed an MCP handshake.
- Registry name
- org.pubscope/pubscope
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 381 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Journal intelligence: indexing, quartile, APC, trust score, measured publication times
- Website
- https://pubscope.org/mcp
- Repository
- https://github.com/nadir-ib/pubscope-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 381 ms |
| 1 day ago | Handshake completed | 355 ms |
| 2 days ago | Handshake completed | 155 ms |
| 3 days ago | Handshake completed | 354 ms |
| 4 days ago | Handshake completed | 358 ms |
| 5 days ago | Handshake completed | 348 ms |
| 6 days ago | Handshake completed | 365 ms |
| 8 days ago | Handshake completed | 189 ms |
| 11 days ago | Handshake completed | 358 ms |
| 13 days ago | Handshake completed | 367 ms |
| 16 days ago | Handshake completed | 415 ms |
| 18 days ago | Handshake completed | 389 ms |
| 20 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 341 ms |
| 24 days ago | Handshake completed | 374 ms |
| 26 days ago | Handshake completed | 350 ms |
| 27 days ago | Handshake completed | 346 ms |
| 29 days ago | Handshake completed | 352 ms |
| 29 days ago | Handshake completed | 153 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 org.pubscope/pubscope and makes no claim about it beyond what these checks measured.