Remote MCP · Endpoint

LLM Prover MCP server

No. LLM Prover answered an MCP handshake 9 hours ago.

Up · key neededLast checked 9 hours ago

Server URL

https://mcp.llmprover.pysolvr.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.pysolvr/llmprover
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
49 ms
Tools exposed
Behind credentials
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
LLM evaluation: compare models on cost and quality, score outputs, run benchmarks, analyse agents.
Listing
From the official MCP registry (active).
Recent checks of LLM Prover
CheckedResultHandshake
9 hours agoHandshake completed49 ms
4 days agoHandshake completed1.51 s
7 days agoHandshake completed1.52 s

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

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