{
  "markdown": "# Apify MCP servers\n\nRegistry manifests for two hosted Model Context Protocol servers. Both run as Apify Actors in\nStandby mode and speak Streamable HTTP.\n\nThis repository holds the `server.json` files only — it is the public home the\n[MCP registry](https://registry.modelcontextprotocol.io) points at. The server implementations\nlive in their own repositories.\n\n## Servers\n\n### `io.github.afanasenkoa/zillow-mcp-server`\n\nZillow property and agent data. Three tools:\n\n| Tool | What it does |\n|---|---|\n| `zillow_search_by_zip` | Homes for sale, for rent or sold in one or more US ZIP codes |\n| `zillow_search_by_url` | Any Zillow search, browse, sold or single-property URL, filters included |\n| `zillow_lookup_property` | One property by `zpid` |\n\nEach row carries address, price, beds and baths, agent name, email and phone, Zestimate, schools,\nphotos and price history.\n\nEndpoint: `https://afanasenko--zillow-mcp-server.apify.actor/mcp`\nStore page: <https://apify.com/afanasenko/zillow-mcp-server>\n\n### `io.github.afanasenkoa/instagram-profile-mcp-server`\n\nInstagram profile data. Six tools:\n\n| Tool | What it does |\n|---|---|\n| `instagram_analyze_followers_following` | Export the follower or following list of a public account |\n| `instagram_analyze_specific_accounts` | Enrich a list of handles you already have |\n| `instagram_network_expansion` | Expand seed handles through Instagram's Suggested for You |\n| `instagram_keyword_discovery` | Find accounts by keyword |\n| `instagram_location_discovery` | Find accounts by location |\n| `instagram_post_engagement_discovery` | The accounts that engaged with a given post |\n\nUp to 38 fields per profile, including emails, bio links, engagement rate, business category and\nlanguage.\n\nEndpoint: `https://afanasenko--instagram-profile-scraper-mcp-server.apify.actor/mcp`\nStore page: <https://apify.com/afanasenko/instagram-profile-scraper-mcp-server>\n\n## Connecting\n\nBoth endpoints require an Apify API token, passed as a bearer token. Create one under\n[Apify Console → Integrations](https://console.apify.com/settings/integrations).\n\n```json\n{\n  \"mcpServers\": {\n    \"zillow\": {\n      \"type\": \"http\",\n      \"url\": \"https://afanasenko--zillow-mcp-server.apify.actor/mcp\",\n      \"headers\": { \"Authorization\": \"Bearer <APIFY_TOKEN>\" }\n    }\n  }\n}\n```\n\nAn unauthenticated request returns `401` with `api-token-missing` — that is the Standby actor\nasking for the token, not an outage.\n\nBoth servers are billed per result through Apify's pay-per-event model, at the same price as the\nbatch actor behind them. A tool call starts a real run, so it costs what that run costs.\n\n## Publishing\n\n```bash\nmcp-publisher login github\nmcp-publisher publish server-zillow.json\nmcp-publisher publish server-instagram.json\n```\n\nBump `version` in the manifest whenever the underlying actor's version changes, or the registry\nrejects the publish as a duplicate.\n\n## Licence\n\nMIT — see [LICENSE](LICENSE). The licence covers these manifests; the actors themselves are\ncommercial and are not distributed here.\n",
  "bytes": 3035,
  "sha": "584cd18b41358a3590923bf3454b3cf59fc1e482311d026a022048a890f1187a",
  "repo_slug": "afanasenkoa/apify-mcp-servers",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_afanasenkoa_zillow_mcp_server_66845c7b/readme"
}