Back to Browse

Sorsa MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for the Sorsa.io X/Twitter data API

About

MCP server for the Sorsa.io X/Twitter data API

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-designed MCP server with clean architecture and proper authentication. The API key is correctly required and passed via environment variables, not hardcoded. Input validation uses Zod schemas, and the code is straightforward with no obvious malicious patterns. Minor quality issues around error handling breadth and response logging do not significantly impact security. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

4 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

Sorsa.io API key, sent in the ApiKey header with every request.Required

Environment variable: SORSA_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-sorsa-io-sorsa-mcp": {
      "env": {
        "SORSA_API_KEY": "your-sorsa-api-key-here"
      },
      "args": [
        "-y",
        "sorsa-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Sorsa MCP

An MCP server for the Sorsa.io API v3 — access to X/Twitter data: profiles, tweets, search, follow/retweet checks, Sorsa scores, lists and communities.

The server exposes 40 tools, one per API endpoint.

Installation

npm install
npm run build

Or, once published, run it with no install via npx (see below).

Configuration

You need a Sorsa API key. It is read from the SORSA_API_KEY environment variable and sent with every request in the ApiKey header.

VariableRequiredDefault
SORSA_API_KEYyes
SORSA_BASE_URLnohttps://api.sorsa.io/v3

Connecting a client

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project).

Using the published npm package (nothing to install, npx fetches it):

{
  "mcpServers": {
    "sorsa": {
      "command": "npx",
      "args": ["-y", "sorsa-mcp"],
      "env": {
        "SORSA_API_KEY": "YOUR_KEY"
      }
    }
  }
}

Or running from a locally built checkout:

{
  "mcpServers": {
    "sorsa": {
      "command": "node",
      "args": ["D:\\Code\\Cursor Projects\\Sorsa_MCP\\dist\\index.js"],
      "env": {
        "SORSA_API_KEY": "YOUR_KEY"
      }
    }
  }
}

Claude Desktop

Edit %APPDATA%\Claude\claude_desktop_config.json and add the same mcpServers block as above, then restart the app.

Local check

# build
npm run build

# run (communicates over stdio — easiest to test through a client)
SORSA_API_KEY=YOUR_KEY npm start

The quickest way to confirm your key works is the get_key_usage_info tool — it returns your remaining request balance and the key's expiration date.

Available tools

Profiles: get_user_info, get_user_info_batch, get_followers, get_following, get_verified_followers, get_account_about

Tweets: get_tweet_info, get_tweet_info_bulk, get_user_tweets, get_tweet_comments, get_tweet_quotes, get_retweeters, get_article, get_trends

Search: search_tweets, search_users, search_mentions, get_space_info

Communities: get_community_members, get_community_tweets, search_community_tweets

Checks: check_follow, check_comment, check_quoted, check_retweet, check_community_member

Sorsa metrics: get_sorsa_score, get_sorsa_score_changes, get_followers_stats, get_top_followers, get_top_following, get_new_followers_7d, get_new_following_7d

Lists: get_list_members, get_list_tweets, get_list_followers

Utilities: username_to_id, id_to_username, link_to_id, get_key_usage_info

Project layout

  • src/endpoints.ts — a declarative table of every endpoint (method, path, parameters). To add or change a tool, edit this file only.
  • src/index.ts — the HTTP client plus tool registration driven by that table.

How it works

Each endpoint is one entry in ENDPOINTS. Based on each field's in (path / query / body), the handler routes arguments into the URL path, the query string, or the JSON body, then sends the request to Sorsa with the ApiKey header. The response is returned to the client as JSON text.

License

MIT

Reviews

No reviews yet

Be the first to review this server!