Remote MCP · Endpoint

Clinical Trial & Medical Research Tracker — buy per-query in-session (trialwatch) MCP server

No. Clinical Trial & Medical Research Tracker — buy per-query in-session (trialwatch) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://a2awire.com/mcp/data/trialwatch-new-clinical-trials-medical-research-results-0f9d9f/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-medical-research-trial-results-tracker
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
16 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Medical research: new trial results tracker. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/trialwatch-new-clinical-trials-medical-research-results-0f9d9f
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of Clinical Trial & Medical Research Tracker — buy per-query in-session (trialwatch)
CheckedResultHandshake
1 hour agoHandshake completed73 ms
1 day agoHandshake completed126 ms
2 days agoHandshake completed63 ms
3 days agoHandshake completed90 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed69 ms
6 days agoHandshake completed78 ms
9 days agoHandshake completed64 ms
12 days agoHandshake completed215 ms
14 days agoHandshake completed55 ms
16 days agoHandshake completed119 ms
18 days agoHandshake completed55 ms
20 days agoFailed - the request timed out—
22 days agoHandshake completed136 ms
25 days agoHandshake completed28 ms
26 days agoHandshake completed62 ms
28 days agoHandshake completed137 ms
29 days agoHandshake completed46 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Clinical Trial & Medical Research Tracker — buy per-query in-session (trialwatch) and makes no claim about it beyond what these checks measured.