mcp.eveoy.com

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

Very long descriptions are sometimes used to bury instructions to the AI. Skim it before allowing.

This server isn't on gate's handpicked list. That's not necessarily bad, but there's no third-party signal about it — review its tools carefully.

The description states the bonus must be 0 or $20–$200 (2000–20000 cents), but the JSON schema sets minimum/maximum to ±9007199254740991 — essentially unbounded, including large negative numbers. Since total_usd = units×2499 + units×sku + round(units×bonus×1.33), a negative bonus value would reduce the computed total below the actual base price. If this schema is used to validate input server-side (as implied by 'never returns a number the form would reject'), a caller could request an artificially low quote. This should be tightened to the documented 2000–20000 range (or 0).

Same issue as in get_pricing: the schema permits shopper_bonus_cents far outside the documented $20–$200 range, including negative values, while the tool claims 'the server recomputes the total — what get_pricing quotes is exactly what Stripe charges.' If validation relies on the same loose schema, this could allow a manipulated/negative bonus to lower the real payment amount below intended pricing. Recommend clamping min/max to 0 or 2000–20000.