rapidapi
# RapidAPI MCP
[](https://smithery.ai/server/@SecurFi/rapidapi_mcp)
``` bash
uv add -r requirements.txt
# install the server in Claude (and restart Claude manually)
fastmcp install server.py
# debug in the inspector
fastmcp dev server.py
```
## claude config
```
"RapidAPI": {
"command": "uv",
"args": [
"run",
"--with",
"fastmcp",
"--with",
"requests",
"fastmcp",
"run",
"/Users/{YOUR_USERNAME}/Documents/rapidapi_mcp/server.py"
]
}
```
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined as retrieving recent tweets for a user, leaving no room for confusion or misselection.
The tool name 'get_user_recent_tweets' follows a consistent verb_noun pattern (get + user_recent_tweets), and since there is only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
A single tool for a server named 'rapidapi' suggests a severely limited scope, as APIs typically offer multiple endpoints for various operations. This feels too thin and underpowered for any meaningful domain coverage, indicating a poor fit for typical agent workflows.
The server appears to target Twitter or social media data, but with only one tool to get recent tweets, it lacks any other operations like posting tweets, searching, managing users, or handling other API functions. This is severely incomplete for the implied domain, leaving major gaps that will hinder agent tasks.