MCP.Market

Chasa MCP server

online · 100% uptime
by docracy1·io.github.docracy1/chasa·v1.0.0
No reviews yet

AI invoice follow-up emails for freelancers. Draft-only, never sends for you.

A85/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Chasa yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Chasa tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 920ms; handshake note: [ { "code": "invalid_union", "errors": [ [ { "code": "invalid_value", "value20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Chasa compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 80% of 1,761 Finance servers
Uptime
100%
of our recent checks; the typical remote Finance server answers 100%
Response time
196 ms
faster than 67% of 1,133 Finance servers

Install Chasa in Claude Code, Cursor or VS Code

claude mcp add --transport http chasa https://api.chasa.io/mcp
Add to Cursor

What the publisher says

From the Chasa repository's README, as published. We do not edit it. Read it on GitHub

docstoc

Paste your unpaid invoices. Get the follow-up email already written, in the right tone for how late it is.

docstoc 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).

Live URLs

Worker PUBLICAPPURL is https://docstoc.io (magic links, OAuth callbacks, Stripe return URLs, digest links).

Legacy chasa.io / api.chasa.io 301 to docstoc (Pages _middleware.ts + worker redirect). See scripts/oauth-redirect-uris.md for provider console URIs.

Go-live checklist

  1. Attach docstoc.io on Cloudflare Pages project chasa and wait for Active.
  2. www.docstoc.io → apex: handled by apps/web/functions/_middleware.ts (redeploy web).
  3. chasa.io / www.chasa.io → docstoc.io: same middleware.
  4. api.chasa.io → api.docstoc.io: worker middleware in apps/worker/src/lib/legacyHostRedirect.ts.
  5. Register OAuth redirect URIs on api.docstoc.io — see scripts/oauth-redirect-uris.md.
  6. Optional DMARC: ./scripts/dmarc-remove-rua.sh (removes rua= from _dmarc.docstoc.io).
  7. Run ./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.

App origin resolution

Magic links, post-login redirects, Stripe return URLs and team invites use the origin the user is actually on, not PUBLICAPPURL. The Pages /api proxy forwards it as X-Docstoc-App-Origin, and the worker honours it only if it matches lib/appUrl.ts's allowlist (PUBLICAPPURL, docstoc.io, www.docstoc.io, legacy chasa.io hosts, *.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.docstoc.io directly, and the digest cron — still fall back to PUBLICAPPURL.

Product specs

Plans & pricing

Stripe price IDs live in apps/worker/wrangler.toml as STRIPEPRICESOLO (maps to Pro), STRIPEPRICEPRO / STRIPEPRICEENTERPRISE (map to Business; non-secret). Billing portal and webhooks update accounts.plan and is_paid.

Feature matrix (by plan)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Chasa: common questions

Is Chasa MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Chasa safety report
How do I install Chasa?
It runs remotely at api.chasa.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Chasa need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Chasa maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v1.0.0.
Is Chasa up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Chasa?
Servers from other publishers that do the same job: three.ws Tutor MCP server, E Arveldaja MCP server and Quickbooks MCP server.
How does Chasa compare with other Finance MCP servers?
safety score 85/100 (higher than 80% of 1,761 Finance servers); uptime 100% (of our recent checks; the typical remote Finance server answers 100%); response time 196 ms (faster than 67% of 1,133 Finance servers). Full comparison.

Alternatives to Chasa

Same job from other publishers: the closest match first, then the best rated.

  • three.ws Tutor
    Read a Pay-As-You-Learn tutoring session's itemized tab and close it for an attested invoice.
    A
  • E Arveldaja
    Estonian e-arveldaja (RIK e-Financials) accounting — invoices, bank import, reports.
    B
  • Quickbooks
    MCP server for QuickBooks Online (Intuit) — customers, invoices, payments, items, accounts, P&L
    More from codespar →
    B
  • Norman Finance — AI Bookkeeping, Accounting & Taxes
    Bookkeeping, invoices and tax workflows for European businesses, including Polish KPiR and JPK.
    A
  • Bexio
    Swiss accounting integration for Bexio. 315 tools: invoices, contacts, projects, account balances
    A

More from docracy1 →