REDACTED PUBLIC COPY (13 October 2026). Names, internal file paths and internal tool names are replaced; nothing else is changed. The sha256 values below refer to the unredacted originals, available on request from seo@blotato.com. # Study #7 classifier brief (PREREG v3.2 s5). Written 2026-10-13, before any sample was drawn. You label GitHub repositories from files ALREADY SAVED on disk. Each repo's folder is (internal file) and may hold `repo.json` (description, topics, homepage), `README.md`, `FILES.txt` (root file list) and manifests (`package.json`, `pyproject.toml`, `requirements.txt`, `setup.py`, `go.mod`, `Cargo.toml`, `server.json`, `smithery.yaml`). A folder with `GONE.txt` = the repo is no longer readable. ## Hard rules - Read ONLY those saved files. No web requests of any kind, no Chrome, no `gh`, no `curl`. Never run, install or import any code from these repos. Never contact any MCP endpoint. - Never infer from the repo name alone. If the saved files do not say it, the answer is `false` (unreadable = no). - Do not write files. Return your answer as text in the exact format at the end. - Judge each repo on its own. You are not told when it was created; do not try to work it out. ## Task N: `{"server": bool, "publishes": bool}` (study #6 inclusion and capability rules, verbatim) `server` = true only if ALL hold (study #6 RULES R1): 1. It is an MCP server: MCP server code in the repo. A skill, CLI, SDK, client, prompt pack or agent with no MCP server is excluded (`not_mcp_server`). 2. At least one tool acts on a named in-scope platform's accounts or content (publish, read posts/profiles/comments/metrics, reply, DM, analytics, search platform content). In-scope platforms (10): X/Twitter, LinkedIn, Facebook, Instagram, Threads, TikTok, YouTube, Pinterest, Bluesky, Reddit. 3. The platform is named in the repo name, topics, or the first 300 characters of the README. Threads counts only if the files show Meta's Threads (Meta / Threads API / threads.net / graph.threads.net wording; "Threads" named as a social platform alongside another in-scope social platform; or Instagram/Meta login or tokens used for it). Generic threads (Slack, email, discussion, forum, comment) never count. `server` = false for any of these: `template` (starter/boilerplate/example), `awesome_list` (lists or directories of servers), `not_mcp_server`, `no_platform_action` (platform named only incidentally, e.g. a "share to Twitter" docs link, or a generic tool), `threads_not_meta`, `ads_only` (every platform tool is about paid ads: campaigns, ad sets, budgets, ad creatives, boosting), `downloader_transcript` (only downloads media or fetches transcripts/subtitles/captions; title, description, duration or thumbnail alone also stays here), `unreadable` (no README/description says what the tools do), `other`. - A server that BOTH downloads/transcribes AND does something else on the platform (returns engagement metrics, comments, search results, channel/playlist/feed listings, or publishes) IS included. - A server that queries a third-party database of platform content collected earlier, or a marketplace/listing site, is `no_platform_action` unless its own docs say it fetches from the platform at request time. - Platforms outside the 10 (Mastodon, Discord, Telegram, Slack, WhatsApp, Snapchat, Twitch, Medium, Substack, etc.) do not count. `publishes` (only meaningful when `server` is true; else false) = a documented tool creates an ORGANIC post, reel, video, short, pin, thread or tweet on an in-scope platform account. Scheduling a post counts. Ad, promoted-only, nullcast and dark posts do not count. Replies and comments alone do not count. ## Task D: `{"mcp_code": bool}` `mcp_code` = true if the saved files show the repo contains MCP (Model Context Protocol) server OR client code: e.g. an MCP SDK dependency (`@modelcontextprotocol/sdk`, `mcp`, `fastmcp`, `mcp-go`, `rmcp`, etc.) in a manifest, or a README describing an MCP server/client this repo implements. False for: a list/directory of MCP servers, docs or prompts only, a repo where "mcp" means something else (e.g. Minecraft Coder Pack, a person's initials, a product code), a config-only repo with no code, or unreadable/GONE. ## Output (exactly this, one line per repo, nothing else after the block) For N batches: ``` /\t\t\t\t\t ``` For D batches: ``` /\t\t\t ``` Every repo in your batch gets exactly one line, in the order given.