Skip to content

databutler-provenance MCP server

io.github.physics-star-cat/databutler-provenancephysics-star-catstreamable-httpv1.0.0Scanned

Live trust signals for domains & packages: age, registrar, typosquat resemblance.

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the databutler-provenance MCP server can do

The databutler-provenance MCP server is published by the GitHub account physics-star-cat. It has 2 tools. It can create or change data (2 tools: domain_provenance and package_provenance), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (domain_provenance and package_provenance).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in.

Last scanned Oct 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • domain_provenanceWho runs this domain?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Who runs this domain? Live RDAP lookup: registration date and age, registrar, nameservers, status, whether the registrant is redacted, plus a typosquat check (edit-distance / brand-substring) against high-value brands. A very recently registered domain resembling a bank or big brand is a classic phishing signal — but report it as a signal, not a conclusion.

    Annotations the server declares

    • title: Domain provenance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • package_provenanceWho publishes this package, and is it a typosquat?Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Who publishes this package, and is it a typosquat? Live npm or PyPI lookup: first-publish date and age, release count, latest version, maintainers/author, linked repo, plus a typosquat check against popular package names. Use when an agent is about to install or recommend an unfamiliar dependency.

    Annotations the server declares

    • title: Package provenance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
403
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
no
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint asks for credentials (HTTP 403) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.

    Matched text

    https://databutler.dev/api/mcp/provenance: initialize answered HTTP 403, without a WWW-Authenticate header

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 403
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 403; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 200 to 403
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • WWW-Authenticate on 401: not observed to no

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http databutler-provenance https://databutler.dev/api/mcp/provenance
claude mcp add --transport http databutler-provenance https://databutler.dev/api/mcp/provenance

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__databutler-provenance__domain_provenance",
      "mcp__databutler-provenance__package_provenance"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as databutler-provenance. Review it before you use it.

Capability tags behind 2 rules
  • mcp__databutler-provenance__domain_provenance untrusted-input
  • mcp__databutler-provenance__package_provenance untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.physics-star-cat/databutler-provenance/verify?hash=4ee35b85200e981367487ec403a00affda4d581cebbeb049e6be4eae678b0504" | jq -e '.changed == false'

Pinned hash 4ee35b85200e, from Oct 21, 2026, 19:33 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.physics-star-cat/databutler-provenance/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.physics-star-cat/databutler-provenance
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.physics-star-cat/databutler-provenance.svg)](https://radar.anlyon.com/servers/io.github.physics-star-cat/databutler-provenance)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:43 UTC.

databutler-provenance MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the databutler-provenance MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the databutler-provenance MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the databutler-provenance MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the databutler-provenance MCP server have?

2 tools: 2 write. domain_provenance and package_provenance.

Does the databutler-provenance MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 403 without credentials, and no OAuth protected resource metadata was found.

Does the databutler-provenance MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the databutler-provenance MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.