x-scout MCP server
2026년 10월 22일 커밋로그인 없이도 AI agent가 X 게시물을 읽고, Grok을 통해 주제를 검색하며, 계정 통계를 감사할 수 있도록 지원합니다.
다른 이름 JunJayDev/x-scout
- 스타
- 0
- Tools
- 7
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 10월 22일
- 라이선스
- MIT
x-scout MCP란?
로그인 없이도 AI agent가 X 게시물을 읽고, Grok을 통해 주제를 검색하며, 계정 통계를 감사할 수 있도록 지원합니다. 7개 도구를 제공합니다. 예: x_read, x_search, x_audit.
프로젝트 README에서 생성된 요약
x-scout MCP server 정보
개발자와 AI agent는 계정에 로그인할 필요 없이 X (Twitter) 활동을 모니터링하고, 주제 검색을 수행하며, 계정 성과를 분석할 수 있습니다. 이 server는 특정 게시물, 스레드 또는 답글을 읽고 사용자 프로필을 탐색하여 최근 활동을 확인하는 도구를 제공합니다. CLI, stdio MCP를 통해 로컬에서 작동하거나 Claude Code의 플러그인으로 사용할 수 있도록 설계되었으며, Cloudflare Workers에 배포하여 ChatGPT 또는 Claude.ai와 같은 웹 기반 클라이언트에서 원격으로 접속할 수 있습니다.
게시물 읽기와 계정 감사는 공개 엔드포인트를 사용하는 무료 작업입니다. 시맨틱 검색을 위해 이 server는 xAI의 Grok과 통합되어 있으며, 이를 위해서는 XAI_API_KEY가 필요합니다. x_search 도구는 Grok을 사용하여 관련 링크를 찾은 다음 agent가 처리할 수 있도록 원본 텍스트를 가져옵니다. 또한 사용자는 x_audit 도구를 활용하여 계정의 게시 주기, 참여율 및 조회 통계에 대한 심층적인 인사이트를 얻을 수 있습니다.
활용 사례
- 1Grok을 통한 특정 주제 연구개발자가 AI에게 시맨틱 검색을 사용하여 특정 기술 주제에 대한 최근 논의를 찾아 요약하도록 지시할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
x-scout MCP 도구 7
README에서 감지됨x_readx_searchx_auditsavetalkspreadeng
| x_read | — | |
| x_search | — | |
| x_audit | — | |
| save | — | |
| talk | — | |
| spread | — | |
| eng | — |
구성
XAI_API_KEY
| 이름 | 설명 | 유형 |
|---|---|---|
| XAI_API_KEY | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능junjaydev/x-scout is public and reachablegithub.com/junjaydev/x-scout ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-22github.com/junjaydev/x-scout ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음7 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기English · 中文
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.
x-scout MCP 질문
x-scout MCP는 어떤 도구를 제공하나요?
7개 도구를 제공합니다. 예: x_read, x_search, x_audit, save, talk.
x-scout를 사용하려면 X 계정이 필요한가요?
아니요, 게시물 읽기와 계정 감사는 무료이며 로그인이나 계정이 필요하지 않습니다.
x-scout를 배포하여 ChatGPT나 Claude.ai에서 사용할 수 있나요?
네, 원격 MCP server를 개인 Cloudflare 계정에 배포하여 커스텀 커넥터로 사용할 수 있습니다.