Model Context Protocol server wrapping the Tinder API
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tinder-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for the Tinder API, implemented in TypeScript.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
api-docsAPI documentation
api-docs
server-statusServer status information
server-status
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for Tinder Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for the Tinder API, implemented in TypeScript.
This MCP server provides a standardized interface for interacting with the Tinder API. It handles authentication, request processing, rate limiting, caching, and error handling, making it easier to build applications that integrate with Tinder.
The server follows a modular architecture with the following components:
Clone the repository:
git clone https://github.com/yourusername/tinder-api-mcp-server.git
cd tinder-api-mcp-server
Install dependencies:
npm install
Create a .env file based on .env.example:
cp .env.example .env
Edit the .env file with your configuration settings.
Start the development server:
npm run dev
Build the project:
npm run build
Run the production server:
npm start
Run tests:
npm test
POST /mcp/auth/sms/send: Send SMS verification codePOST /mcp/auth/sms/validate: Validate SMS verification codePOST /mcp/auth/facebook: Authenticate with FacebookPOST /mcp/auth/captcha: Verify CAPTCHAPOST /mcp/auth/refresh: Refresh authentication tokenGET /mcp/user/:userId: Get user profileGET /mcp/user/recommendations: Get user recommendationsPUT /mcp/user/profile: Update user profileGET /mcp/user/matches: Get user matchesPOST /mcp/interaction/like/:targetUserId: Like a userPOST /mcp/interaction/superlike/:targetUserId: Super like a userPOST /mcp/interaction/pass/:targetUserId: Pass on a userPOST /mcp/interaction/boost: Boost profilePOST /mcp/interaction/message/:matchId: Send messageGET /mcp/interaction/messages/:matchId: Get messages for a matchPOST /mcp/tools: Execute MCP toolGET /mcp/resources/:resourceId: Access MCP resourceGET /mcp/info: Get server informationThe server provides the following MCP tools:
authenticate_sms: Authenticate user with SMSauthenticate_facebook: Authenticate user with Facebookverify_captcha: Verify CAPTCHA responselike_user: Like a user profilesuper_like_user: Super like a user profilepass_user: Pass on a user profileboost_profile: Boost user profile visibilityget_user_profile: Get user profile informationget_recommendations: Get potential matchesclear_cache: Clear cacheget_rate_limits: Get rate limit informationThe server provides the following MCP resources:
api-docs: API documentationserver-status: Server status informationMIT