Skip to content

DIY Accounting Submit MCP server

io.github.diy-accounting-uk/diya-submitdiy-accounting-ukstreamable-httpv0.1.4Scanned

Opens a book, derives VAT return figures and reads stored VAT receipts. Files no return.

6 tools: 3 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DIY Accounting Submit MCP server can do

The DIY Accounting Submit MCP server is published by the GitHub account diy-accounting-uk. It has 6 tools. It can create or change data (3 tools: open_book, derive_vat_return and prepare_vat_return), but cannot delete data. 3 tools only read.

2 tools read private data (list_books and get_vat_receipt).

The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.1.4.

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.

6 tools

Changes things 3Claude Code: ask
  • derive_vat_returnThe nine VAT boxes for one obligation period from the session's loaded book, read from the engine's own VAT interface: the quarter ending on periodEnd (a month end the book carries…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The nine VAT boxes for one obligation period from the session's loaded book, read from the engine's own VAT interface: the quarter ending on periodEnd (a month end the book carries), with HMRC's field names and rounding, the three months' figures, and every sales and purchases journal line that fed boxes 1, 4, 6 and 7. Refuses a book that is not VAT registered, a period the book does not carry, and a period whose lines do not reconcile with the interface.

    Annotations the server declares

    • title: Derive a VAT return
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • open_bookOpen a book saved in the DIYA cloud by bookId (a practice client's own book with clientId), signed in as the caller.1 finding

    Why it is in this group

    • The name "open_book" says "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "open_book" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "open_book" says "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Open a book saved in the DIYA cloud by bookId (a practice client's own book with clientId), signed in as the caller. Answers the product, the entity, the period covered, the line count and the book checks summary. Replaces the session's loaded book.

    Annotations the server declares

    • title: Open a book
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • prepare_vat_returnDerives the VAT return for the quarter ending on periodEnd from the session's loaded book, exactly as derive_vat_return does, and answers a link to the VAT form on the Submit site …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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Derives the VAT return for the quarter ending on periodEnd from the session's loaded book, exactly as derive_vat_return does, and answers a link to the VAT form on the Submit site with the seven figures filled in (the form works out boxes 3 and 5 itself). This tool never files anything and reaches no outside service. The person opens the link, checks the figures on the page, ticks the declaration and files there; the figures filed are the figures the page shows.

    Annotations the server declares

    • title: Prepare a VAT return to file in the browser
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_vat_receiptA stored VAT return receipt by its file name, over the deployed API: what HMRC answered when it accepted the return (the processing date, the form bundle number, the payment indica…Reads private dataNo findings

    Why it is in this group

    • The name "get_vat_receipt" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "file": it reads files.
    Description, as the server wrote it
    A stored VAT return receipt by its file name, over the deployed API: what HMRC answered when it accepted the return (the processing date, the form bundle number, the payment indicator and the charge reference). clientId, when given, narrows the fetch to one of the practice's clients but does not change which receipt is read.

    Annotations the server declares

    • title: Get a VAT receipt
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_booksList the books saved in the DIYA cloud, most recently updated first, signed in as the session's credentials.Reads private data1 finding

    Why it is in this group

    • The name "list_books" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "credential": it reads secrets.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...dated first, signed in as the session's credentials. Each row carries the bookId open_book..."

      What this check looks for
    Description, as the server wrote it
    List the books saved in the DIYA cloud, most recently updated first, signed in as the session's credentials. Each row carries the bookId open_book takes, the book's title, its product and the period it covers. With clientId, lists that practice client's books instead of the practice's own.

    Annotations the server declares

    • title: List saved books
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_vat_receiptsThe VAT return receipts Submit has stored for the signed-in account, newest first: each row carries the name get_vat_receipt takes, HMRC's form bundle number and the day the return…No findings

    Why it is in this group

    • The name "list_vat_receipts" says "list": a word for reading.
    Description, as the server wrote it
    The VAT return receipts Submit has stored for the signed-in account, newest first: each row carries the name get_vat_receipt takes, HMRC's form bundle number and the day the return was filed. clientId narrows the list to one of the practice's clients.

    Annotations the server declares

    • title: List VAT receipts
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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 untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://submit.diyaccounting.co.uk/.well-known/oauth-protected-resource/mcp
Authorization servers
https://submit.diyaccounting.co.uk
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://submit.diyaccounting.co.uk/mcp: tools/list returned 6 tools to an anonymous client, including open_book (write), derive_vat_return (write), prepare_vat_return (write)

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://submit.diyaccounting.co.uk/.well-known/oauth-protected-resource/mcp to none

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "open_book" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "open_book" says "open": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...dated first, signed in as the session's credentials. Each row carries the bookId open_book..."

    What this check looks for

History

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

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 3 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed
    • resource_metadata in WWW-Authenticate: https://submit.diyaccounting.co.uk/.well-known/oauth-protected-resource/mcp to none

Install

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

claude mcp add --transport http diya-submit https://submit.diyaccounting.co.uk/mcp
claude mcp add --transport http diya-submit https://submit.diyaccounting.co.uk/mcp

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": [
      "mcp__diya-submit__list_books",
      "mcp__diya-submit__get_vat_receipt",
      "mcp__diya-submit__list_vat_receipts"
    ],
    "ask": [
      "mcp__diya-submit__open_book",
      "mcp__diya-submit__derive_vat_return",
      "mcp__diya-submit__prepare_vat_return"
    ],
    "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 diya-submit. Review it before you use it.

Capability tags behind 2 rules
  • mcp__diya-submit__list_books private-data
  • mcp__diya-submit__get_vat_receipt private-data

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.diy-accounting-uk/diya-submit/verify?hash=caaba33eb95da1d90451d81e0fa8ab429cabbc892ce63c4a3004626d4c76b4bf" | jq -e '.changed == false'

Pinned hash caaba33eb95d, from Nov 18, 2026, 18:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.diy-accounting-uk/diya-submit/changes.xml

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

Badge

Anlyon Radar badge for io.github.diy-accounting-uk/diya-submit
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.diy-accounting-uk/diya-submit.svg)](https://radar.anlyon.com/servers/io.github.diy-accounting-uk/diya-submit)

Source: MCP Registry · repository. Synced Nov 18, 2026, 18:17 UTC.

DIY Accounting Submit MCP server: questions and answers

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

Is the DIY Accounting Submit MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 2 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 DIY Accounting Submit MCP server delete data?

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

Can the DIY Accounting Submit 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 DIY Accounting Submit MCP server have?

6 tools: 3 write, 3 read. open_book, derive_vat_return, prepare_vat_return, list_books, get_vat_receipt and list_vat_receipts.

Does the DIY Accounting Submit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DIY Accounting Submit MCP server send data to outside services?

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

Has the DIY Accounting Submit MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.