About Twitter Username Changes MCP Server
A lightweight MCP server for checking the historical usernames associated with a Twitter account’s current screen name. It is intended for account-history checks, including assessing frequent name changes as a possible scam warning sign.
Key features
- 01Look up historical usernames by current screen name
- 02Provide a query prompt template
- 03Use a minimal set of dependencies
Use cases
- 01Review a crypto project account’s name history
- 02Check username changes during account research
MCP support
Exposes the `query_username_changes` tool and a prompt template to MCP clients. The tool accepts a screen name and returns available historical usernames.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMETwitter Username Changes MCP Server
An MCP server that tracks the historical changes of Twitter usernames—frequent screen name changes in crypto projects can be a red flag for potential scam risks.
Features
- Username Change History: Query the historical usernames of a Twitter user by their current screen name (e.g.,
@OSINT_Ukraineor@Mormonger). - Prompt Support: Includes a prompt template to guide users in formulating queries.
- Lightweight Design: Built with minimal dependencies (
mcpandrequests) for easy setup.
Installation
Prerequisites
- Python 3.10+
piporuvfor dependency management- Claude Desktop (optional, for MCP integration)
Setup
-
Clone the Repository:
git clone https://github.com/kukapay/twitter-username-changes-mcp.git cd twitter-username-changes-mcp -
Install Dependencies:
pip install mcp[cli] requests
Usage
Running the Server
Start the server in development mode to test locally:
mcp dev main.py
This launches the MCP Inspector, where you can:
- List available tools (
query_username_changes). - Test queries (e.g.,
screen_name: "OSINT_Ukraine"). - Debug prompts.
Integrating with Claude Desktop
-
Configure MCP Server: Edit the Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server:
{ "mcpServers": { "twitter-username-changes": { "command": "python", "args": [ "/absolute/path/to/twitter-username-changes-mcp/main.py" ] } } }Replace
/absolute/path/to/with the full path tomain.py. - macOS:
-
Install the Server:
mcp install main.py --name "TwitterUsernameChanges" -
Query in Claude Desktop:
- Open Claude Desktop and look for the hammer icon (indicating MCP tools).
- Enter a query like:
Show the username change history for Twitter user @OSINT_Ukraine - Expected output:
Username change history for OSINT_Ukraine: User ID 4725638310: - The_HelpfulHand (2016-01-09 to 2020-09-27) - nftpromo_s (2022-02-10 to 2022-02-23) - OSINT_Ukraine (2022-02-24 to 2022-02-25)
Example Queries
-
Query
@Mormonger:Tool input:
screen_name: "Mormonger"Output:
Username change history for Mormonger: User ID 1408886100: - colenoorda (2016-04-02) - Mormonger (2017-01-19 to 2025-02-25) -
Query Invalid Handle:
Tool input:
screen_name: "InvalidUser123"Output:
No username change history found for InvalidUser123
License
This project is licensed under the MIT License. See LICENSE for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.