Stop Searching. Start Trusting.

The curated directory of MCP servers, vetted for security, efficiency, and quality.

Tired of the MCP "Marketplace" Chaos?

We built MCPScout.ai to solve the ecosystems biggest pain points.

No Insecure Dumps

We manually analyze every server for basic security flaws.

Easy Setup

Our gotcha notes warn you about complex setups.

Avoid "Token Hogs"

We estimate token costs for cost-effective agents.

Products, Not Demos

We filter out "Hello World" demos.

CATEGORIES:
SORT:

Vetted Servers(9120)

0
0
Medium Cost
Ahmedvision icon

zen-mcp-server

by Ahmedvision

Sec9

A Multi-Model Communication Protocol (MCP) server designed for orchestrating and enhancing various AI-powered software development and analysis tools and workflows.

Setup Requirements

  • ⚠️Requires Docker to be installed for deployment.
  • ⚠️At least one API key (e.g., GEMINI_API_KEY, OPENAI_API_KEY, or XAI_API_KEY) is mandatory, typically linking to paid AI services.
  • ⚠️Using certain advanced models (e.g., O3-Pro, as highlighted in `test_o3_pro_expensive.py`) can incur extremely high token costs.
Verified SafeView Analysis
The server demonstrates strong inherent security practices: it runs as a non-root user ('zenuser'), utilizes a read-only filesystem with tmpfs for temporary files, and operates solely via standard I/O (stdio) without exposing any network ports. Secrets are managed securely through environment variables. The codebase includes extensive tests for detecting various security vulnerabilities in *simulated* code, indicating a robust focus on security for the AI's output rather than the server's own vulnerabilities.
Updated: 2026-01-19GitHub→
0
0
Medium Cost
abedmreyan icon

DEV-MCP-Server

by abedmreyan

Sec3

The server enables AI agents to manage software development lifecycle across multiple platforms like GitHub, Netlify, Supabase, Azure, and Google Workspace, effectively setting up a semi-autonomous dev team.

Setup Requirements

  • ⚠️Requires API keys/credentials for up to 10 different cloud and AI services, demanding extensive manual setup.
  • ⚠️Google Sheets and Tasks require specific Google Cloud API enablement and sharing a Google Sheet with a service account email.
  • ⚠️AI integrations (Perplexity, Gemini) will incur usage-based costs based on token consumption.
Review RequiredView Analysis
The direct execution of raw SQL queries provided by the AI agent through the `supabase_query`, `azure_query_postgresql`, and `azure_query_mysql` tools poses a severe SQL injection vulnerability. Similarly, `supabase_create_table` directly uses an input schema string, allowing arbitrary schema modification. Any malicious or unverified input from the AI could lead to unauthorized data access, modification, deletion, or schema manipulation on the integrated databases. These integrations lack explicit input sanitization, which is critical given the extensive access granted to an AI agent across numerous powerful platforms.
Updated: 2025-11-29GitHub→
0
0
Low Cost
Sec3

A minimal Model Context Protocol (MCP) server that acts as a connector to an AI LLM proxy, designed to forward chat requests for Data Loss Prevention (DLP) and policy enforcement.

Setup Requirements

  • ⚠️Requires an external AI LLM proxy running and accessible at the configured LLM_PROXY_URL.
  • ⚠️This server is an MCP server, meaning it requires an MCP host (e.g., Claude Desktop style) to connect to and invoke its 'secure_llm_chat' tool.
  • ⚠️The hardcoded 'Bearer demo-internal-key' is a security risk and should be replaced with a secure, configurable mechanism for production use.
Review RequiredView Analysis
The server includes a hardcoded secret `Authorization: "Bearer demo-internal-key"` in `src/proxyClient.ts`. This is a critical security vulnerability as it allows anyone with access to the code to authenticate with the LLM proxy, potentially bypassing intended access controls. The server's core function relies on an external proxy for all security enforcement, so its own security posture is limited to its role as a connector.
Updated: 2025-12-02GitHub→
0
0
Medium Cost
samjjmmmm icon

n8n-hubspot-mcp

by samjjmmmm

Sec8

Facilitates an AI agent in fetching and summarizing HubSpot deal data, including engagements, by calling an n8n webhook.

Setup Requirements

  • ⚠️Requires an n8n instance with a workflow configured to fetch HubSpot deal and engagement data. The specific n8n webhook URL is hardcoded in `server.js` and needs to be updated in the source code if deploying to a different n8n instance.
  • ⚠️Requires Node.js to run.
Verified SafeView Analysis
The `N8N_WEBHOOK_URL` is hardcoded in `server.js`, which is a configuration management issue and reduces deployment flexibility. It should ideally be an environment variable. The `/sse` endpoint uses `Access-Control-Allow-Origin: *`, which is broad but acceptable for publicly exposing tool definitions. The server acts as a proxy, forwarding `dealId` to an n8n webhook; potential security risks related to data handling or authentication for HubSpot data depend entirely on the security and implementation of the n8n workflow. No `eval` or direct malicious patterns found in this server's code.
Updated: 2025-11-20GitHub→
0
0
Medium Cost

Provides backend API and control plane functionalities, potentially managing other services or devices.

Setup Requirements

  • ⚠️Likely requires a specific runtime environment (e.g., Node.js, Python, Java) to be installed.
  • ⚠️May require a database (e.g., PostgreSQL, MongoDB, MySQL) for data persistence.
  • ⚠️Specific port configurations might be necessary for network access.
Review RequiredView Analysis
A critical security audit cannot be performed as no source code was provided for analysis. Therefore, it's impossible to check for common risks like 'eval' usage, obfuscation, network vulnerabilities, hardcoded secrets, or malicious patterns. Running this server without a proper code review is highly risky.
Updated: 2025-11-27GitHub→
0
0
Low Cost
Sec8

This repository serves as a template to bootstrap a new interactive educational Labspace environment.

Setup Requirements

  • ⚠️Requires Docker to be installed and running locally.
  • ⚠️Requires GitHub Action Secrets (DOCKERHUB_USERNAME, DOCKERHUB_TOKEN) for publishing/deployment.
  • ⚠️Requires manual renaming of the `.github/workflows/publish-labspace.yaml.temp` file and updating `DOCKERHUB_REPO` within it.
Verified SafeView Analysis
The project relies on an external Docker OCI image (`oci://dockersamples/labspace-content-dev`) for its core development environment, the contents of which are not auditable from the provided source. Assuming the `dockersamples` source is trusted, the provided configuration and markdown content do not contain immediate high-severity security risks. Hardcoded secrets are not present; GitHub Actions secrets are properly specified for deployment.
Updated: 2025-11-21GitHub→
0
0
High Cost
Sec8

Automating cryptocurrency trading operations, market data retrieval, technical analysis, and opportunity scanning by integrating with Claude Desktop.

Setup Requirements

  • ⚠️Requires API keys and secrets for a cryptocurrency exchange (e.g., MEXC_API_KEY, MEXC_SECRET) to operate in 'live' mode.
  • ⚠️Requires Node.js (>=18.0.0) and npm/npx for installation and execution.
  • ⚠️Designed to run as an MCP server for Claude Desktop, not as a standalone application, requiring configuration within Claude Desktop.
Verified SafeView Analysis
The server uses `ccxt` for exchange interactions and `Decimal.js` for precise financial calculations, which are good practices. API keys and secrets are correctly sourced from environment variables, not hardcoded. Communication with Claude Desktop occurs via standard I/O (stdin/stdout), limiting direct network exposure for the server itself. Rate limiting is implemented for exchange API calls. There is no usage of `eval` or obvious code obfuscation. The primary security consideration for users is the inherent risk of live trading with real funds, for which a 'demo' mode is provided and strongly recommended.
Updated: 2025-12-07GitHub→
0
0
Medium Cost
tarekbadrsh icon

git-commit-helper

by tarekbadrsh

Sec10

This MCP server helps Claude generate professional git commit messages by providing context from the local git repository's status, staged changes, all changes, and commit history.

Setup Requirements

  • ⚠️Requires Rust toolchain installed for building from source.
  • ⚠️Requires Git to be installed and accessible in the system's PATH.
  • ⚠️The absolute path to the compiled binary must be precisely configured in Claude Desktop's `claude_desktop_config.json`.
  • ⚠️Claude Desktop must be completely quit and restarted after configuration changes.
  • ⚠️macOS Gatekeeper may block the binary (requires `xattr -d com.apple.quarantine` to fix).
Verified SafeView Analysis
The server executes `git` commands locally via `std::process::Command`. All command arguments are strictly controlled within the source code (e.g., `["status"]`, `["diff", "--cached"]`), and the `repo_path` parameter is used to set the working directory for `git`, preventing arbitrary command injection. The `git_log` limit is clamped to 50 commits. There is no network exposure as communication occurs over stdio, no dynamic code execution (`eval`), and no hardcoded secrets were found. Robust error handling is implemented for `git` command failures and cases where `git` is not installed.
Updated: 2025-11-22GitHub→
0
0
Low Cost
Sec8

Provides AI tools for managing TODO list items through a Spring AI Multi-Modal Chat Protocol (MCP) server.

Setup Requirements

  • ⚠️Requires Java Development Kit (JDK 17+ recommended for Spring Boot 3).
  • ⚠️Designed to run as a Spring AI MCP server, typically interacting with a larger AI application via standard I/O.
Verified SafeView Analysis
Standard Spring Boot application using JPA and an in-memory H2 database. No 'eval', obfuscation, or malicious patterns found. The H2 database credentials ('sa'/empty password) are hardcoded but are for an in-memory development database and do not pose a significant risk in this context. As a server exposing tools, proper access control and input validation (beyond what Spring AI's tool parameters might implicitly provide) would be necessary in a production environment, but are not inherently lacking in the provided snippet.
Updated: 2025-11-27GitHub→
0
0
Medium Cost

Enables AI assistants to interact with the Betfair Exchange betting platform for market intelligence and account information.

Setup Requirements

  • ⚠️Requires a Betfair account and an Application Key, which can be a paid 'Live' key for real-time market data (£299).
  • ⚠️Certificate-based authentication, recommended for production, requires manual generation and secure configuration of SSL certificates.
  • ⚠️Access to market data is geo-blocked for German IP addresses, potentially requiring hosting outside of Germany (e.g., a home PC setup).
Verified SafeView Analysis
Secrets (Betfair credentials) are correctly loaded from environment variables. Certificate private key file permissions are explicitly checked (chmod 600) for enhanced security. The server is designed for read-only access, significantly mitigating risks associated with automated betting.
Updated: 2025-11-21GitHub→
0
0
High Cost
Sec10

Provides data protection regulations and compliance context to LLMs for code review and application development.

Setup Requirements

  • ⚠️Requires Python 3.10 or higher.
  • ⚠️Manual creation and configuration of a '.env' file to specify REGULATION_DATA_DIR is critical.
  • ⚠️Requires running 'python setup_data.py' or manually copying sample data to the configured data directory.
Verified SafeView Analysis
The server operates locally, loading data from a user-configured directory. It does not perform network requests or use risky functions like 'eval'. Interaction is via stdio, making it safe to run in an isolated environment.
Updated: 2025-11-16GitHub→
0
0
Low Cost
samreensami icon

mcp_server

by samreensami

Sec1

A simple bank system API that allows users to create accounts, authenticate, deposit/transfer funds, and view transaction history, along with unprotected administrative endpoints to view all accounts and transactions.

Setup Requirements

  • ⚠️Requires Python dependencies: fastapi, uvicorn, sqlalchemy, pydantic, bcrypt, requests, colorama. These must be installed (e.g., `pip install -r requirements.txt` if a requirements file exists, or individually).
  • ⚠️The server (`main.py`) and CLI frontend (`cli_frontend.py`) are separate applications that need to be run concurrently for a full experience.
  • ⚠️A local SQLite database file `bank.db` will be created in the application's root directory.
Review RequiredView Analysis
Critical authorization bypass: All core financial operations (deposit, transfer, view balance, view transactions) and administrative endpoints (view all accounts, view all transactions) are exposed without any authentication or authorization. An attacker merely needs to know an `account_id` (which is returned upon initial login) to perform unauthorized transactions or view all sensitive data. No proper session management, JWT, or OAuth is implemented. The authentication endpoint also distinguishes between 'account not found' and 'invalid PIN', which aids in account enumeration. No rate limiting is present.
Updated: 2025-11-23GitHub→
PreviousPage 688 of 760Next