# io.github.docracy1/chasa (remote · api.chasa.io)

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

- Trust score: 18/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `api.chasa.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/docracy1-chasa/api.md), [page](https://verifymcp.io/servers/docracy1-chasa/api)

## Channel facts

- Endpoint: `https://api.chasa.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the io.github.docracy1/chasa MCP server?

io.github.docracy1/chasa is a hosted endpoint at https://api.chasa.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http docracy1-chasa 'https://api.chasa.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "docracy1-chasa": {
      "url": "https://api.chasa.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "docracy1-chasa": {
      "type": "http",
      "url": "https://api.chasa.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.docracy1-chasa]
url = "https://api.chasa.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "docracy1-chasa": {
      "type": "remote",
      "url": "https://api.chasa.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add docracy1-chasa --url 'https://api.chasa.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  docracy1-chasa:
    url: "https://api.chasa.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "docracy1-chasa": {
      "Transport": "http",
      "Url": "https://api.chasa.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add docracy1-chasa -t streamable-http -u 'https://api.chasa.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "docracy1-chasa": {
      "type": "http",
      "url": "https://api.chasa.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-30 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] HTTPS: fail → unverified
- [security regression] Stability: 0.43 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-29 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-26 (score 62)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-23 (score 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: chasa → docstoc
- [security] Tool “list_templates” rewrote its description, which is the text the model reads
- [security] Tool “recommend_template” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good

### 2026-08-17 (score 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-16 (score 0)

First indexed and scored.

## MCP tools (4)

### `draft_chase_email` (~85 tokens)

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.

Input parameters:

- `client_name` (string, required): Client or company name
- `days_overdue` (number, required): How many days past the due date (0 = due today)
- `invoice_amount` (number, required): Invoice amount in dollars

### `get_chase_tip` (~40 tokens)

Get a short chase-tone tip for how late an invoice is.

Input parameters:

- `days_overdue` (number, required): Days past due (0 = due today)

### `recommend_template` (~47 tokens)

Recommend a free docstoc payment-reminder template for a given days-overdue stage, with a URL.

Input parameters:

- `days_overdue` (number, required): Days past due (0 = due today)

### `list_templates` (~21 tokens)

List docstoc free invoice follow-up email templates with URLs.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/docracy1-chasa/api#diagnostics

## Score history

- 2026-09-24: 18
- 2026-09-23: 18
- 2026-09-22: 18
- 2026-09-21: 18
- 2026-09-20: 18
- 2026-09-19: 18
- 2026-09-18: 18
- 2026-09-17: 18
- 2026-09-16: 18
- 2026-09-15: 18
- 2026-09-14: 18
- 2026-09-13: 18
- 2026-09-12: 18
- 2026-09-11: 18
- 2026-09-10: 18
- 2026-09-09: 18
- 2026-09-08: 18
- 2026-09-07: 18
- 2026-09-06: 18
- 2026-09-05: 18
- 2026-09-04: 18
- 2026-09-03: 18
- 2026-09-02: 18
- 2026-09-01: 18
- 2026-08-31: 18
- 2026-08-30: 18
- 2026-08-29: 63
- 2026-08-28: 62
- 2026-08-27: 62
- 2026-08-26: 62

## Common questions

### What is the io.github.docracy1/chasa MCP server?

io.github.docracy1/chasa is an MCP server listed in the public MCP registry as io.github.docracy1/chasa. AI invoice follow-up emails for freelancers. Draft-only, never sends for you. This page covers its hosted endpoint (https://api.chasa.io/mcp).

### Is the io.github.docracy1/chasa MCP server safe to use?

io.github.docracy1/chasa scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.docracy1/chasa MCP server expose?

io.github.docracy1/chasa exposes 4 tools: draft_chase_email, get_chase_tip, recommend_template, list_templates. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.

### Does the io.github.docracy1/chasa MCP server require authentication?

No. We connected to io.github.docracy1/chasa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.docracy1/chasa MCP server still maintained?

io.github.docracy1/chasa is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.chasa.io/mcp
- Repository: https://github.com/docracy1/chasa
- Changelog RSS feed: https://verifymcp.io/servers/docracy1-chasa/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/docracy1-chasa/api.json
- HTML version of this page: https://verifymcp.io/servers/docracy1-chasa/api