Model Context Protocol low risk

Twitter Username Changes

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

Connections & Capabilities

Connects To

GitHub

Capabilities

read

Quickstart

Install

pip install mcp[cli]

Config

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

Exposed MCP Tools (1)

safe

query_username_changes

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

Read-only operation; retrieves publicly available data.

Safety Assessment

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.

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.

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.

Safety Assessment

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.

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.