# MoonClerk MCP by usefulapi (remote · moonclerk.usefulapi.io)

Read MoonClerk payment forms, customers (plans with subscriptions) and payments. Read-only.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `moonclerk.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-moonclerk/moonclerk.md), [page](https://verifymcp.io/servers/io-usefulapi-moonclerk/moonclerk)

## Channel facts

- Endpoint: `https://moonclerk.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## 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-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1088 tokens (~181/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MoonClerk MCP by usefulapi server?

MoonClerk MCP by usefulapi is a hosted endpoint at https://moonclerk.usefulapi.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 io-usefulapi-moonclerk 'https://moonclerk.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-moonclerk": {
      "url": "https://moonclerk.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-moonclerk": {
      "type": "http",
      "url": "https://moonclerk.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-moonclerk]
url = "https://moonclerk.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-moonclerk --url 'https://moonclerk.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-moonclerk:
    url: "https://moonclerk.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-moonclerk": {
      "Transport": "http",
      "Url": "https://moonclerk.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-moonclerk -t streamable-http -u 'https://moonclerk.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-moonclerk": {
      "type": "http",
      "url": "https://moonclerk.usefulapi.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-10-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (6)

### `moonclerk_list_forms` (~105 tokens)

List payment forms

List the MoonClerk payment forms: id, title, currency, payment_volume (cents), successful_checkout_count and created/updated times. Use the form ids to filter customers (plans) and payments. Read-only. GET /forms.

Input parameters:

- `count` (integer): Rows to return, 1-100 (default 25).
- `offset` (integer): Start position (default 0). Pass the previous reply's next_offset to get the next page.

### `moonclerk_get_form` (~56 tokens)

Get payment form

One payment form by id: title, currency, payment volume and checkout count. Read-only. GET /forms/{id}.

Input parameters:

- `form_id` (integer, required): MoonClerk form id (from moonclerk_list_forms).

### `moonclerk_list_customers` (~273 tokens)

List customers (plans)

List MoonClerk customers, which the MoonClerk web app calls "Plans": each is one payer with their subscription (status, plan amount and interval, next payment date, trial and cancel dates), payment method (brand, last 4), coupon discount, custom form fields and the form they used. Filter by form, status (active, canceled, expired, past_due, pending, unpaid), sign-up date range or next-payment date range, e.g. past_due plans or renewals due this month. The payer's management link and checkout token are never returned. Read-only. GET /customers.

Input parameters:

- `checkout_from` (string): Customers created on or after this date.
- `checkout_to` (string): Customers created on or before this date.
- `count` (integer): Rows to return, 1-100 (default 25).
- `form_id` (integer): Only customers who signed up through this form.
- `next_payment_from` (string): Subscriptions due to bill on or after this date.
- `next_payment_to` (string): Subscriptions due to bill on or before this date.
- `offset` (integer): Start position (default 0). Pass the previous reply's next_offset to get the next page.
- `status` (string): Subscription status.

### `moonclerk_get_customer` (~93 tokens)

Get customer (plan)

One MoonClerk customer (plan) by id with the full subscription, payment method, discount, checkout amounts (subtotal, fee, total, upfront amount, trial days) and custom field answers. The payer's management link and checkout token are never returned. Read-only. GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): MoonClerk customer id (from moonclerk_list_customers).

### `moonclerk_list_payments` (~216 tokens)

List payments

List MoonClerk payments (charges): date, status (successful, refunded, failed), amount, Stripe fee and amount refunded in cents, currency, payer name and email, payment method, form, customer id (recurring payments only), coupon and custom fields. Filter by form, customer, status or charge-date range, e.g. failed payments this month or refunds for one plan. Amounts are in cents. Read-only. GET /payments.

Input parameters:

- `count` (integer): Rows to return, 1-100 (default 25).
- `customer_id` (integer): Only payments of this customer (plan).
- `date_from` (string): Payments charged on or after this date.
- `date_to` (string): Payments charged on or before this date.
- `form_id` (integer): Only payments made through this form.
- `offset` (integer): Start position (default 0). Pass the previous reply's next_offset to get the next page.
- `status` (string): Payment status.

### `moonclerk_get_payment` (~90 tokens)

Get payment

One MoonClerk payment by id with amounts (cents), Stripe fee, refunds, payer, payment method, Stripe references (charge, customer, invoice), coupon, custom fields and one-time checkout data. The checkout token is never returned. Read-only. GET /payments/{id}.

Input parameters:

- `payment_id` (integer, required): MoonClerk payment id (from moonclerk_list_payments).

## Diagnostics

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

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### What is the MoonClerk MCP by usefulapi server?

MoonClerk MCP by usefulapi is listed in the public MCP registry as io.usefulapi/moonclerk. Read MoonClerk payment forms, customers (plans with subscriptions) and payments. Read-only. This page covers its hosted endpoint (https://moonclerk.usefulapi.io/mcp).

### Is the MoonClerk MCP by usefulapi server safe to use?

MoonClerk MCP by usefulapi scores 62 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 MoonClerk MCP by usefulapi server expose?

MoonClerk MCP by usefulapi exposes 6 tools: moonclerk_list_forms, moonclerk_get_form, moonclerk_list_customers, moonclerk_get_customer, moonclerk_list_payments, moonclerk_get_payment. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.

### Does the MoonClerk MCP by usefulapi server require authentication?

Yes. MoonClerk MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the MoonClerk MCP by usefulapi server still maintained?

MoonClerk MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 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://moonclerk.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/moonclerk/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-moonclerk/moonclerk.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-moonclerk/moonclerk.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-moonclerk/moonclerk