Remote MCP · Endpoint

FilmRightsProof MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://filmrightsproof.davisvillelabs.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
com.davisvillelabs.filmrights/filmrightsproof
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
61.1% from 18 checks
Described by its publisher as
Film/TV public-record rights intelligence for AI agents with provenance and bounded verification.
Website
https://filmrightsproof.davisvillelabs.com/
Repository
https://github.com/davisvillelabs/filmrightsproof
Listing
From the official MCP registry (active).
Recent checks of FilmRightsProof
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoHandshake completed387 ms
12 days agoHandshake completed413 ms
15 days agoHandshake completed277 ms
17 days agoHandshake completed468 ms
19 days agoHandshake completed307 ms
21 days agoHandshake completed450 ms
23 days agoHandshake completed464 ms
25 days agoHandshake completed315 ms
26 days agoHandshake completed232 ms
28 days agoHandshake completed634 ms
29 days agoHandshake completed479 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 22 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 FilmRightsProof and makes no claim about it beyond what these checks measured.