PrintFriendly MCP server vs ScrapeAtlas

PrintFriendly MCP server 40

No machine payment protocol (0). Per-document overage prices public (20). Free plan with 100 documents, no card (20). A person signs in for the key (0). 0 + 20 + 20 + 0 = 40.

ScrapeAtlas 55

No x402, MPP or L402 on ScrapeAtlas's own endpoints. The vendor's eight Actors on the Apify Store, covering TikTok, Instagram, Meetup and Couchsurfing at $1.98 per 1,000 successful requests, can be paid through Apify, whose prepaid token is sold over x402, so partial credit for a third-party route on part of the catalogue (10 of 40). Per-unit prices are on the home page without a login, 1 credit per successful request and packs at $1.90, $1.78 and $1.25 per 1,000, with the 2-credit endpoints named (20). 100 free credits at signup, no card (20). A person signs up in a browser and creates a key; the Apify route reaches four platforms without a ScrapeAtlas account (5 of 20). 10+20+20+5 = 55.

PrintFriendly MCP server 74

Two tools with schemas in a public server card at /.well-known/mcp/server-card.json (25). llms-install.md in the repository; no llms.txt read (5 of 10). Clear descriptions, with 'What each tool does' on the docs page (17 of 20). Typed inputs (12 of 15). FAQ with the 401, limit and plan errors (12 of 15). Registry 1.0.1; no changelog (3 of 15). 25 + 5 + 17 + 12 + 12 + 3 = 74.

ScrapeAtlas 88

An OpenAPI 3.1.0 file (version 0.1.0, 34 MB) is public at scrapeatlas.com/docs/openapi.json with 384 paths and 386 operations, a per-platform x-api-key security scheme on each, response schemas for 200 and every documented error, and 931 component schemas (25). llms.txt at scrapeatlas.com/docs/llms.txt lists all 373 endpoints with one-line descriptions and schema links, and endpoint pages carry a copy-as-Markdown action (10). 386 operations have a summary and 373 a description, median 39 words, saying what public page is read, what the response holds, how to page and what it costs. llms.txt says not to assume one normalised JSON shape. Guidance on when not to call an endpoint is thin, with 9 descriptions using only and 2 instead (14 of 20). 1,390 parameters, 304 with enums, most with minLength, maxLength or a pattern, 232 operations needing one required parameter and 143 none; the 12 POST bodies are typed (14 of 15). A response example on 373 operations and examples on 508 parameters, HTTP 400 to 504 mapped to one failure object with 33 codes, per-endpoint error tables and code samples in six languages; no Retry-After header declared (14 of 15). Paths are under /v1 and a dated public changelog started on 24 September 2026 with 58 updates, but nothing is marked deprecated in the file, breaking changes aren't flagged, and the 14 October GitHub entry says former paths keep working without saying for how long (11 of 15). 25+10+14+14+14+11 = 88.

PrintFriendly MCP server 58

Registry entry com.printfriendly/printfriendly and repository commit on 16 October 2026 (30). Fewer than three dated releases found in 90 days (0). Help pages and support (8 of 15). Official registry entry under its own namespace (15). Repository holds docs and manifests (5 of 10). 30 + 0 + 8 + 15 + 5 = 58. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

ScrapeAtlas 70

The newest change is CLI 0.26.0 on 28 October 2026 per the 30 October npm reading, not re-read on 2 November, after the StockX endpoints on 27 October, still the changelog's newest entry on 2 November (30). 15 dated release days between 21 September and 27 October, 58 updates (20). Closed service with a public changelog. Support in the dashboard is for customers with a credit purchase, the contact form takes buying questions and privacy requests, and no Discord, forum or issue tracker was found; the careers page lists a customer support role (7 of 15). io.github.OnlineDopamine/scrapeatlas is in the official MCP registry under a GitHub-verified personal namespace, at 1.0.0 since 5 October and describing about 40 platforms against 49 now. The CLI is current on npm and an n8n node exists, but there are no SDKs (10 of 15). The CLI package has no repository field, no public source and no visible CI; it needs Node 22 or newer (3 of 10). 30+20+7+10+3 = 70.

PrintFriendly MCP server 87

Two compact tools (25). Output format choice (12 of 20). Errors that name the cause and the fix, including how long to wait (18 of 20). Annotated, read_page read-only and idempotent (20). One key and a REST API with the same limits (12 of 15). 25 + 12 + 18 + 20 + 12 = 87.

ScrapeAtlas 76

API reading. Responses are bounded by limit on 93 operations, by per-body caps, by format on 19 and view on 14 operations, and by since and until on about 60; Instagram and Twitch have reduced basic-profile endpoints. No field selection was found. The MCP server loads 373 tool definitions with no documented subset, which on the MCP reading would score 5 (15 of 25). Cursor pagination on 130 operations, sort on 28, date windows, and coverage.order reported on every list since 2 October 2026 (20). One failure object with code and message, a requestId on every response, retryable codes named, and an HTTP status table (19 of 20). All data reads are GET, failed requests aren't charged, and the docs say which codes to retry; no idempotency key on the 12 POST batch reads and MCP annotations weren't read (14 of 20). Median one required parameter and defaults on limits, but no official SDK in any language. The npm CLI, the n8n node and six-language samples stand in (8 of 15). 15+20+19+14+8 = 76.

PrintFriendly MCP server 49

Closed service under terms naming Print Friendly LLC; the repository is MIT (15). Page content isn't used to train AI models, images are analysed while the page is processed, and mobile copies are deleted after delivery (20 of 30). The first server address stays as an alias, a dated change kept working (8 of 20). Third-party AI providers named as service providers without a list (8 of 20). 15 + 20 + 8 + 8 = 51.

ScrapeAtlas 59

Closed service with clear terms dated 29 September 2026 naming the legal entity, governing law and liability cap; the CLI is MIT on npm with no source published (15 of 30). The privacy policy (19 October 2026) gives retention periods, 90 days for raw usage records, 30 days for inactive key metadata, 10 minutes to 30 days for OAuth artefacts, and says workers keep no archive of results, which the terms and the Public Data Notice repeat. Providers are named with their roles. No DPA is published; the terms say to arrange one before submitting such a workload (22 of 30). The terms promise reasonable notice of material changes when practicable, and the changelog records a Reddit retirement on 29 September and kept paths on 14 October, but there is no deprecation policy with periods and nothing in the OpenAPI file is marked deprecated (7 of 20). Supabase, Tinybird, PostHog, Stripe, Google, OpenAI and Affonso are named with purposes, but the only location statement is that the operator is in the UAE and infrastructure can process in other countries (10 of 20). 15+22+7+10 = 54.

PrintFriendly MCP server 46

One API key in a header (20 of 30). One read-only tool and one that creates files, nothing destructive (15 of 20). read_page returns third-party web pages with no injection guidance (3 of 15). No audit log; usage counts per key (5 of 15). No security.txt or certifications found (3 of 20). 20 + 15 + 3 + 5 + 3 = 46.

ScrapeAtlas 55

Customer keys with prefix sa_live_, several per account, each with an expiry date, revoked within 60 seconds and stored as hashes per the privacy policy, and keys can't start a checkout or create keys. No scopes or per-platform keys. The MCP server adds an authorization-code flow with PKCE S256, dynamic client registration, refresh-token rotation and revocation, but a single scope, scrapeatlas. No documented option to send a secret in a query string, and the MCP page says never to put the key in a prompt, argument or URL (22 of 30). The whole surface is read-only retrieval of public pages with no destructive action, and an OAuth grant covers retrieval plus the account's usage records only; nothing restricts a key to some platforms (16 of 20). Every response is third-party page content, and the only guidance found concerns keeping secrets out of tool arguments, nothing on treating returned text as untrusted (2 of 15). GET /v1/activity returns per-request metadata (endpoint, time, status, duration) newest first with filters, GET /v1/usage daily totals, responses carry x-credits-charged and x-credits-remaining, and the dashboard shows a credit history (13 of 15). No security.txt (404), no disclosure policy, bug bounty, SOC 2 or ISO 27001; the privacy policy describes access controls and incident notices and gives an abuse address (2 of 20). 22+16+2+13+2 = 55.