com.brick-byte/footnote
NPM · @BRICK-BYTE/FOOTNOTE
Every number in an AI answer traces back to the rows that produced it.
Available components
Last scanned (21 hours ago)
Scores higher than 33% of npm servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 107 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 440 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 0
- Package version: 0.1.1 → 0.1.2 functional
- 26 Oct 26 0
- Package version: 0.1.1 → 0.1.2 functional
- 25 Oct 26 0
- Package version: 0.1.1 → 0.1.2 functional
- 24 Oct 26 +10
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 +17
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.1.1 → 0.1.2 functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@brick-byte/footnote@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getCustomerSummary Customer master data and balance ~49
Returns master data for one customer plus their total open balance and open ticket count. Use this for "tell me about customer X" questions.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | string | yes | Customer name or numeric ID. |
No output schema declared.
No examples provided.
getOpenTickets Open support tickets for a customer ~50
Returns unresolved support tickets for one customer. Use this when assessing account risk or when a question asks why a customer might be unhappy or withholding payment.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | string | yes | Customer name or numeric ID. |
No output schema declared.
No examples provided.
getOverdueInvoices Overdue invoices for a customer ~91
Returns every invoice for one customer that is past its due date and not fully paid, as of a given date, with the outstanding total. Aggregation is done in SQL. Use this for any question about what a customer owes.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | yes | Evaluate overdue status as of this date. |
| customer | string | yes | Customer name or numeric ID. Must resolve to a real customer. |
No output schema declared.
No examples provided.
getPaymentHistory Payments received from a customer ~66
Returns payments received from one customer since a given date, with the total. Use this for questions about whether or when a customer has paid.
| Name | Type | Req | Description |
|---|---|---|---|
| customer | string | yes | Customer name or numeric ID. |
| sinceDate | string | yes | Only include payments received on or after this date. |
No output schema declared.
No examples provided.
getReceivablesAging Receivables aging across all customers ~61
Returns the aging profile of all outstanding receivables as of a date, bucketed by days overdue. Use this for portfolio-level questions rather than single-customer ones.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | yes | Evaluate aging as of this date. |
No output schema declared.
No examples provided.
verifyProvenanceChain Verify the provenance chain ~44
Re-derives every hash in the provenance log and reports whether the trail has been modified since it was written. Returns the first inconsistency found, if any.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.brick-byte/footnote MCP server?
com.brick-byte/footnote runs locally as an npm package, launched with npx -y @brick-byte/footnote. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @brick-byte/footnote
claude mcp add com-brick-byte-footnote -- npx -y @brick-byte/footnote
What is the com.brick-byte/footnote MCP server?
com.brick-byte/footnote is an MCP server listed in the public MCP registry as com.brick-byte/footnote. Every number in an AI answer traces back to the rows that produced it. This page covers its npm package (@brick-byte/footnote).
Is the com.brick-byte/footnote MCP server safe to use?
com.brick-byte/footnote scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.brick-byte/footnote MCP server expose?
com.brick-byte/footnote exposes 6 tools: getOverdueInvoices, getCustomerSummary, getPaymentHistory, getOpenTickets, getReceivablesAging, verifyProvenanceChain. Their descriptions and schemas cost roughly 361 tokens of context every time the server is loaded.
Is the com.brick-byte/footnote MCP server still maintained?
com.brick-byte/footnote is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.brick-byte/footnote MCP server under?
com.brick-byte/footnote declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.