Twitter NoAuth
MCP Server - Twitter NoAuth provides Twitter API access without requiring local credential setup, enabling headless operation in remote environments. Built by buryhuang, it implements a decoupled architecture where clients complete OAuth flows independently and pass credentials as context to the server. The implementation supports core Twitter operations including searching tweets, retrieving user tweets, posting new content, and replying to existing tweets. It handles automatic token refreshing and is designed for containerization with Docker, making it particularly valuable for AI assistants that need to interact with Twitter while maintaining separation between credential storage and server implementation.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.
Scan details: Circle-IR · 2026-09-02 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- cloud-infra
- Source
- PulseMCP
- Repository
- github.com/baryhuang/mcp-twitter-noauth
- Author type
- human
- Last scanned
- 2026-09-02
- Updated
- 2026-09-02
Use via MCP
Resolve Twitter NoAuth from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.