io.github.Role1776/mcp-x

MCPcommunity
v0.1.1io.github.Role1776UnknownUpdated 24d agoGitHub

Search, read and publish X posts and manage users, lists and media via the X API v2.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
24d agoLast update
Needs 4 credentials before it runs
  • X_API_KEYAPI keyrequired

    OAuth 1.0a consumer key. developer.x.com -> your project -> your app -> Keys and tokens.

  • X_API_KEY_SECRETAPI keyrequired

    OAuth 1.0a consumer secret, issued together with X_API_KEY.

  • X_ACCESS_TOKENAPI keyrequired

    User access token. Set the app permissions to Read and Write BEFORE generating it: a token keeps the permissions it was created with, and a read-only one fails every write until it is regenerated.

  • X_ACCESS_TOKEN_SECRETAPI keyrequired

    User access token secret, issued together with X_ACCESS_TOKEN.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.Role1776
LicenseUnknown
Version0.1.1
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 23d agoHow well does this scan work?
EvalsNone
IndexedSep 10, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source23d ago

Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Search, read and publish X posts and manage users, lists and media via the X API v2.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in social media