MCP server for the FastSpring API — manage subscriptions, accounts, and webhook events from Claude
Strong foundation with 7 well-named, read-only tools covering a coherent FastSpring domain. All tools have descriptions (avg 180 chars, within baseline 194) and Zod schemas with typed parameters. Naming follows verb_noun pattern (get_, list_, search_). However, output schemas are undocumented, responses are JSON-stringified without field documentation, forcing LLMs to infer structure. Error handling is basic (try/catch with generic messages). Missing tool annotations (readOnlyHint), per-tool risk classification, and actionable recovery guidance. Parameter descriptions are solid but lack format constraints (e.g., date format YYYY-MM-DD stated in description but not enforced in schema). No pagination support despite list_subscriptions and list_events returning potentially large result sets.
Get full account details by FastSpring account ID. Returns email, name, address, and associated subscriptions.
Get full webhook event payload by event ID. Use after list_events to inspect the complete data FastSpring sent.
Get full subscription details by FastSpring subscription ID. Returns status, product, next charge date, pricing, account, and tags (referrer = LinkStorm user ID).
List FastSpring webhook events. Use for webhook gap analysis — comparing what FastSpring sent vs what Symfony processed. Note: 'processed' means delivered to your endpoint, NOT successfully handled by your code.
Get charge/payment history for a subscription. Shows successful charges, failed payments, refunds. Use to distinguish voluntary churn (canceled) from involuntary churn (payment failure).
Output schemas undocumented. Tools return JSON.stringify(data) without field documentation. LLMs cannot infer which fields are present, their types, or how to chain results to downstream tools.
No pagination support. list_subscriptions and list_events accept limit but return no cursor, next_token, or total_count. Large result sets risk context window exhaustion.
Error messages lack recovery guidance. Generic 'FastSpring API error (status)' and 'Invalid subscriptionId' do not tell LLM what to do next or how to self-correct.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
List subscriptions with optional filters. Use accountId to find all subs for a customer.
Search FastSpring accounts by email. This is the entry point for debugging — you typically start from a customer email, not a FastSpring ID.
Missing tool annotations. No readOnlyHint declared despite all tools being read-only. Agents cannot distinguish safe tools from destructive ones without explicit hints.
Date format constraints stated in descriptions but not enforced in schema. 'begin' and 'end' params accept any string; no regex pattern or format validation in Zod schema.