Remote MCP · Endpoint
Précis Finance MCP MCP server
No — it is up, but it requires credentials. Précis Finance MCP answered 1 hour ago with an authentication challenge rather than a session.
Auth requiredLast checked 1 hour ago
Server URL
https://mcp.precis.finance/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.github.precis-finance/precis-finance-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 20 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Public read-only Précis Finance MCP demo with synthetic data; no account or credentials required.
- Website
- https://precis.finance/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Credentials required | — |
| 1 day ago | Handshake completed | 472 ms |
| 2 days ago | Handshake completed | 450 ms |
| 3 days ago | Handshake completed | 441 ms |
| 4 days ago | Handshake completed | 448 ms |
| 5 days ago | Handshake completed | 452 ms |
| 6 days ago | Handshake completed | 455 ms |
| 9 days ago | Handshake completed | 462 ms |
| 11 days ago | Handshake completed | 626 ms |
| 14 days ago | Handshake completed | 434 ms |
| 16 days ago | Handshake completed | 434 ms |
| 18 days ago | Handshake completed | 466 ms |
| 20 days ago | Handshake completed | 448 ms |
| 22 days ago | Handshake completed | 431 ms |
| 24 days ago | Handshake completed | 486 ms |
| 26 days ago | Handshake completed | 438 ms |
| 28 days ago | Handshake completed | 430 ms |
| 29 days ago | Handshake completed | 434 ms |
The last 18 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 Précis Finance MCP and makes no claim about it beyond what these checks measured.