Servidor MCP simplificado para interactuar con la API de Stripe.
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation, error handling guidance, and output schema clarity. All tools are write operations (payment/subscription/customer creation) but lack confirmation patterns or dry-run support. Descriptions are present but generic (avg ~100 chars, below 194-char baseline). Parameter descriptions exist but lack format constraints, ranges, or validation rules. No output schema documentation visible. Error handling returns Stripe errors but does not guide LLM recovery actions.
Creates a Stripe Customer with the specified email and optional name. Returns customer_id. Note: Supabase update is handled by the backend tool after receiving this ID.
Creates a Stripe PaymentIntent with the specified amount, currency, and description. Returns client_secret and payment_intent_id.
Creates a Stripe Subscription for a customer with the specified price. Returns subscription_id and status.
No output schema documentation. Tools return JSON objects (client_secret, payment_intent_id, etc.) but LLM cannot see expected fields, types, or structure. Breaks downstream tool chaining and forces LLM to infer response shape.
Destructive operations (create_payment, create_subscription, create_customer) lack confirmation or dry-run support. Agents cannot preview consequences before committing irreversible charges or subscriptions. No idempotent hints or retry guidance.
Parameter descriptions lack format constraints and validation rules. 'amount' has no range (cents? max?). 'currency' has no enum (ISO 4217 codes?). 'price_id' and 'customer_id' have no format hints. LLM cannot validate inputs before sending.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | 2026-07-28+ | v2 |
Error responses return raw Stripe errors without recovery guidance. 'Error de Stripe: ...' tells LLM nothing about whether to retry, ask user, or abort. No error classification (retryable vs fatal).
Metadata parameter is object type with no schema. LLM cannot see what fields are valid or required. Documentation says 'user_id will be added automatically' but this is not enforced in schema, LLM might pass conflicting user_id values.