A
licenseNot graded
qualityD
maintenanceScan APIs for security vulnerabilities and get OWASP risk scores. Detects auth bypass, BOLA/IDOR, data exposure, prompt injection, and 12+ security categories.
24 npm
Apache 2.0
rapidapi
by SecurFi
Provides integration with RapidAPI, enabling access to their API marketplace and services through the MCP server.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@rapidapiget current weather data for New York City"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RapidAPI MCP
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.pyclaude config
"RapidAPI": {
"command": "uv",
"args": [
"run",
"--with",
"fastmcp",
"--with",
"requests",
"fastmcp",
"run",
"/Users/{YOUR_USERNAME}/Documents/rapidapi_mcp/server.py"
]
}Available Tools
1 toolget_user_recent_tweetsD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
get_user_recent_tweets
TDQS
D1.7/5.0
Scored across 1 tool
Disambiguation5/5
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.
Naming Consistency5/5
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.
Tool Count2/5
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.
Completeness1/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
- OneOAuthai.withone
Search, document and execute authenticated API calls across 700+ apps via one MCP server
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Load & browser performance testing — drive MaxoPerf from your AI agent with your API key.
Related MCP Servers
fetchsandbox-mcpofficial
AlicenseAqualityAmaintenanceA deterministic eval engine for coding agents. Your agent claims it fixed the bug—this checks it. The same scenario runs twice against a sandbox of the services your code calls, with failures injected on purpose. It must fail on the old code and pass on the new. The verdict is an exit code, not a model's opinion. Every run leaves a receipt.816657 npm1MIT- AlicenseAqualityDmaintenanceEnables testing and validation of APIs for AI agent compatibility, providing scores, grades, and actionable recommendations.3MIT
- AlicenseBqualityCmaintenanceEnables QA/SDET engineers to test APIs by ingesting Swagger/OpenAPI specs and Postman collections, generating and executing tests in multiple languages and frameworks with real-time progress tracking.1117 npm6MIT