F
licenseNot graded
qualityD
maintenanceEnables searching and comparing live credit card merchant offers (cash back, points, statement credits) across Amex, Chase, Citi, PayPal, Rakuten, and Capital One from any AI agent.
-
Pinchy
Server Details
Find coupon and promo codes for any online store, ordered by how likely they are to work.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- trypinchy/pinchy-mcp
- GitHub Stars
- 0
- Server Listing
- pinchy
TDQS
A4.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another operation. find_coupons has a singular, well-defined purpose and is the only entry point an agent needs to consider.
Naming Consistency5/5
The tool name follows a clean verb_noun convention: find_coupons. It is descriptive, readable, and accurately signals both the action and the resource it targets.
Tool Count4/5
The server exposes exactly one tool, which is minimal but justifiable because its purpose is narrowly scoped to coupon discovery. It is slightly below the typical 3-15 tool range, but the count feels appropriate rather than padded.
Completeness5/5
The single tool covers the full stated purpose of the server: given a store URL, it returns actionable coupon codes, including an empty list when none are known. There are no obvious dead ends or missing operations for a coupon-finding service.
Available Tools
1 toolfind_couponsFind coupon codesARead-onlyInspect
Find coupon / promo / discount codes for an online store. Pass the store domain or any URL from the store (product, cart or checkout page). Returns codes ordered by how likely they are to work: try them at checkout from the top, keep the one that lowers the total the most. Codes can expire or carry store restrictions, so none is guaranteed; an empty list means none are known for that store.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of codes to return | |
| store | Yes | Store domain or any URL on the store, e.g. "momcozy.com" |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| domain | Yes | |
| coupons | Yes | |
| storeName | No |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, and the description aligns with these while adding meaningful behavioral context: result ordering is by likelihood of working, results are not guaranteed, and empty lists have a defined meaning. This goes beyond the structured annotations and helps the agent set user expectations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded: it states the purpose and input format first, then explains result ordering and caveats. Every sentence contributes useful information, with no filler or redundant phrasing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity read-only tool with a high-coverage schema and an output schema, the description covers all essential context: what to pass, what the tool returns, how to use the results, and important limitations. Nothing critical is missing for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents both parameters. The description repeats the store parameter semantics but does not add new parameter-level detail beyond the schema. The baseline of 3 is appropriate because the schema carries the parameter documentation burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: find coupon/promo/discount codes for an online store. It also specifies the accepted input format (store domain or any store URL), making it unambiguous. No sibling tools exist, so differentiation is not required.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage guidance: pass a store domain or any store URL, and explains how to interpret and act on results (try codes from the top, keep the one that lowers total the most). It also manages expectations by noting codes may expire or carry restrictions, and that an empty list means no known codes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
find_coupons
Related MCP Connectors
Verified deals, store policies & a trust score for thousands of online retailers. No auth.
Which of your credit cards to use at any store, from verified bank data. No bank login.
Shopping search across 100M+ products, with every retailer's offer and live price in one place.
Search current U.S. gift-card discounts from validated providers. Anonymous and read-only.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI models to find the best online deals by browsing and interacting with multiple shopping platforms like Amazon and eBay across various regions. It uses Playwright to automate searches and retrieve product information from compatible e-commerce and deal-tracking websites.7 npm3MIT
- FlicenseNot gradedqualityBmaintenanceEnables users to search for hidden coupons, generate commission short links, find combined savings deals, set price drop alerts, and track historical prices for JD.com products.1-
- AlicenseCqualityDmaintenanceAutomated grocery shopping assistant with intelligent unit pricing and automatic coupon clipping, enabling AI to search products, manage carts, and plan grocery runs via Claude Desktop or CLI.181-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.