Twitter Username Changes MCP

Communauté Marketing et ventes

Track historical Twitter username changes.

Que pouvez-vous faire avec Twitter Username Changes MCP ?

  • Username Change History: Query the historical usernames of a Twitter user by their current screen name (e.g., @OSINT_Ukraine or @Mormonger).
  • Prompt Support: Includes a prompt template to guide users in formulating queries.
  • Lightweight Design: Built with minimal dependencies (mcp and requests) for easy setup.

Installation

Les étapes d'installation sont dans la documentation ci-dessous. Documentation

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Twitter Username Changes MCP Server
  2. Features
  3. Installation
  4. Usage
  5. License

Twitter 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_Ukraine or @Mormonger).
  • Prompt Support: Includes a prompt template to guide users in formulating queries.
  • Lightweight Design: Built with minimal dependencies (mcp and requests) for easy setup.

Installation

Prerequisites
  • Python 3.10+
  • pip or uv for dependency management
  • Claude Desktop (optional, for MCP integration)
Setup
  1. Clone the Repository:
     git clone https://github.com/kukapay/twitter-username-changes-mcp.git
     cd twitter-username-changes-mcp
  2. 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
  1. 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 to main.py.

  2. Install the Server:
     mcp install main.py --name "TwitterUsernameChanges"
  3. 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
  1. 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)
  2. 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.

Questions fréquentes

Qu'est-ce que Twitter Username Changes MCP ?

Track historical Twitter username changes.

Comment installer Twitter Username Changes MCP ?

Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.

Twitter Username Changes MCP est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Twitter Username Changes MCP ?

Il est publié par kukapay. AI.tn le référence sans le maintenir ni le recommander.

Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.