Skip to content
Back to search

saasumcp

Read-only MCP server over stdio for lookups in Saasu accounting files, held to a daily request budget per file.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 21 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/hampel/saasumcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/hampel/saasumcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hampel--saasumcp/badge.svg)](/listings/hampel--saasumcp)

HTML

<a href="/listings/hampel--saasumcp"><img src="/api/listings/hampel--saasumcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Download `saasumcp-<version>` and `SHA256SUMS` from the release, verify, and install the binary:

sha256sum --ignore-missing -c SHA256SUMS
install -m 0755 saasumcp-<version> /usr/local/bin/saasumcp

From a checkout, `composer install` and run `php saasumcp` in place of `saasumcp`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 129 lines
  1. # saasumcp — Saasu lookups over MCP
  2. A read-only [MCP](https://modelcontextprotocol.io/) server, over stdio, that lets an agent look up
  3. invoices, payments, contacts, accounts, tax codes, items and bank balances in one or more
  4. [Saasu](https://www.saasu.com/) files. It is for an operator's agent that needs to answer "what
  5. is this purchase, and how was it paid?" without holding a Saasu login itself.
  6. **Nothing it does can change a file, and every request it sends is rationed.** Both are the
  7. point of it; see *Safety*.
  8. ## Requirements
  9. PHP 8.3 or later. A Saasu login for each file, made for this server alone.
  10. ## Installation
  11. Download `saasumcp-<version>` and `SHA256SUMS` from the release, verify, and install the binary:
  12. ```bash
  13. sha256sum --ignore-missing -c SHA256SUMS
  14. install -m 0755 saasumcp-<version> /usr/local/bin/saasumcp
  15. ```
  16. From a checkout, `composer install` and run `php saasumcp` in place of `saasumcp`.
  17. ## Configuration
  18. Three things: an environment file, a file inventory, and a state directory.
  19. **The environment file** says where the state lives, and holds no credential. `.env.example`
  20. is the template and says where the file is looked for. A variable already set, exported or
  21. passed by the MCP client, wins over the same key in the file.
  22. ```dotenv
  23. SAASUMCP_STATE_PATH=/var/lib/saasumcp
  24. ```
  25. **The file inventory** names the files and holds the login for each. `files.toml.example` is the
  26. template; by default it is `files.toml` in the state directory. It holds passwords, so
  27. `app:validate` fails it at anything wider than 0600, or root-owned and 0640 for a group.
  28. ```toml
  29. [acme]
  30. name = "Acme Example Pty Ltd"
  31. file_id = 12345
  32. username = "mcp@example.com"
  33. password = "..."
  34. # daily_budget = 500
  35. ```
  36. The table name is the key every tool takes.
  37. **The state directory** is created 0700 on first use. It holds cached OAuth tokens, the shared
  38. throttle, each file's request count, and the lists kept for a day. Set it absolutely: a compiled
  39. binary otherwise uses the working directory, which the MCP client chooses.
  40. ```bash
  41. saasumcp app:config # what is configured, and the .env actually read
  42. saasumcp app:validate # checks it, and asks Saasu for every permission the tools need
  43. ```
  44. `app:validate` sends about a dozen requests to each file, counted against its budget.
  45. `--offline` skips them; `--strict` exits 2 on a warning.
  46. ## Logins
  47. **Give the server its own login in each file, without two-factor authentication**, so its
  48. spending is its own and its token cache is not shared with another integration.
  49. **Give it read access and no write access.** That is enough for every tool, measured against
  50. Saasu: the reads it needs are **sales, purchases, contacts, accounts and inventory items**. A
  51. login without the Purchase permission is refused every invoice list, sales included, and an
  52. untyped payment list. `app:validate` tries each.
  53. ## Registering the server
  54. With Claude Code:
  55. ```bash
  56. claude mcp add saasu -- saasumcp mcp:start saasu
  57. ```
  58. Any MCP client that starts a stdio server works the same way: the command is
  59. `saasumcp mcp:start saasu`. If the environment file is not in one of the places looked for, set
  60. `SAASUMCP_ENV` in the environment the client starts it with.
  61. ## Tools
  62. | tool | answers | costs |
  63. |---|---|---|
  64. | `list-files` | the configured files and their budgets | nothing |
  65. | `file-access` | whether the login reaches a file, and what the file is | 1 |
  66. | `get-invoice`, `get-payment`, `get-contact`, `get-account`, `get-item` | one record by its Saasu id | 1 |
  67. | `list-invoices` | sales or purchases by date, number or contact | 1 a page, 5 at most |
  68. | `list-payments` | payments by date, or those applied to one invoice | 1 a page, 5 at most |
  69. | `find-contacts` | contacts by email, reference, name or date changed | 1 a page, 5 at most |
  70. | `find-items` | inventory items by a search | 1 a page, 5 at most |
  71. | `list-accounts`, `list-tax-codes` | the whole chart of accounts, every tax code | kept a day; usually nothing |
  72. | `bank-balances` | each bank account's balance | 1 |
  73. A login costs one more when no token is cached. Records go out as Saasu sends them, less their
  74. hypermedia links. Every answer carries `budget`: what the call sent and what is left.
  75. ## Safety
  76. **Read-only twice over.** The server has no tool that writes, and the login it is given has no
  77. write access in Saasu, which the tools do not need. Either alone keeps a file unchanged.
  78. **Saasu blocks a file's whole API for 24 hours once its daily quota is exceeded** — every
  79. integration on it, not only this one. So:
  80. - **Each file has a budget over any 24 hours**, 500 requests unless set otherwise, kept in the
  81. state directory and shared by every server process. A call sets aside the most it might send
  82. before it starts; one that does not fit is refused without asking Saasu.
  83. - **Lists need a date range or a filter**, fetch one page of 100 unless asked for more, and never
  84. more than five. Saasu does not say how many records a list holds, so an answer says only
  85. whether more exist.
  86. - **One request a second per file**, across every process, through a lock in the state directory.
  87. ## Development
  88. ```bash
  89. composer check # phpstan, then pest
  90. composer build # the release phar, into builds/
  91. ```
  92. ## Licence
  93. MIT. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.