mcpbeat Sign in

Chasa MCP Server

not responding

Chasa is listed as active in the registry but did not answer our last check. It exposes 4 tools. Last commit 2 Nov 2026.

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

Uptime history 79 days of history · worst day 0%
79 days agonow
0.0%
Uptime 24h
0 of 91 checks
4
Tools
read from the server
214 ms
Response time
average over 24h
0
Stars
last commit 2 Nov 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 August 2026. No other catalogue keeps this.

22 Aug 2 tool descriptions were rewritten list_templates, recommend_template

What the code does

We read the source, 3 h ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add chasa --transport http https://api.chasa.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.chasa.io/mcp
~/.codex/config.toml
[mcp_servers.chasa]
url = "https://api.chasa.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "chasa": {
      "url": "https://api.chasa.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "chasa": {
      "type": "http",
      "url": "https://api.chasa.io/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

chase
get_chase_tip
Get a short chase-tone tip for how late an invoice is.
draft
draft_chase_email
Draft a payment follow-up email for an overdue invoice. Returns subject + body. Does not send email — the user copies it to their own inbox.
recommend
recommend_template
Recommend a free docstoc payment-reminder template for a given days-overdue stage, with a URL.
templates
list_templates
List docstoc free invoice follow-up email templates with URLs.

Endpoints

URLTransportStateLatencyChecked
https://api.chasa.io/mcp streamable-http answering 214 ms 7 min ago

Alternatives to Chasa

same job, measured the same way
M
MailMCP
by mcpproducts

Read, search and draft email over IMAP from any AI agent. Never sends.

116 installs/wk local only
FoxyInvoice
by foxyinvoice

Invoicing tools for AI assistants: clients, draft invoices with computed tax, and email sending.

answering
Outlook Email
by mintmcp

A MCP server for Outlook email that lets you search, read, and draft emails and replies.

answering
Gmail
by mintmcp

A MCP server for Gmail that lets you search, read, and draft emails and replies.

answering
D
DropAgent
by getdropagent

Ringless voicemail and SMS follow-up for AI agents, with consent checks and confirmed bulk sends.

answering
Botmail
by botmail

Your agent's own email address: read, search, send, reply, draft and wait for mail.

answering
Pushizo
by pushizo

Push, email, SMS, in-app and journeys. 54 tools: reads and drafts; only test sends.

153 installs/wk answering
Anjal
by anjal

Email inboxes and calendars for AI agents: send, receive, search, draft and schedule.

answering

Chasa — questions

Answers built from our own checks of this server.

What can Chasa do?
It exposes 4 tools, read directly from the server on our last check. Among them: draft_chase_email, get_chase_tip, list_templates, recommend_template. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Chasa working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 214 ms. The bar chart above shows every period we have measured.
The registry lists Chasa as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Chasa?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Chasa need an API key?
No. Chasa completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
Is Chasa open source?
We cannot say either way: written in HTML and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.