com.mcparmory/apify
Apify
Build, deploy, and run web scraping and automation actors in the cloud
alive probed 2026-10-19
112tools
≈ 32ktokens, estimate
≈ 16.2 %of Claude's 200k window
23×the median server
10.2 sto initialize
686 msto list tools
- Run it
- uvx mcparmory-apify==1.0.5 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- Apify 4.1.1
- Capabilities
- logging, prompts, resources, tools
- Instructions
- none
- Of a 1M window
- ≈ 3.2 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/mcparmory/registry
- Registry
- active, updated 2026-05-11 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| update_actor | 2 226 | 7 % |
| create_actor | 2 107 | 7 % |
| run_actor_sync_get_dataset_items | 1 225 | 4 % |
| run_task_sync_and_get_dataset_items | 1 140 | 4 % |
| run_actor_sync_get_dataset_items_with_input | 1 010 | 3 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.