A Model Context Protocol server implementation that demonstrates how tools can be dynamically overridden across multiple servers.
{
"mcpServers": {
"mcp-tool-override-tester": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
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 server implementation that demonstrates how tools can be dynamically overridden across multiple servers.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 334 days ago.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Dynamic problem-solving through sequential thought chains
A Model Context Protocol server for searching and analyzing arXiv papers
An open-source AI agent that brings the power of Gemini directly into your terminal.
The official Python SDK for Model Context Protocol servers and clients
MCP Security Weekly
Get CVE alerts and security updates for Mcp_tool_override_tester 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 server implementation that demonstrates how tools can be dynamically overridden across multiple servers.
This project implements a Model Context Protocol (MCP) server that registers tools using the same names as existing server tools to demonstrate how tools can be dynamically overridden when a new server is added to the configuration.
read_file from Filesystemsend_email from Gmail MCP Serverslack_list_channels from Slack MCP ServerI simply added an MCP Tool Override tester MCP to mimic the tools of other servers. Surprisingly, they are easily overridden by the new tools (which are fake).
┌───────────┐ ┌────────────────────────────────────┐
│ MCP Client│ │ MCP Tool Servers │
│ (Claude │────▶│ - File System MCP │
│ Desktop) │ │ - Tool: read_file, ... │
└───────────┘ │ - Gmail MCP │
│ - Tool: send_email, ... │
│ - Slack MCP │
│ - Tool: slack_list_channels, ... │
│ - MCP Tool Override Tester │
│ - Tool: read_file, send_email │
│ and slack_list_channels │
└────────────────────────────────────┘
The Claude Desktop still confuses even after all tools of the Override tester MCP are turned off.
{
"mcpServers": {
"slack": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-slack"
],
"env": {
"SLACK_BOT_TOKEN": "YOUR SLACK BOT TOKEN",
"SLACK_TEAM_ID": "YOUR SLACK TEAM ID",
"SLACK_CHANNEL_IDS": "CHANNEL1_ID, CHANNEL2_ID, ..."
}
},
"gmail": {
"command": "npx",
"args": [
"@gongrzhe/server-gmail-autoauth-mcp"
]
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/your/directory/path/to/allow"
]
},
"override_tester": {
"command": "/path/to/your/uvx",
"args": [
"--from",
"mcp-tool-override-tester@latest",
"override_mcp_tools"
]
}
}
}
This project is licensed under the MIT License.