Apify MCP servers
Registry manifests for two hosted Model Context Protocol servers. Both run as Apify Actors in Standby mode and speak Streamable HTTP.
This repository holds the server.json files only — it is the public home the
MCP registry points at. The server implementations
live in their own repositories.
Servers
io.github.afanasenkoa/zillow-mcp-server
Zillow property and agent data. Three tools:
Each row carries address, price, beds and baths, agent name, email and phone, Zestimate, schools, photos and price history.
Endpoint: https://afanasenko--zillow-mcp-server.apify.actor/mcp
Store page: https://apify.com/afanasenko/zillow-mcp-server
io.github.afanasenkoa/instagram-profile-mcp-server
Instagram profile data. Six tools:
Up to 38 fields per profile, including emails, bio links, engagement rate, business category and language.
Endpoint: https://afanasenko--instagram-profile-scraper-mcp-server.apify.actor/mcp
Store page: https://apify.com/afanasenko/instagram-profile-scraper-mcp-server
Connecting
Both endpoints require an Apify API token, passed as a bearer token. Create one under Apify Console → Integrations.
{
"mcpServers": {
"zillow": {
"type": "http",
"url": "https://afanasenko--zillow-mcp-server.apify.actor/mcp",
"headers": { "Authorization": "Bearer <APIFY_TOKEN>" }
}
}
}
An unauthenticated request returns 401 with api-token-missing — that is the Standby actor
asking for the token, not an outage.
Both servers are billed per result through Apify's pay-per-event model, at the same price as the batch actor behind them. A tool call starts a real run, so it costs what that run costs.
Publishing
mcp-publisher login github
mcp-publisher publish server-zillow.json
mcp-publisher publish server-instagram.json
Bump version in the manifest whenever the underlying actor's version changes, or the registry
rejects the publish as a duplicate.
Licence
MIT — see LICENSE. The licence covers these manifests; the actors themselves are commercial and are not distributed here.