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

io.github.sind00/flippa-mcp

NPM · FLIPPA-MCP-SERVER · SCANNED SEP 24

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

Available components

0 this week 79 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability66
  • 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 Management80
  • Stability observed for 24 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.sind00/flippa-mcp server?

io.github.sind00/flippa-mcp runs locally as an npm package, launched with npx -y flippa-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · flippa-mcp-server

# add to Claude Code
claude mcp add sind00-flippa-mcp -- npx -y flippa-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "sind00-flippa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "flippa-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sind00-flippa-mcp": {
      "command": "npx",
      "args": [
        "-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"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sind00-flippa-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "flippa-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sind00-flippa-mcp -t stdio -c npx -a -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.

  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 Sept 26 +1

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

  • 20 Sept 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 18 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/flippa-mcp-server@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 109 packages
Packages resolved 109
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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_formatstring–Response 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_idstring–Find comparable listings for this listing ID. If provided, the listing's property_type and revenue range are used for matching.
page_sizeinteger–Number of comparable listings to return (1-20, default 10)
property_typestring–Filter comparables by property type. If listing_id is provided, this overrides the listing's type.
response_formatstring–Response 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_formatstring–Response 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_typestring–Focus on a specific property type. If omitted, aggregates across all major types.
response_formatstring–Response 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_numberinteger–Page number for pagination, starting at 1
page_sizeinteger–Number of results per page (1-100, default 30)
property_typestring–Filter by property/business type (e.g., 'saas', 'website', 'ecommerce_store')
response_formatstring–Response format: 'markdown' for human-readable or 'json' for structured data
sale_methodstring–Filter by sale method: 'auction' or 'classified' (fixed price)
sort_aliasstring–Sort order for results (e.g., 'most_recent', 'highest_price', 'most_profitable')
statusstring–Filter by listing status: 'open' (active), 'closed' (sold), or 'ended' (expired)

No output schema declared.

No examples provided.

Common questions

What is the io.github.sind00/flippa-mcp server?

io.github.sind00/flippa-mcp is listed in the public MCP registry as io.github.sind00/flippa-mcp. Search, analyze, and evaluate online businesses for sale on Flippa.com marketplace. This page covers its npm package (flippa-mcp-server).

Is the io.github.sind00/flippa-mcp server safe to use?

io.github.sind00/flippa-mcp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.sind00/flippa-mcp server expose?

io.github.sind00/flippa-mcp exposes 5 tools: flippa_search_listings, flippa_get_listing, flippa_analyze_listing, flippa_comparable_sales, flippa_market_overview. Their descriptions and schemas cost roughly 1,422 tokens of context every time the server is loaded.

Is the io.github.sind00/flippa-mcp server still maintained?

io.github.sind00/flippa-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.sind00/flippa-mcp server under?

io.github.sind00/flippa-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.