Ext Ops Panel
Open dashboard
Comparison

Apify vs app.sallim/korea-realty

Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). app.sallim/korea-realty is an MCP server published by sallim.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceApifyapp.sallim/korea-realty
Docker MCP Catalog Listed
Version: sha256:42cc91f13363
Forks (GitHub): 443
Pulls (Docker Hub): 39 277
Stars (Docker Hub): 0
Stars (GitHub): 15 507
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.131.11
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Apify vs app.sallim/korea-realty
FactApifyapp.sallim/korea-realty
Marketplaces that list it11
Stars (GitHub) (differs)15 507 (better)0 (worse)
Pulls (Docker Hub) (differs)39 277No figure on Docker Hub
Forks (GitHub) (differs)443 (better)0 (worse)
Last release (differs)Not published2026-11-10
Where it runs (differs)On your machine (mcp/apify-mcp-server)Remote server (realty.sallim.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/apify/actors-mcp-servergithub.com/sallim-app/korea-realty
Changes in the last 7 days (differs)011
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 2 days ago returned HTTP 200

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Apify

In its own words, on Docker MCP Catalog:

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.

app.sallim/korea-realty

In its own words, on Official MCP Registry:

Korean real estate: court auctions, 10M+ MOLIT records, subscription notice facts, loan/DSR rules

How to run each

Apify As a local MCP server: Docker image

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio apify-mcp-server -- docker run -i --rm -e APIFY_TOKEN mcp/apify-mcp-server

Requires: APIFY_TOKEN (secret)

app.sallim/korea-realty

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only app.sallim/korea-realty has a remote endpoint we check. How we check endpoints

Tools each declares

Only Apify has

  • abort-actor-run
  • apify--rag-web-browser
  • call-actor
  • fetch-actor-details
  • fetch-apify-docs
  • get-actor-run
  • get-dataset-items
  • get-key-value-store-record
  • search-actors
  • search-apify-docs

Only app.sallim/korea-realty has

  • fetch
  • realty_area_price_bands
  • realty_auction_alerts
  • realty_auction_history
  • realty_auction_sale_rate
  • realty_builder_presale_record
  • realty_capital_gains_tax
  • realty_compare_auction_vs_market
  • realty_compare_regions
  • realty_complex_pyeong_price
  • realty_complex_rent_by_pyeong
  • realty_complex_report
Show the remaining 44
  • realty_demographics
  • realty_get_auction_case
  • realty_invest_risk
  • realty_loan_eligibility
  • realty_loan_limit
  • realty_location_scores
  • realty_macro_indicators
  • realty_market_signals
  • realty_member_transfer_check
  • realty_move_in_supply
  • realty_nonapt_prices
  • realty_notice_facts
  • realty_notice_text
  • realty_onbid_sale_rate
  • realty_poi_nearby
  • realty_poi_stats
  • realty_policy_rules
  • realty_predict_price
  • realty_presale
  • realty_presale_context
  • realty_presale_cost
  • realty_presale_funding_plan
  • realty_presale_price_trend
  • realty_presale_vs_market
  • realty_public_rental_notices
  • realty_reconstruction
  • realty_redevelopment
  • realty_redevelopment_burden
  • realty_region_price_stats
  • realty_region_rankings
  • realty_region_trend_basket
  • realty_remodel_feasibility
  • realty_rental_yield
  • realty_search_auctions
  • realty_search_complexes
  • realty_search_onbid
  • realty_small_deposit_check
  • realty_subscription_odds
  • realty_subscription_score
  • realty_supply_demand_balance
  • realty_supply_pipeline
  • realty_vacant_housing
  • report_issue
  • search

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (app.sallim/korea-realty as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of app.sallim/korea-realty publish no settings it asks for, so we do not compare settings.

What it can do: Apify · What it can do: app.sallim/korea-realty · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built