Footnote MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Footnote row-bound business-data claim provenance: Do claim references and tamper-evident exports preserve the exact rows and query context that produced each number?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Attach claim-level provenance to AI answers backed by business-database rows.

What we know

Every number in an AI answer traces back to the rows that produced it. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@brick-byte/footnote 0.1.1 published 2026-08-17T11:20:00.620Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Query data according to configured SQLite/Postgres connection; provenance-store local writes Writes: Create local provenance evidence records (not a source-business-data mutation claim).
Local actor/database environment variables; production database access control supplied by deployment
Sensitive access: Business row-level data, Database credentials, Provenance actor

Potential high-impact side effects: Create local provenance evidence records (not a source-business-data mutation claim).

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do claim references and tamper-evident exports preserve the exact rows and query context that produced each number?

The bounded review of the publisher's documented Footnote row-bound business-data claim provenance and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Create local provenance evidence records (not a source-business-data mutation claim).
Query data according to configured SQLite/Postgres connection; provenance-store local writes
Local actor/database environment variables; production database access control supplied by deployment
Claim traces and provenance hashes persist in local SQLite or optional Postgres.
Reviewed write actions: Create local provenance evidence records (not a source-business-data mutation claim)
Sensitive access: Business row-level data, Database credentials, Provenance actor
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
MCP claim-to-evidence rendering still depends on the host
Actual database permissions and row-level access must be configured
Audit retention and integration deep links require deployment implementation
This is not a generic read-only DB connector: it persists provenance and may access sensitive ERP rows.

Original activity observations

@brick-byte/footnote 0.1.1 published 2026-08-17T11:20:00.620Z

Technical identity

npm/@brick-byte/footnote

Exact implementation source: https://www.npmjs.com/package/@brick-byte/footnote ↗
Reviewed resource type: MCP Server
Repository identity: brick-byte/footnote
Package identity: npm:@brick-byte/footnote

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@brick-byte/footnote
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
brick-byte/footnote
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Evidence/provenance tool with example MCP configurations in publisher README; do not claim it automatically enforces claim-level citations in arbitrary clients.
Host must explicitly preserve structuredContent and cited evidence.
Earlier review note retained for provenance; the V3 verified fields take precedence: Targeted 2026-10-13 re-research: Publisher supplies mcpServers stdio example; distinguish local demo HTTP server from MCP registration.
Publisher supplies mcpServers stdio example; distinguish local demo HTTP server from MCP registration.
Prior reviewed safety note: Do not place orders, spend tokens, modify infrastructure or upload confidential files as a test.
Prior reviewed safety note: Do not invent a one-line reversal command.
Earlier review note retained for provenance; the V3 verified fields take precedence: Second-pass 2026-10-14 could not retrieve full current publisher npm README; preserve baseline, do not promote source-specific claims or run commands until documentation is rechecked.
Direct npm README reviewed 2026-10-14; client registration still required.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.

Install / connect
Publisher instructions
Evidence/provenance tool with example MCP configurations in publisher README; do not claim it automatically enforces claim-level citations in arbitrary clients.
publisher documented mcp stdio launch · Publisher instructions
npx -y @brick-byte/footnote
Configure / authenticate
MCP100 setup guide
Register `npx -y @brick-byte/footnote` in a client using the official README MCP JSON; numerical output is structured but claims are not automatically linked to citations.
Check connection
Suggested check
Inspect available Footnote tools then use an official read-only query example before relying on generated citations.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `brick-byte-footnote`, run `claude mcp remove brick-byte-footnote`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove brick-byte-footnote

Official Documentation & Sources

What it does

Every number in an AI answer traces back to the rows that produced it. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Data & Databases
Resource type: MCP Server
Best fit: Attach claim-level provenance to AI answers backed by business-database rows.

Representative uses

Query grounded numeric business claims
Inspect claim-to-row provenance
Run local demo with SQLite or opt-in Postgres

Limitations

MCP claim-to-evidence rendering still depends on the host
Actual database permissions and row-level access must be configured
Audit retention and integration deep links require deployment implementation
This is not a generic read-only DB connector: it persists provenance and may access sensitive ERP rows.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local actor/database environment variables; production database access control supplied by deployment
Permissions: Query data according to configured SQLite/Postgres connection; provenance-store local writes
Data handling: Claim traces and provenance hashes persist in local SQLite or optional Postgres.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Create local provenance evidence records (not a source-business-data mutation claim).

Access scope and cautions

Write actions: Create local provenance evidence records (not a source-business-data mutation claim)
Sensitive access: Business row-level data Database credentials Provenance actor
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Query grounded numeric business claims; Inspect claim-to-row provenance; Run local demo with SQLite or opt-in Postgres.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @brick-byte/footnote. Recorded transport: stdio. Recorded environment-variable notes: PROVENANCE_DB; PROVENANCE_ACTOR; DATABASE_URL (optional Postgres). No configuration values are supplied here. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local actor/database environment variables; production database access control supplied by deployment

Can it modify data or perform write operations?

Documented write actions include: Create local provenance evidence records (not a source-business-data mutation claim). Recorded permission boundary: Query data according to configured SQLite/Postgres connection; provenance-store local writes

What data-handling boundary should I consider?

Claim traces and provenance hashes persist in local SQLite or optional Postgres. Recorded sensitive-access context: Business row-level data; Database credentials; Provenance actor.

What limitations and risks should I check before use?

Potential high-impact side effects: Create local provenance evidence records (not a source-business-data mutation claim). MCP claim-to-evidence rendering still depends on the host. Actual database permissions and row-level access must be configured. Audit retention and integration deep links require deployment implementation. This is not a generic read-only DB connector: it persists provenance and may access sensitive ERP rows. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.