io.github.diy-accounting-uk/diya-submit
DIY Accounting Submit
Is the DIY Accounting Submit MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Opens a book, derives VAT return figures and reads stored VAT receipts. Files no return.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:@diy-accounting-uk/diya-submit, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"Unauthorized"},"id":null}- Endpoint
- https://submit.diyaccounting.co.uk/mcp (streamable-http)
- Host
- submit.diyaccounting.co.uk
- Of a 1M window
- 2.6 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://submit.diyaccounting.co.uk/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server submit.diyaccounting.co.uk, PKCE S256, grants authorization_code, refresh_token.
Scopes openid email profile.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk
- Website
- https://submit.diyaccounting.co.uk
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Servers that mention submit.
- ARPI MCP ai.arpi/arpi-mcp · no DNS
- Contractors Near Me ai.contractorsnearme/contractors-near-me · needs auth
- FlipDomain Domain Sales ai.flipdomain/domain-sales · not found
- GVRN Incorporation ai.gvrn/incorporation · alive
- ai.projectlaunch/mcp · needs auth
- ai.ssid/ssid-mcp · alive
- ONCE app.once/mcp · needs auth
- Robisie — agent-readable execution board app.robisie/board · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.