- Reliability 10/20
- server.json clearly defines a streamable-http remote endpoint with a required Authorization header, and the README's tool list, default tool set (actors, docs, apify/rag-web-browser), and auto-injection rules (call-actor/Actor tools/get-actor-run triggering get-dataset-items, etc.) are internally consistent with no obvious contradictions. However, this is a static-only review and the provided material contains no verifiable test files or CI workflow contents (the README only names a badge and a check.yaml file, without evidencing its content). Per the static calibration rule, reliability is capped at 12. Score: 10.
- Security and permissions 8/20
- The manifest marks the Authorization token as isSecret and isRequired, showing reasonable baseline credential handling. However, the default tool set includes call-actor and Actor tools with openWorldHint (executing arbitrary third-party Apify Actors with real external network access and side effects such as scraping and incurred cost), and the README documents optional agentic payment flows (x402/Skyfire/AGI) where, for example, the x402 flow has the client 'automatically sign a $1.00 USDC transaction' to fund a prepaid balance, with no explicit per-spend confirmation step described beyond ordinary MCP tool-call approval. Telemetry is also enabled by default (opt-out only). These are visible but incompletely scoped/confirmed risks; they do not rise to an unmitigated red line since payment features are opt-in, capped in amount, and refundable, and open-world execution is disclosed via openWorldHint for client-side gating. Score: 8.
- Maintenance 15/20
- The project is MIT-licensed, versioned at 0.14.2, has CONTRIBUTING.md and DEVELOPMENT.md, a defined contribution policy and canary pre-release process, and is distributed via Docker Hub through the community-maintained mcp-registry (README itself notes deployment frequency there is 'unknown'). The repo is not archived, and 2605 stars with 110 open issues indicate active usage. No explicit security-response channel or SECURITY.md is evidenced in the provided material. Score: 15.
- Documentation 17/20
- The README is extensive: table of contents, a tool overview table with a default-enablement legend, tools configuration (URL query params and CLI flags), backward-compatibility notes, disclosed limitations (schema truncation rules, etc.), a privacy policy, telemetry opt-out instructions, and a troubleshooting link. Gaps include no concrete per-Actor cost figures (only 'costs vary'), and payment-flow fee/token-lifetime details are deferred to an external link not included in the provided material. Score: 17.
- Setup experience 14/20
- Two clear setup paths are documented: the hosted OAuth endpoint ('just the URL') and local npx with APIFY_TOKEN, plus JSON config examples, CLI flag examples, a one-click MCPB installer, and a list of tested clients — overall steps are clear. As this is a static review, the provided material contains no verifiable CI or test evidence confirming the connection flow actually works end-to-end, so per the static calibration rule setup is capped at 15. Score: 14.