Serveur MCP x-scout
Commit 22 oct. 2026Permet aux agents IA de lire des posts X, de rechercher des sujets via Grok et d'auditer les statistiques d'un compte sans nécessiter de connexion.
Aussi connu sous JunJayDev/x-scout
- Étoiles
- 0
- Outils
- 7
- Téléchargements, 30 jours
- —
- Dernière version
- —
- Dernier commit
- 22 oct. 2026
- Licence
- MIT
Qu'est-ce que x-scout MCP ?
Permet aux agents IA de lire des posts X, de rechercher des sujets via Grok et d'auditer les statistiques d'un compte sans nécessiter de connexion. Il expose 7 outils, comme x_read, x_search, x_audit.
Résumé généré à partir du README du projet
À propos du MCP server x-scout
Les développeurs et les agents IA peuvent surveiller l'activité sur X (Twitter), effectuer des recherches par sujet et analyser les performances d'un compte sans avoir besoin de se connecter à un compte. Ce serveur fournit des outils pour lire des posts, des threads ou des réponses spécifiques, et pour parcourir les profils d'utilisateurs afin de voir leur activité récente. Il est conçu pour fonctionner localement via CLI, stdio MCP, ou comme plugin pour Claude Code, et peut être déployé sur Cloudflare Workers pour un accès à distance depuis des clients web comme ChatGPT ou Claude.ai.
La lecture de posts et l'audit de comptes sont des opérations gratuites qui utilisent des endpoints publics. Pour la recherche sémantique, le serveur s'intègre à Grok de xAI, ce qui nécessite une XAI_API_KEY. L'outil x_search utilise Grok pour trouver des liens pertinents, puis récupère le texte original pour que l'agent puisse le traiter. Les utilisateurs peuvent également utiliser l'outil x_audit pour obtenir des informations approfondies sur la cadence de publication d'un compte, les ratios d'engagement et les statistiques de vues.
Ce que vous pouvez faire avec
- 1Recherche de sujets spécifiques via GrokUn développeur peut demander à une IA de trouver et de résumer les discussions récentes sur un sujet technique précis en utilisant la recherche sémantique.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Outils MCP x-scout 7
Détectés depuis le READMEx_readx_searchx_auditsavetalkspreadeng
| x_read | — | |
| x_search | — | |
| x_audit | — | |
| save | — | |
| talk | — | |
| spread | — | |
| eng | — |
Configuration
XAI_API_KEY
| Nom | Description | Type |
|---|---|---|
| XAI_API_KEY | — |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessiblejunjaydev/x-scout is public and reachablegithub.com/junjaydev/x-scout ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-10-22github.com/junjaydev/x-scout ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle7 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNo tool named like delete, drop or execRéussi
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubEnglish · 中文
x-scout
X (Twitter) for AI agents: read posts, search topics and browse profiles without login.
x-scout provides a CLI, MCP tools and a self-contained agent skill. Open a post, search with one query, or visit an account's profile and recent posts. No mandatory scoring or account audits. Reading is free and needs no key; search uses xAI's Grok and requires an API key.
x-scout read https://x.com/jack/status/20
x-scout search "bun 1.3 production"
x-scout read @jack --posts 10
Runs locally through CLI, stdio MCP or Claude Code plugin, or on your own Cloudflare Worker
for remote clients. No runtime dependencies. Optional x_audit provides account statistics
when the user asks for deeper analysis.
Install
You can let an agent install x-scout for you: "install x-scout, following https://github.com/JunJayDev/x-scout/blob/main/INSTALL.md".
Recommended installation path by client:
- Claude Code: install the marketplace plugin for tools and skill together.
- Codex: configure the MCP server for tools and marketplace plugin for the skill.
- Cursor, VS Code, Claude Desktop, and other MCP clients: configure the stdio MCP server.
- claude.ai, ChatGPT, and phones: deploy a remote worker to Cloudflare in one command.
- Agents without MCP support: copy the self-contained skill folder.
Install the plugin (bundles skill and MCP server, prompts for an optional xAI key and stores it in the system keychain):
/plugin install x-scout --marketplace JunJayDev/x-scout
On Claude Code versions older than 2.1.275:
/plugin marketplace add JunJayDev/x-scout
/plugin install x-scout@x-scout
Or add the MCP server alone without the plugin:
claude mcp add x-scout -- npx -y github:JunJayDev/x-scout mcp
Add the MCP server for tools:
codex mcp add x-scout -- npx -y github:JunJayDev/x-scout mcp
Add the skill via the marketplace:
codex plugin marketplace add JunJayDev/x-scout
Then install x-scout from the plugin list.
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"x-scout": {
"command": "npx",
"args": ["-y", "github:JunJayDev/x-scout", "mcp"]
}
}
}
To enable search in Cursor, add "env": {"XAI_API_KEY": "xai-..."} inside the x-scout block.
Add to .vscode/mcp.json:
{
"servers": {
"x-scout": {
"type": "stdio",
"command": "npx",
"args": ["-y", "github:JunJayDev/x-scout", "mcp"]
}
}
}
Standard configuration for clients supporting stdio MCP (command npx, arguments ["-y", "github:JunJayDev/x-scout", "mcp"]):
{
"mcpServers": {
"x-scout": {
"command": "npx",
"args": ["-y", "github:JunJayDev/x-scout", "mcp"]
}
}
}
To enable search, add "env": {"XAI_API_KEY": "xai-..."} inside the server entry. Requires Node 18 or newer.
Deploy a remote MCP server to your own Cloudflare account (the free plan is sufficient):
npx -y github:JunJayDev/x-scout deploy
A browser opens once to log in to Cloudflare. The command deploys the worker, pipes secrets via stdin, runs a smoke test against the public URL, and outputs a connector URL:
https://x-scout.<your-subdomain>.workers.dev/mcp/<token>
Add this URL in claude.ai as a custom connector, or in ChatGPT as a developer-mode connector. No client login is required. Connectors added on the web sync to mobile apps.
Run with --rotate to generate a new token, or --check to re-test the endpoint. Run deploy again after updating keys.
Copy skills/x-scout/ into your agent's skills directory (~/.claude/skills/, ~/.codex/skills/, or .agents/skills/). The skill is self-contained: the agent executes node scripts/x-scout.mjs <command> directly using Node 18 or newer, with no packages to install.
Turn on search
Reading and auditing operate without configuration. To turn on semantic search:
- Obtain an API key from console.x.ai.
- Save and test credentials:
npx -y github:JunJayDev/x-scout setup # saves to ~/.config/x-scout/config.env (mode 600)
npx -y github:JunJayDev/x-scout doctor # tests key and read sources
Alternatively, set XAI_API_KEY in your environment. Run deploy again to sync the key to your remote worker.
Without a key, reading and auditing remain fully functional, and the skill falls back to web searches (site:x.com ...) followed by x_read.
Advanced options: setup --base-url <url> (or XAI_API_BASE) configures custom endpoints speaking xAI's Responses API; XAI_MODEL specifies the model (default: grok-4.7). SEARCH_TIMEOUT_S sets how long one query may take (default 120); three queries took 3.5 minutes in one test, so raise it if queries come back as FAILED, not searched. deploy forwards these settings to your remote server.
Quick start
Install the CLI globally:
npm install -g https://github.com/JunJayDev/x-scout/archive/refs/heads/main.tar.gz
Or invoke directly with npx -y github:JunJayDev/x-scout <command>.
x-scout read https://x.com/karpathy/status/2039805659525644595
x-scout read <post-url> --replies --max-replies 30 # inspect corrections and nuance
x-scout read @handle --posts 30
x-scout audit @handle
x-scout search "bun 1.3 production" "migrated from node to bun" --from 2026-09-01
x-scout search "remotion agent" "AI 视频 剪辑 agent" --handle remotion --json # one query per language
Real output of x-scout read:
[1] @karpathy · Andrej Karpathy · 2026-04-02 20:42Z
https://x.com/karpathy/status/2039805659525644595
22M views · 61k likes · 2.9k replies · 7.4k reposts · 2.2k quotes · 108k bookmarks
LLM Knowledge Bases
...
Tools
| Tool | Capabilities | Key |
|---|---|---|
x_read |
1-10 post URLs, IDs, profile URLs or @handles. Mode: post, thread, replies. Profiles with up to 100 recent posts. Optional translation. |
None |
x_search |
1-5 queries; Grok finds links and public readers supply original text, authors and dates. Inclusive dates, up to 20 allowed or excluded handles, image/video understanding, 6 results by default, at most 10 across all queries. Loads originals within an 8-second read budget; verify: false returns model snippets instead. |
XAI_API_KEY |
x_audit |
Reads an account's last 10-100 posts: cadence, mix, median and p90 views, likes per 1k followers, save and talk ratios, link-out share, breakout multiplier, top posts by views and by saves, X's "About this account", hints. | None |
All three tools take format: "json" for structured output.
Default text keeps the post content and interaction counts. Analysis ratios and routine
source details are omitted; fallback and incomplete-content warnings stay visible. Threads
show the target post once. Full metadata is available with --json.
For optional analysis, the library exports postSignals(post) to compute:
save: bookmarks / likes (measures retention and reference value)talk: replies / likes (elevated talk with low save flags debate or bait)spread: (reposts + quotes) / likes (amplification rate)eng: engagements / views (interaction density)
Agent workflow
The skill starts with the user's request:
- Open a supplied link with
x_read, or run onex_searchquery. - Show useful content with source links. Search returns original posts; reuse them and
use
x_readonly for missing content, threads or replies. - Stop when the request is answered. Add queries, account analysis or source tracking only when needed for the user's task.
For profiles, x_read returns the bio, counts and 20 recent posts by default. Set
profile_posts: 0 (CLI --posts 0) for just the bio and counts, or choose up to 100 posts.
Search asks Grok for links only, then loads original posts in parallel (up to 10, with a shared 8-second reading budget). Supported Grok models use low reasoning effort to avoid spending high-effort reasoning on ordinary searches. A failed read keeps the link and error; loading a post does not fact-check its claims.
A query is a fixed topic. Grok searches its core terms, then follows up on distinct angles, experiences and objections within that topic. All caller queries share at most five tool turns, with early stopping when coverage is sufficient. It prioritizes detailed original long posts, independent perspectives and useful questions over routine news and copied summaries. Substantive controversial or unverified claims remain eligible as the author's views, without fact-checking or treating inclusion as proof.
English is the default search language. Technical topics may add Chinese; local topics
prioritize their local language. One topic is normally enough as input. Results target six
distinct posts by default, with a total cap of ten (max_results), even across multiple queries.
Two to six strong matches are preferable to padding; zero or one is valid for sparse topics.
verify: false (CLI --no-verify) skips the readers and returns model snippets. Existing
verify: true / --verify calls remain supported; original loading is now the default.
Optional account and draft analysis references: judging, signals, ranking code. They are not part of the default browsing flow.
Read only: x-scout never logs in and never likes, follows, replies or posts on X. It provides links and leaves actions to the user. See platform rules.
Costs
| Operation | Cost |
|---|---|
| Reading & auditing | Free. Uses public endpoints; FxTwitter allows 1,000 requests per minute per IP. |
| Searching | xAI bills about $5 per 1,000 posts fetched by the model, plus tokens. Queries share a five-turn budget; each turn may contain several searches. Focused follow-ups can increase latency and fetched-post costs. Output reports posts fetched; JSON includes search-call counts when available. |
| Remote server | Cloudflare Workers free plan includes 100,000 requests per day. |
| Token footprint | Short post under 100 tokens; account audit roughly 600-1,000 tokens. |
Limits
- Reading relies on public services (FxTwitter, vxTwitter) and X's embed endpoint. Fallbacks lack views and bookmarks, and X's embed truncates long posts.
- Retrieved replies exclude hidden, protected, or deleted items.
- Search discovery still uses Grok, so latency and selection vary. Original text comes from public readers; if they fail, the result keeps its link. Opt-in model snippets may be incomplete or paraphrased.
- No For You feed, notifications, direct messages, or write actions on X, by design.
- Evaluation is an agent methodology, not an absolute classifier. Report incorrect assessments via the judging issue template.
Library
Install the package:
npm install github:JunJayDev/x-scout
import { makeContext, runRead, runAudit } from "x-scout";
const ctx = makeContext(process.env);
const { items } = await runRead({ targets: ["https://x.com/jack/status/20"] }, ctx);
x-scout/worker exports the Cloudflare Worker handler for custom deployments.
Related projects
- FxEmbed: Primary reading backend. Maintainers request self-hosting under high volume.
- x-reader and x-md: Reading tools and skills for agents; x-md offers keyless search via pooled accounts; x-reader provided the model for INSTALL.md.
- Agent-Reach: Multi-platform reader for agents. X search requires personal cookies; x-scout never touches user accounts.
- twitterapi.io MCP: Paid X data API with read tools for bulk collection.
- bangermeter: Scores reach potential using X's published ranking weights. x-scout describes reach and scores value.
- twag: LLM tweet triage with score caps on restated opinions and rolling account averages.
- bullshit-detector: Claim-by-claim text verification. The judging rubric borrows two diagnostic questions from it.
- Bouncer: Feed filtering using plain-language categories. Acts on timelines; x-scout answers questions.
Part of an agent media literacy series. github-scout applies the same methodology to GitHub: identifying existing open-source solutions before an agent writes code.
Contributing
Issues and pull requests are welcome. See CONTRIBUTING.md. Tests run offline: node --test.
License
MIT. See LICENSE.
Questions sur x-scout MCP
Quels outils x-scout MCP fournit-il ?
Il expose 7 outils, dont x_read, x_search, x_audit, save, talk.
Ai-je besoin d'un compte X pour utiliser x-scout ?
Non, la lecture et l'audit sont gratuits et ne nécessitent ni connexion ni compte.
Puis-je déployer x-scout pour l'utiliser avec ChatGPT ou Claude.ai ?
Oui, vous pouvez déployer un MCP server distant sur votre propre compte Cloudflare pour l'utiliser comme connecteur personnalisé.