Remote MCP · Endpoint

Content Provenance MCP server

No. Content Provenance answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bonissystems.com/api/knox/agents/content-provenance/mcp

The last check completed an MCP handshake.

Registry name
com.bonissystems/content-provenance
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
128 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Listing
From the official MCP registry (active).
Recent checks of Content Provenance
CheckedResultHandshake
1 hour agoHandshake completed128 ms
10 hours agoHandshake completed229 ms
1 day agoHandshake completed129 ms
2 days agoHandshake completed129 ms
4 days agoHandshake completed125 ms
4 days agoHandshake completed130 ms
5 days agoHandshake completed159 ms
6 days agoHandshake completed317 ms
8 days agoHandshake completed591 ms
11 days agoHandshake completed114 ms
13 days agoHandshake completed155 ms
16 days agoHandshake completed139 ms
18 days agoHandshake completed174 ms
20 days agoHandshake completed140 ms
22 days agoHandshake completed130 ms
24 days agoHandshake completed230 ms
26 days agoHandshake completed113 ms
27 days agoHandshake completed99 ms
29 days agoHandshake completed164 ms

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

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