Skip to content

org.lunenburgbudgetproject/archive

by lunenburgbudgetproject.org · remote · no sign-in to list tools · v1.0.0 · published by org.lunenburgbudgetproject

The Lunenburg, Massachusetts town and school budget, every figure traced to its source document.

Changes · 5
CompareRegistry entry

8 tools: 5 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http archive https://lunenburgbudgetproject.org/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Changes things 5Claude Code: ask
  • budget_historyWhat a school budget line was in each year, AT ONE STAGE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What a school budget line was in each year, AT ONE STAGE. The stage argument is required and singular on purpose: `proposed`, `settled` and `actual` are three different documents about the same year, and a growth rate measured from an actual to a budget is partly growth and partly the step between them. That mistake put a special education escalator 1.5 points too high here and was invisible until somebody asked how the number was derived. Note also that a budget line is NET — what the town must raise after grants, fees and state aid — so a line can rise because a grant ended rather than because anything cost more.
  • documentWhere a document came from: the publisher's URL, our copy, and its sha256 so a reader can check they have the same bytes.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Where a document came from: the publisher's URL, our copy, and its sha256 so a reader can check they have the same bytes. Use it to cite anything.
  • queryAny question the other tools do not cover, as one read-only SQL statement over the archive database.No findings

    Why it is in this group

    • The name "query" says "query": a word for reading.
    • The input takes a statement or command to run (input.sql), which can change anything it can reach.
    Description, as the server wrote it
    Any question the other tools do not cover, as one read-only SQL statement over the archive database. SELECT or WITH only; a LIMIT is imposed if you omit one. Call `read_first` before computing anything and `list_datasets` to find table names. A query estimated to read more than 250,000 rows is refused — narrow it with a WHERE, or ask for one table at a time.
  • staffHow many people the town PRINTED on a school staff roster, by year, school and kind of job.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    How many people the town PRINTED on a school staff roster, by year, school and kind of job. Uses our classification of the printed title, never the title itself, because the town has called the same job Tutor, Aide, Paraprofessional, Para, (para) and Sped Para across fifteen years. THIS IS A COUNT OF NAMES, NOT A STAFFING LEVEL: a roster carries no FTE, so a 0.4 music teacher and a full-timer are one row each, and it names no funding source, which is the question that usually matters. Grade appears only where the page happened to print it.
  • worked_examples107 questions this archive can answer, each with the SQL that answers it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    107 questions this archive can answer, each with the SQL that answers it. Every one is executed against the database on every build, so none of them is a claim. Start from the nearest one and edit it rather than writing a query from scratch.
Only reads 3Claude Code: allow
  • list_datasetsEvery dataset in the archive, with THE YEARS EACH COVERS, its row count and its size.No findings

    Why it is in this group

    • The name "list_datasets" says "list": a word for reading.
    Description, as the server wrote it
    Every dataset in the archive, with THE YEARS EACH COVERS, its row count and its size. Call this before answering from prose: it is how you find out whether the archive holds data for the year and subject you are being asked about. 49 datasets covering the town and school budgets, the town ledger, staff rosters, out-of-district placements, elections, and fifteen years of annual town reports.
  • read_firstThe grain of every table and the specific ways to get a confident wrong answer out of this data.No findings

    Why it is in this group

    • The name "read_first" says "read": a word for reading.
    Description, as the server wrote it
    The grain of every table and the specific ways to get a confident wrong answer out of this data. Read this before computing anything. It states, among others, that a budget and an actual must never be combined in one calculation; that a budget line is NET of grants and fees and is not what a thing costs; and that no budget line is mapped to a ledger account, so budget-to-actual at line level cannot be answered from this data at all.
  • search_meetingsWhich of the 1,422 published town meeting documents contain a word — every board, 2025 onward.No findings

    Why it is in this group

    • The name "search_meetings" says "search": a word for reading.
    Description, as the server wrote it
    Which of the 1,422 published town meeting documents contain a word — every board, 2025 onward. Returns the board, the date and a citable URL for each. AN EMPTY RESULT MEANS THE WORD IS NOT IN THE INDEXED DOCUMENTS, which is not the same as nobody having said it: the archive starts in January 2025. It matches words exactly, so plurals are separate terms — search "jersey" and "jerseys" both.

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.

Install

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

claude mcp add --transport http archive https://lunenburgbudgetproject.org/mcp

Run in a terminal.

Claude Code permissions

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__archive__list_datasets",
      "mcp__archive__read_first",
      "mcp__archive__search_meetings"
    ],
    "ask": [
      "mcp__archive__worked_examples",
      "mcp__archive__budget_history",
      "mcp__archive__staff",
      "mcp__archive__document",
      "mcp__archive__query"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as archive. Review it before you use it.