footnote
com.brick-byte/footnote
Every number in an AI answer traces back to the rows that produced it.
Description as published in the official MCP registry.
What we measured
| Endpoint | None listed (runs locally) | registry |
|---|---|---|
| GitHub stars | 0 | github.com/brick-byte/footnote |
| Last push | 2026-08-14 | GitHub API |
| Licence | MIT | GitHub API |
| Registry version | 0.1.1 · active · updated 2026-08-17 | registry |
| Package | npm: @brick-byte/footnote | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.
Connect
npx -y @brick-byte/footnoteCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- footnote-mcp Source-grounded web research: search, extraction, verification, and browser automation.
Badge for your README
Shows the result of our latest check and links back to this page.
[](https://openforallofus.com/tools/com.brick-byte/footnote)Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name com.brick-byte/footnote.