Remote MCP · Endpoint

CiteMe MCP server

No. CiteMe answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://citeme.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.citeme/citeme
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
179 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search papers, format citations in 60 styles, and verify bibliographies against scholarly sources.
Listing
From the official MCP registry (active).
Recent checks of CiteMe
CheckedResultHandshake
6 hours agoHandshake completed179 ms
2 days agoHandshake completed210 ms
4 days agoHandshake completed565 ms
5 days agoHandshake completed156 ms
7 days agoHandshake completed127 ms
8 days agoHandshake completed132 ms
9 days agoHandshake completed117 ms
12 days agoHandshake completed135 ms
13 days agoHandshake completed114 ms
15 days agoHandshake completed143 ms
16 days agoHandshake completed203 ms
17 days agoHandshake completed167 ms
18 days agoHandshake completed109 ms
19 days agoHandshake completed128 ms
20 days agoHandshake completed147 ms
21 days agoHandshake completed101 ms
22 days agoHandshake completed272 ms

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

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