Twitter Username Changes | AI Builder Hub Review & Alternatives | Flaex AI

VERIFIED

Twitter Username Changes

Safety: 85/100

0.0(0)

This MCP server retrieves historical Twitter username changes, aiding in identifying potential scams by tracking frequent screen name alterations.

MCP ServersSocial MediaDevelopmentData & DatabasesSearch & WebAI & LLMFinance & CryptoUtilitiesFreemium

Boost this tool

Subscribe to listing upgrades or segmented pushes.

Overview

This MCP server retrieves historical Twitter username changes, aiding in identifying potential scams by tracking frequent screen name alterations.

This MCP server is generally safe for querying Twitter username history. The primary risk lies in the accuracy of the data retrieved from Twitter and potential rate limiting. It's risky if the data is used without verification for critical decision-making.

Performance depends on Twitter's API response times. Rate limiting may affect performance under heavy load.

Cost is primarily related to the resources used to run the server. Excessive queries may trigger Twitter API rate limits.

Python2 starsMIT

Connections & Capabilities

Connects To

GitHub

Capabilities

Read

Client Compatibility

Claude Desktop

full

Cursor

untested

Windsurf

untested

VS Code (Copilot)

untested

Quickstart

Install

pip install mcp[cli]

Claude Desktop Config

{
  "mcpServers": {
    "twitter-username-changes": {
      "command": "python",
      "args": [
        "/absolute/path/to/twitter-username-changes-mcp/main.py"
      ]
    }
  }
}

Tools (1)

safe

query_username_changes

Retrieves the historical username changes for a given Twitter screen name.

Read-only operation; retrieves publicly available data.

Security

Auth Method

None

Known Risks

!Reliance on Twitter's API and data availability.
!Potential for rate limiting by Twitter.
!Data accuracy and potential for manipulation by third parties.
!Lack of input validation could expose to injection vulnerabilities if extended.

Safety Score

low risk

Positive

+Read-only operations; only retrieves data.
+No authentication required, reducing risk of credential compromise.
+Limited dependencies minimize potential attack surface.
+Data retrieval is focused on publicly available information.

Risks

-Relies on external Twitter data, which could be inaccurate or manipulated.
-Potential for rate limiting if queries are excessive.
-No input sanitization mentioned, which could lead to injection attacks if extended.
-Lack of built-in error handling could lead to unexpected behavior.

Use Cases

Security & Fraud Detection

-Identifying potential scams by tracking username changes.
-Verifying the legitimacy of Twitter accounts.
-Investigating suspicious activity on Twitter.

OSINT & Research

-Tracking the history of Twitter accounts.
-Analyzing social media trends.
-Gathering information for investigations.

Account Management

-Monitoring brand accounts for unauthorized changes.
-Tracking username availability.
-Auditing account activity.

Who Is This For?

Best For

Security analysts investigating potential scams.
OSINT researchers tracking social media accounts.
Journalists verifying the history of Twitter accounts.
Researchers studying social media trends.

Not Ideal For

Real-time monitoring requiring immediate alerts.
High-volume data processing without rate limiting.
Applications requiring write access to Twitter accounts.

Autonomy & Execution

Default ModeRead-only

Sandboxed

The server only supports read operations, so autonomy is limited to data retrieval. No destructive actions are possible.

StatelessYes

Retry LogicNot documented

ConcurrencySingle-threaded

Production Tip

Implement robust error handling and rate limiting to prevent service disruptions in a production environment.

FAQ

How accurate is the username change history?

The accuracy depends on the data provided by Twitter's API, which may not always be complete or up-to-date.

What happens if a Twitter account is private?

This tool only retrieves publicly available information, so private accounts will not be accessible.

Is there a limit to the number of queries I can make?

Yes, Twitter's API has rate limits that may restrict the number of queries you can make within a certain time period.

Does this server store any user data?

No, this server does not store any user data. It only retrieves and displays information from Twitter's API.

Can I use this server to change Twitter usernames?

No, this server only supports read operations. It cannot be used to change Twitter usernames.

What Python version is required?

Python 3.10 or higher is required.

How do I handle rate limiting?

Implement retry logic with exponential backoff to handle rate limiting errors gracefully.

Key Features

Social Media Development Data & Databases Search & Web AI & LLM Finance & Crypto Utilities

Metrics

Discovered2/14/2026

Reviews0

Saved By0 users

Twitter Username Changes

Overview

Connections & Capabilities

Connects To

Capabilities

Client Compatibility

Quickstart

Install

Claude Desktop Config

Tools (1)

Security

Safety Score

Positive

Risks

Use Cases

Security & Fraud Detection

OSINT & Research

Account Management

Who Is This For?

Best For

Not Ideal For

Autonomy & Execution

FAQ

How accurate is the username change history?

What happens if a Twitter account is private?

Is there a limit to the number of queries I can make?

Does this server store any user data?

Can I use this server to change Twitter usernames?

What Python version is required?

How do I handle rate limiting?

Key Features

Metrics

Related Tools