AI invoice follow-up emails for freelancers. Draft-only, never sends for you.
MCPpedia last refreshed this data
io.github.docracy1/chasa is an MCP server that AI invoice follow-up emails for freelancers. Draft-only, never sends for you. Its tool list has not been published yet over http, requires no API key, and scores 90/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-docracy1-chasa": {
"args": [
"-y",
"npm"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Paste your unpaid invoices. Get the follow-up email already written, in the right tone for how late it is.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / finance
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
The official MCP server implementation for the Perplexity API Platform
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Ruflo - Enterprise AI agent orchestration for Claude Code. Deploy 60+ specialized agents in coordinated swarms with self-learning, fault-tolerant consensus, vector memory, and MCP integration
MCP Security Weekly
Get CVE alerts and security updates for io.github.docracy1/chasa and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Paste your unpaid invoices. Get the follow-up email already written, in the right tone for how late it is.
Chasa never emails your clients for you — it drafts follow-ups you copy into Gmail, Outlook, or Apple Mail. Tone escalates with days overdue (friendly → firm → direct).
| URL | |
|---|---|
| Marketing | https://chasa.io/ |
| App (Tool) | https://chasa.io/app/ |
| Login | https://chasa.io/app/login |
| Connector | https://chasa.io/app/connector |
| Admin | https://chasa.io/app/admin |
| API | https://api.chasa.io |
| MCP | https://api.chasa.io/mcp — read-only tools public; draft_chase_email requires session or API key |
Worker PUBLIC_APP_URL is https://chasa.io (magic links, OAuth callbacks, Stripe return URLs, digest links).
Go-live checklist
chasa.io on Cloudflare Pages project chasa and wait for Active.www → apex. Pages _redirects cannot match hostnames, so use Bulk Redirects: source www.chasa.io → target https://chasa.io, 301, with preserve query string, subpath matching and preserve path suffix. Needs a proxied www DNS record (CNAME → chasa-71s.pages.dev, or A → 192.0.2.1 if apex-only).CLOUDFLARE_API_TOKEN with Zone DNS Edit): ./scripts/go-live-dns.shQBO_CLIENT_ID / QBO_CLIENT_SECRET, XERO_CLIENT_ID / XERO_CLIENT_SECRET) and redirect URIs registered in Intuit / Xero developer consoles:
https://api.chasa.io/api/account/connectors/quickbooks/callbackhttps://api.chasa.io/api/account/connectors/xero/callback./scripts/go-live-verify.sh.The order does not matter: browser-facing links are built from the origin the request came in on (see “App origin resolution” below), so pages.dev and chasa.io both keep working whichever is deployed first.
Magic links, post-login redirects, Stripe return URLs and team invites use the origin the user is actually on, not PUBLIC_APP_URL. The Pages /api proxy forwards it as X-Chasa-App-Origin, and the worker honours it only if it matches lib/appUrl.ts's allowlist (PUBLIC_APP_URL, chasa.io, www.chasa.io, *.pages.dev project/preview hosts, localhost). This keeps preview deploys self-contained and makes the domain cutover zero-downtime.
Requests that arrive without a trusted origin — provider OAuth callbacks hitting api.chasa.io directly, and the digest cron — still fall back to PUBLIC_APP_URL, so those links only work once chasa.io resolves.
| Plan | Price | AI drafts | Team seats | Notes |
|---|---|---|---|---|
| Free | $0 | 5 / month (server-enforced) | 1 (owner only) | No signup required for drafts; sign in to upgrade |
| Solo | $7 / mo | Unlimited | 3 (owner + invites) | Flat workspace fee — not per-seat |
| Pro | $17 / mo | Unlimited | 5 | Most popular; same Solo+ feature parity |
| Enterprise | Stripe checkout | Unlimited | 25 | Self-serve via /app/account?plan=enterprise |
Stripe price IDs live in apps/worker/wrangler.toml as STRIPE_PRICE_SOLO, STRIPE_PRICE_PRO, STRIPE_PRICE_ENTERPRISE (non-secret). Billing portal and webhooks update accounts.plan and is_paid.
| Feature | Free | Solo+ |
|---|---|---|
| AI chase email drafts (tone by days overdue) | 5/mo | Unlimited |
15+ copy-paste email templates (/free-templates/) | ✓ | ✓ |
| CSV invoice upload (Tool) | ✓ | ✓ |
| Manual invoice list + aging board (Tool) | ✓ | ✓ |
| Rewrite softer / firmer / shorter | — | ✓ |
| Thank-you, reply-to-client, 3-step sequence, SMS/WhatsApp drafts | — | ✓ |
| Clients CRM + contact notes | — | ✓ |
| Aging sync (Tool → server) | — | ✓ |
| Reminder calendar (planned chase dates) | — | ✓ |
| Chase timeline + mark sent/paid | — | ✓ |
| Daily chas |