Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.sind00/flippa-mcp

NPM · FLIPPA-MCP-SERVER · SCANNED AUG 3

Search, analyze, and evaluate online businesses for sale on Flippa.com marketplace.

Available components

+24 this week 66 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (108 of 109), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (108 of 109), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1422 tokens (~284/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · flippa-mcp-server

# add to Claude Code
claude mcp add sind00-flippa-mcp -- npx -y flippa-mcp-server
# add to Codex CLI
codex mcp add sind00-flippa-mcp -- npx -y flippa-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sind00-flippa-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "flippa-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sind00-flippa-mcp --command npx --arg -y --arg flippa-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  sind00-flippa-mcp:
    command: "npx"
    args: ["-y", "flippa-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "sind00-flippa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "flippa-mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +47
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.20 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 42

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 108 packages

108 packages in the resolved dependency tree · 108 deprecated · 32 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~1,422 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
flippa_analyze_listing ~272

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. Examples: - Analyze a listing: { "listing_id": "12299903" } - Get analysis as JSON: { "listing_id": "12299903", "response_format": "json" }

NameTypeReqDescription
listing_idstringyesThe Flippa listing ID to analyze (e.g., '12299903')
response_formatstringResponse format: 'markdown' for human-readable or 'json' for structured data

No output schema declared.

No examples provided.

flippa_comparable_sales ~315

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. Examples: - Comps for a listing: { "listing_id": "12299903" } - SaaS comparables: { "property_type": "saas", "page_size": 15 }

NameTypeReqDescription
listing_idstringFind comparable listings for this listing ID. If provided, the listing's property_type and revenue range are used for matching.
page_sizeintegerNumber of comparable listings to return (1-20, default 10)
property_typestringFilter comparables by property type. If listing_id is provided, this overrides the listing's type.
response_formatstringResponse format: 'markdown' for human-readable or 'json' for structured data

No output schema declared.

No examples provided.

flippa_get_listing ~175

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. Examples: - Get listing details: { "listing_id": "12299903" } - Get as JSON: { "listing_id": "12299903", "response_format": "json" }

NameTypeReqDescription
listing_idstringyesThe Flippa listing ID (e.g., '12299903')
response_formatstringResponse format: 'markdown' for human-readable or 'json' for structured data

No output schema declared.

No examples provided.

flippa_market_overview ~214

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. Examples: - Full market overview: {} - SaaS market overview: { "property_type": "saas" }

NameTypeReqDescription
property_typestringFocus on a specific property type. If omitted, aggregates across all major types.
response_formatstringResponse format: 'markdown' for human-readable or 'json' for structured data

No output schema declared.

No examples provided.

flippa_search_listings ~446

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. Examples: - Search all open SaaS listings: { "property_type": "saas" } - Most profitable websites: { "property_type": "website", "sort_alias": "most_profitable" } - Ending soon auctions: { "sale_method": "auction", "sort_alias": "ending_soonest" }

NameTypeReqDescription
page_numberintegerPage number for pagination, starting at 1
page_sizeintegerNumber of results per page (1-100, default 30)
property_typestringFilter by property/business type (e.g., 'saas', 'website', 'ecommerce_store')
response_formatstringResponse format: 'markdown' for human-readable or 'json' for structured data
sale_methodstringFilter by sale method: 'auction' or 'classified' (fixed price)
sort_aliasstringSort order for results (e.g., 'most_recent', 'highest_price', 'most_profitable')
statusstringFilter by listing status: 'open' (active), 'closed' (sold), or 'ended' (expired)

No output schema declared.

No examples provided.