MoonClerk MCP by usefulapi
REMOTE · MOONCLERK.USEFULAPI.IO
Read MoonClerk payment forms, customers (plans with subscriptions) and payments. Read-only.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Finance and Payments
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.3 functional
- 24 Oct 26 62
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 25 Oct 2026 · Probed https://moonclerk.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.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 moonclerk.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://moonclerk.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://moonclerk.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://moonclerk.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://moonclerk.usefulapi.io/mcp |
| Authorisation server | https://moonclerk.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://moonclerk.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/moonclerk/ |
| http (plaintext) | http://moonclerk.usefulapi.io/mcp | Inconclusive | 302 | http://moonclerk.usefulapi.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 →
moonclerk_get_customer Get customer (plan) ~93
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | MoonClerk customer id (from moonclerk_list_customers). |
No output schema declared.
No examples provided.
moonclerk_get_form Get payment form ~56
One payment form by id: title, currency, payment volume and checkout count. Read-only. GET /forms/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | integer | yes | MoonClerk form id (from moonclerk_list_forms). |
No output schema declared.
No examples provided.
moonclerk_get_payment Get payment ~90
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_id | integer | yes | MoonClerk payment id (from moonclerk_list_payments). |
No output schema declared.
No examples provided.
moonclerk_list_customers List customers (plans) ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
moonclerk_list_forms List payment forms ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
moonclerk_list_payments List payments ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · moonclerk.usefulapi.io
claude mcp add --transport http io-usefulapi-moonclerk 'https://moonclerk.usefulapi.io/mcp'
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.