Remote MCP · Endpoint

io.github.physics-star-cat/databutler-provenance MCP server

No — it is up, but it requires credentials. io.github.physics-star-cat/databutler-provenance answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://databutler.dev/api/mcp/provenance

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
io.github.physics-star-cat/databutler-provenance
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Live trust signals for domains & packages: age, registrar, typosquat resemblance.
Website
https://databutler.dev/api
Repository
https://github.com/physics-star-cat/databutler
Listing
From the official MCP registry (active).
Recent checks of io.github.physics-star-cat/databutler-provenance
CheckedResultHandshake
1 hour agoCredentials required—
1 day agoCredentials required—
2 days agoCredentials required—
3 days agoCredentials required—
4 days agoCredentials required—
5 days agoCredentials required—
6 days agoHandshake completed58 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed146 ms
14 days agoHandshake completed77 ms
16 days agoHandshake completed61 ms
18 days agoHandshake completed94 ms
20 days agoHandshake completed52 ms
22 days agoHandshake completed61 ms
24 days agoHandshake completed105 ms
26 days agoHandshake completed94 ms
28 days agoHandshake completed196 ms
29 days agoHandshake completed68 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.

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 io.github.physics-star-cat/databutler-provenance and makes no claim about it beyond what these checks measured.