Twitter Username Changes MCP Server

What is Twitter Username Changes MCP Server?

An MCP server that tracks the historical changes of Twitter usernames. It allows users to query past screen names of any Twitter user by their current handle, helping identify frequent name changes that may indicate scam risks in crypto projects.

How to use Twitter Username Changes MCP Server?

Install dependencies with pip install mcp[cli] requests. Run mcp dev main.py to test locally via the MCP Inspector, or integrate with Claude Desktop by editing the JSON config file and running mcp install main.py --name "TwitterUsernameChanges". Then query using the query_username_changes tool with a screen_name argument (e.g., "OSINT_Ukraine").

Key features of Twitter Username Changes MCP Server

• Query username change history by current screen name.
• Includes a prompt template to assist query formulation.
• Lightweight with minimal dependencies (mcp and requests).
• Returns user ID, past usernames, and active date ranges.

Use cases of Twitter Username Changes MCP Server

• Investigate frequent Twitter username changes in crypto projects for scam red flags.
• Research a user’s account history before engaging or transacting.
• Verify if a known username has been reused across different identities.
• Audit social media accounts during due diligence or OSINT investigations.

FAQ from Twitter Username Changes MCP Server

What are the runtime dependencies?

Python 3.10+ and the mcp[cli] and requests Python packages.

Does this server require authentication or API keys?

No. The README does not mention any authentication tokens or API keys for the underlying data service.

What transport protocol does the server use?

It uses the MCP protocol over stdio, as configured via the command and args in the Claude Desktop JSON config.

Where does the historical username data come from?

The README does not specify the data source; it only describes the query tool and its output format.

What happens if I query a handle with no change history?

The tool returns: "No username change history found for <screen_name>".