Remote MCP · Endpoint

Content Provenance MCP server

No. Content Provenance answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
140 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 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
2 hours agoHandshake completed140 ms
2 days agoHandshake completed130 ms
4 days agoHandshake completed230 ms
6 days agoHandshake completed113 ms
7 days agoHandshake completed99 ms
9 days agoHandshake completed164 ms
10 days agoHandshake completed177 ms
11 days agoHandshake completed299 ms
14 days agoHandshake completed137 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed170 ms
18 days agoHandshake completed109 ms
19 days agoHandshake completed139 ms
20 days agoHandshake completed148 ms
21 days agoHandshake completed144 ms
22 days agoHandshake completed138 ms
23 days agoHandshake completed138 ms
24 days agoHandshake completed187 ms

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

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.