com.grain64.sitecite/sitecite
com.grain64.sitecite/sitecite
Is the com.grain64.sitecite/sitecite MCP server down? It gave no valid answer in the probe of 2026-11-15: not MCP (HTTP 200). One failed probe is not an outage.
Cited clinical trial site shortlists and CRO site-list checks from ClinicalTrials.gov.
not MCP no valid answer since 2026-11-15 · probed 2026-11-15 · HTTP 200
Streamable HTTP error: Unexpected content type: text/html; charset=utf-8
- Endpoint
- https://sitecite.grain64.com/mcp (streamable-http)
- Host
- sitecite.grain64.com
- Website
- https://sitecite.grain64.com/docs/#mcp
- Registry
- active, updated 2026-11-12 · registry entry
- Changes
- 3 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention clinicaltrials or shortlists.
- ai.smithery/plainyogurt21-clintrials-mcp · needs auth
- Prognyx oncology intelligence com.prognyx/oncology-intelligence · alive
- reapx clinical trials - ClinicalTrials.gov study records dev.reapx/clinical-trials · needs auth
- PubMed Clinical Research io.github.Taru0208/pubmed-mcp-server · needs auth
- io.github.cyanheads/clinicaltrialsgov-mcp-server · alive
- ToolScout Software Recommendation io.github.pcaiano/toolscout · alive
- io.github.sercanmetalore/clinical-fda-mcp · server error
- Biolab MCP Server io.github.srikarjy/biolab-mcp-server · server error
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-15 11:09 | not MCP | ||||
| 2026-11-14 10:38 | alive | 1.2 s | 2 | 1.5k | 911 |
| 2026-11-12 11:29 | alive | 1.1 s | 2 | 1.5k | 894 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-11-15. One failed probe is not an outage: the board calls a server down after two days without a valid answer. The next probe runs within a day.
- The endpoint answers HTTP 200, but not with a valid MCP initialize result. Common causes: the URL is a web page or a REST API and not the MCP endpoint, the server answers a JSON-RPC error on initialize, or the response is HTML.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.