MCP server for searching, analyzing, and evaluating Flippa.com marketplace listings
Well-structured TypeScript MCP server with 5 tools focused on Flippa marketplace data. All tools have explicit schemas, descriptions, and parameter documentation. Naming follows verb_noun convention clearly (search_, get_, analyze_, comparable_, market_). Schemas use Zod validation with proper enums and constraints. Output schemas are partially documented (descriptions mention structure but no formal JSON Schema for responses). Error handling is present but minimal, no guidance for recovery or categorization. All tools are read-only, reducing security complexity. Main gaps: response schemas not formally documented, error handling lacks recovery guidance, and no output truncation strategy despite CHARACTER_LIMIT constant.
Analyze a Flippa listing's valuation, compute financial metrics, and assess risk. This is a computed tool that fetches listing data and calculates valuation metrics including revenue multiples, profit multiples, ROI estimates, and risk factors. Args: - listing_id: The Flippa listing ID to analyze (e.g., "12299903"). Required. - response_format: "markdown" (default) or "json" Returns: Computed analysis including: - Financial metrics: revenue/profit multiples, annual revenue, price per visitor, ROI estimate - Verdict: "underpriced" (<2x revenue), "fair" (2-4x), "overpriced" (>4x), or "insufficient_data" - Risk factors: unverified revenue/traffic, low traffic, no bids, missing images, etc.
Find comparable listings on Flippa for valuation comparison. If a listing_id is provided, fetches that listing first and uses its property_type and revenue range (0.5x-2x) to find similar listings. You can also search by property_type directly. Args: - listing_id: Find comparables for this listing. Optional. - property_type: Filter by type. Overrides the target listing's type if both provided. Optional. - page_size: Number of comparables to return, 1-20 (default 10) - response_format: "markdown" (default) or "json" Returns: Target listing (if listing_id provided), list of comparable listings, average price, median price, average revenue multiple, and price range.
Get full details for a specific Flippa listing by ID. Args: - listing_id: The Flippa listing ID (e.g., "12299903"). Required. - response_format: "markdown" (default) or "json" Returns: Complete listing details including price, revenue, profit, traffic stats, seller info, verification status, description, and more.
Response schemas not formally documented. Tool descriptions mention what is returned (e.g., 'Paginated list of Flippa listings with price, revenue, profit...') but do not provide structured JSON Schema for the response object. LLMs cannot reliably parse unpredictable output structures.
No documented output truncation or character limit enforcement visible in tool implementations. constants.ts defines CHARACTER_LIMIT = 25000, but it is unclear how this is applied to tool responses. Large responses risk exceeding context windows without explicit handling.
Error responses lack recovery guidance. Tools make external API calls (Flippa v3 API via axios) but error handling is not visible in provided source. If an API call fails, LLMs need explicit direction (e.g., 'Flippa API unavailable. Try again in 30 seconds.' or 'Listing not found. Did you mean: [similar IDs]?').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Get aggregate market statistics from the Flippa marketplace. Queries listings across property types to build a market snapshot including total counts, price/revenue/profit statistics, and verification rates. Args: - property_type: Focus on a specific type (website, saas, ecommerce_store, etc.). If omitted, aggregates across all major types. Optional. - response_format: "markdown" (default) or "json" Returns: Market overview with total listings, breakdown by property type (count, avg price, avg revenue), price/revenue/profit statistics (min, max, avg, median), average revenue multiple, and verified revenue percentage.
Search and browse listings on the Flippa marketplace. Args: - property_type: Filter by type (website, saas, ecommerce_store, fba, ios_app, android_app, ai_apps_and_tools, youtube, newsletter, service, other) - status: Filter by status (open, closed, ended). Default: "open" - sale_method: Filter by sale method (auction, classified) - sort_alias: Sort by (lowest_price, highest_price, most_active, most_recent, ending_soonest, most_profitable, most_relevant) - page_number: Page number (default 1) - page_size: Results per page, 1-100 (default 30) - response_format: "markdown" (default) or "json" Returns: Paginated list of Flippa listings with price, revenue, profit, bid count, and verification status. Includes pagination metadata with has_more flag.
No error classification visible. Errors should be categorized as retryable (API timeout), user-fixable (invalid listing_id), or fatal (auth failure) so the LLM knows how to respond.
Tool composition: flippa_analyze_listing appears to be a computed tool that 'fetches listing data and calculates valuation metrics.' This mixes data retrieval with computation. Consider whether analysis should be client-side (agent calls get_listing, then processes) or server-side with clear responsibility boundaries.