io.github.docracy1/chasa
REMOTE · API.CHASA.IO · SCANNED SEP 24
AI invoice follow-up emails for freelancers. Draft-only, never sends for you.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
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.
remote · api.chasa.io
claude mcp add --transport http docracy1-chasa 'https://api.chasa.io/mcp'
{
"mcpServers": {
"docracy1-chasa": {
"url": "https://api.chasa.io/mcp"
}
}
} {
"servers": {
"docracy1-chasa": {
"type": "http",
"url": "https://api.chasa.io/mcp"
}
}
} [mcp_servers.docracy1-chasa] url = "https://api.chasa.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"docracy1-chasa": {
"type": "remote",
"url": "https://api.chasa.io/mcp",
"enabled": true
}
}
} openclaw mcp add docracy1-chasa --url 'https://api.chasa.io/mcp' --transport streamable-http
mcp_servers:
docracy1-chasa:
url: "https://api.chasa.io/mcp" {
"McpServers": {
"docracy1-chasa": {
"Transport": "http",
"Url": "https://api.chasa.io/mcp"
}
}
} assistant mcp add docracy1-chasa -t streamable-http -u 'https://api.chasa.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Aug 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: fail → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 29 Aug 26 +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.
- 26 Aug 26 62
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Aug 26 0
- 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 security
- Schema quality: excellent → good functional
- 17 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://api.chasa.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chasa.io | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d2b5f0d4d56fed980e03bf3ff2930ce2 |
| SANs: chasa.io, api.chasa.io, *.api.chasa.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.chasa.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| chasa.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 301 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.chasa.io/mcp | Redirected | 301 | https://api.docstoc.io/mcp |
| http (plaintext) | http://api.chasa.io/mcp | Inconclusive | 301 | http://api.docstoc.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
draft_chase_email ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_name | string | yes | Client or company name |
| days_overdue | number | yes | How many days past the due date (0 = due today) |
| invoice_amount | number | yes | Invoice amount in dollars |
No output schema declared.
No examples provided.
get_chase_tip ~40
Get a short chase-tone tip for how late an invoice is.
| Name | Type | Req | Description |
|---|---|---|---|
| days_overdue | number | yes | Days past due (0 = due today) |
No output schema declared.
No examples provided.
list_templates ~21
List docstoc free invoice follow-up email templates with URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recommend_template ~47
Recommend a free docstoc payment-reminder template for a given days-overdue stage, with a URL.
| Name | Type | Req | Description |
|---|---|---|---|
| days_overdue | number | yes | Days past due (0 = due today) |
No output schema declared.
No examples provided.
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.