MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

TwitterAPIs

Earlier Revision Publisher unverified Confidence: Good (0.85)

TwitterAPIs is an MCP server published by TwitterAPIs, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does TwitterAPIs support the current MCP specification (2026-07-28)?

Not yet confirmed. TwitterAPIs is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is TwitterAPIs a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for TwitterAPIs (as of 2026-08-20).

How do I connect to TwitterAPIs?

TwitterAPIs is available via the package npm:@twitterapis/mcp, the official MCP Registry under io.github.TwitterAPIs/twitterapis-mcp, the source repository at https://github.com/twitterapis/twitterapis-mcp. Authentication: unknown. Transports: stdio.

Does TwitterAPIs support MCP revision 2025-11-25?

Yes. TwitterAPIs supports MCP revision 2025-11-25 (checked 2026-08-20).

Does TwitterAPIs support MCP revision 2026-07-28?

No. TwitterAPIs was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were TwitterAPIs's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Official MCP server for twitterapis.com. Read and write Twitter/X: search, users, tweets, DMs.

Which MCP spec revisions does TwitterAPIs support?

TwitterAPIs has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is TwitterAPIs?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for TwitterAPIs

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
0
Forks
0
Last pushed
(44 days ago)
Created
Open issues
0
Primary language
JavaScript
License (repository)
MIT
Continuous integration
None detected
Tests
Present
Security policy
None

Declared topics: ai-agents, api, claude, cursor, developer-tools, llm-tools, mcp, mcp-server, model-context-protocol, tweets, twitter, twitter-api, twitter-client, twitter-data, twitter-scraper, twitter-search, windsurf, x, x-api — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
0.9.3
Last published
First published
Releases
28
License (package)
MIT
Maintainers
1
Direct dependencies
2
Unpacked size
188 KB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.TwitterAPIs/twitterapis-mcp at version 0.6.4 - lists package npm:@twitterapis/mcp and repository https://github.com/twitterapis/twitterapis-mcp - accessed
  2. npm registry metadata for @twitterapis/mcp at published version 0.9.3, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed