Stop Searching. Start Trusting.

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

Browse DirectoryWhy Us?

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
Low Cost
chew-z icon

TimeMCP

by chew-z

Sec9

Provides a Model Control Protocol (MCP) server for current time retrieval and timezone conversions.

Setup Requirements

  • ⚠️Requires a Go (GoLang) development environment to build and run from source.
  • ⚠️If HTTP transport with authentication is enabled, the `TIME_AUTH_SECRET_KEY` environment variable must be set (recommended >=32 characters).
  • ⚠️Relies on the system's IANA timezone database for timezone operations.
Verified SafeView Analysis
The server demonstrates strong security practices for network exposure, including explicit CORS configuration with secure defaults (disabled by default, allowlist required, wildcard '*' rejected with auth enabled) and robust JWT authentication with checks for secret key presence/length and proper token validation. No 'eval' or similar dangerous patterns are present. `TIME_AUTH_SECRET_KEY` is loaded from environment variables. Overall, the project prioritizes security in its design.
Updated: 2025-11-19GitHub→
0
0
Low Cost
Digital-Defiance icon

mcp-core

by Digital-Defiance

Sec8

Provides shared infrastructure for building AI capability servers that expose a set of tools.

Setup Requirements

  • ⚠️Requires Node.js environment
  • ⚠️Requires TypeScript compilation (`yarn build`)
  • ⚠️Primarily uses 'yarn' as package manager (though npm/pnpm might work)
Verified SafeView Analysis
The server-base library itself does not contain obvious critical vulnerabilities like 'eval' or hardcoded secrets. It communicates over standard I/O (StdioServerTransport), reducing direct network attack surface. Tool input validation is facilitated by Zod schemas, but the ultimate security depends on how tool handlers are implemented by the consumer, as 'request.params.arguments' is passed directly to the handler.
Updated: 2026-01-17GitHub→
0
0
Medium Cost
8resd8 icon

Dev-Assistant

by 8resd8

Sec7

An AI-powered local server that allows an LLM to query a local MySQL database and analyze local server log files via the Model Context Protocol (MCP).

Setup Requirements

  • ⚠️Requires a running local MySQL instance.
  • ⚠️Requires configuration of database connection details in `application.properties`.
  • ⚠️The `server.log` file must be present in the application's working directory for log analysis to function.
  • ⚠️Requires an LLM client (e.g., Claude Desktop) that supports Model Context Protocol (MCP) and needs to be configured to connect to this server.
Verified SafeView Analysis
The server restricts database queries to only 'SELECT' statements, which is a strong measure against data manipulation. It uses local Stdio for communication, preventing external network exposure. However, the `DatabaseMcpService` directly executes LLM-generated SQL queries via `jdbcTemplate.queryForList(sql)` without parameterized statements, making it potentially vulnerable to SQL injection if an LLM crafts a malicious 'SELECT' query (e.g., to exfiltrate data or cause performance issues). Log file analysis is limited to 50 lines, reducing potential resource exhaustion.
Updated: 2025-12-02GitHub→
0
0
Low Cost
BlockRunAI icon

awesome-devops-mcp

by BlockRunAI

Sec10

A curated list of Model Context Protocol (MCP) servers for DevOps, cloud infrastructure, and platform engineering, enabling AI agents to interact with various tools and services.

Verified SafeView Analysis
The provided source code consists of markdown documentation (README.md and CONTRIBUTING.md) and does not contain executable code. Therefore, there are no direct security risks such as 'eval', obfuscation, network risks, hardcoded secrets, or malicious patterns within this repository's files. The security of any *listed* MCP servers would need to be assessed independently.
Updated: 2026-01-18GitHub→
0
0
Medium Cost
dennisonbertram icon

mcp-etherscan-server

by dennisonbertram

Sec9

Provides a multi-chain Etherscan-based interface for fetching Ethereum blockchain data, including balances, transactions, token transfers, contract details, and network statistics across 70+ networks.

Setup Requirements

  • ⚠️Requires an Etherscan API Key (free tier with rate limits, paid for higher usage).
  • ⚠️Requires Node.js >= 18.
  • ⚠️Needs an '.env' file configured with ETHERSCAN_API_KEY in the root directory.
Verified SafeView Analysis
The server correctly handles sensitive API keys via environment variables (ETHERSCAN_API_KEY is explicitly required and checked). It uses reputable external APIs (Etherscan, eth.llamarpc.com for ENS) and robust URL building with parameter encoding. No 'eval' or obvious malicious code patterns were found. Dependency usage is for standard utilities and cryptographic operations. The `parseApiResponse` function includes basic structural and status validation, reducing the risk of malformed API responses causing unexpected behavior.
Updated: 2025-12-03GitHub→
0
0
High Cost
GlacierEQ icon
Sec8

A sophisticated, AI-driven framework for multi-engine browser automation, web scraping, and cognitive task execution on the web, capable of complex problem-solving and error recovery.

Setup Requirements

  • ⚠️Requires OpenAI API Key or similar for LLM provider (Paid Service)
  • ⚠️Requires browser drivers to be installed (e.g., playwright install)
  • ⚠️Python 3.11+ required
  • ⚠️Optional: Redis or another memory backend for cognitive persistence
Verified SafeView Analysis
The framework's architecture outlines security best practices like not logging credentials, rotating proxies, and encrypting cookies. However, direct code for handling LLM API keys or external service credentials is not shown, which could be a risk if not implemented securely (e.g., hardcoded keys). Reliance on external LLMs and CAPTCHA services introduces data privacy and security considerations that depend on third-party service policies and the implementation details of data handling. No explicit 'eval' or malicious patterns are visible in the truncated source.
Updated: 2025-11-23GitHub→
0
0
Low Cost
Sec8

Enables AI assistants like GitHub Copilot to execute Power Automate Desktop flows and automate Windows UI operations.

Setup Requirements

  • ⚠️Requires Windows 10 or Windows 11.
  • ⚠️Requires Power Automate Desktop (PAD) to be installed and running, with the Console Host initialized at least once.
  • ⚠️For development, .NET 8.0 SDK is required; for release, .NET 8.0 Runtime is implicitly needed (often bundled with PAD).
Verified SafeView Analysis
The project demonstrates a strong focus on security, providing a detailed SECURITY.md that outlines input validation for flow names, window titles, and keystroke sequences, and enforcing code analysis rules. Operations are local-only and run within the current user's context, mitigating remote attack vectors. However, it relies on `child_process.exec` for system commands (`tasklist`, `powershell`), which are potential injection points if validation fails or is bypassed. Furthermore, Power Automate Desktop flows execute with full PAD permissions and are not sandboxed by the MCP server, posing a risk if a malicious flow is executed. Users must validate AI requests and manage PAD flows carefully, as highlighted in the 'Known Security Considerations'.
Updated: 2025-11-25GitHub→
0
0
Medium Cost
Supplyline icon

plytix-mcp

by Supplyline

Sec9

Provides AI assistants with live access to Plytix PIM data via the Model Context Protocol (MCP) for searching, looking up, and retrieving product information.

Setup Requirements

  • ⚠️Requires Node.js 18+ (20+ recommended).
  • ⚠️Requires a Plytix PIM account with API access (API Key and Password).
Verified SafeView Analysis
The server demonstrates strong security practices. It avoids hardcoded secrets by relying on environment variables or request headers for API credentials. Automatic token refresh and rate limit handling with exponential backoff are implemented for robust API interaction. Input validation for tool arguments is performed using `zod`, which helps prevent common injection vulnerabilities. Explicit CORS configuration restricts access to allowed origins. There is no usage of `eval` or similar dangerous functions found in the provided source code, and the stateless nature inherently reduces some persistence-related risks.
Updated: 2026-01-19GitHub→
0
0
Low Cost
FractalizeR icon

mcp_servers

by FractalizeR

Sec9

Facilitate AI agents to interact with Yandex Wiki API for documentation, knowledge management, and content automation, allowing programmatic creation, modification, and retrieval of wiki pages and dynamic grids.

Setup Requirements

  • ⚠️Requires Node.js version 22.0.0 or higher.
  • ⚠️Requires an OAuth token for Yandex Wiki API, set via the `YANDEX_WIKI_TOKEN` environment variable.
  • ⚠️Requires an organization ID, set via either `YANDEX_ORG_ID` (for Yandex 360) or `YANDEX_CLOUD_ORG_ID` (for Yandex Cloud Organization) environment variable. Only one of these should be provided.
Verified SafeView Analysis
The project demonstrates strong security awareness: explicit handling of sensitive OAuth tokens (not saved to disk), active auditing with `gitleaks` for secrets and `Socket.dev` for supply-chain risks. The `ResponseFieldFilter` is a critical feature to prevent accidental data exposure to LLMs, reducing prompt injection and data leakage risks. File write operations (e.g., for downloading attachments) are present, which could be a risk if `saveToPath` is not properly sanitized/restricted by the client or tool invocation. However, the core framework is robust with `axios` and built-in retry mechanisms.
Updated: 2026-01-01GitHub→
0
0
Medium Cost
sj0405-lee icon

my-mcp-server

by sj0405-lee

Sec8

A TypeScript boilerplate server implementing the Model Context Protocol (MCP) SDK, offering various tools like greeting, calculation, time, AI image generation, and a code review prompt, along with a server information resource.

Setup Requirements

  • ⚠️Requires a Hugging Face API token (HF_TOKEN) for the 'generate-image' tool.
  • ⚠️Requires Node.js (version 18 or higher recommended by dependencies).
  • ⚠️Requires `npm install` and `npm run build` to compile TypeScript to JavaScript before execution.
Verified SafeView Analysis
The server uses environment variables or a configuration object to manage sensitive API tokens (e.g., Hugging Face API token), which is a good practice. There are no clear instances of 'eval', obfuscation, or other overtly malicious patterns. Network risks are confined to calls to legitimate third-party AI services. The code review prompt, while useful, sends user-provided code to an LLM, which implies trust in the LLM provider and handling of potentially sensitive code.
Updated: 2025-11-27GitHub→
0
0
Medium Cost
Sharadendu icon

MCPFileIO

by Sharadendu

Sec2

A comprehensive Model Context Protocol (MCP) server designed for AI agents to perform file operations, compiler tasks, execute code, monitor logs, and manage processes on the host system.

Setup Requirements

  • ⚠️Requires .NET 9.0 or later
  • ⚠️Some tools are Windows-specific, limiting cross-platform functionality
Review RequiredView Analysis
The server provides powerful capabilities to AI agents, including reading/writing/deleting files, executing arbitrary C# code snippets and other executables, compiling projects, and managing processes. If an AI agent's input is compromised or maliciously crafted, these tools can be abused for arbitrary code execution, data exfiltration, system damage, or privilege escalation. There is no mention of sandboxing or strict input validation in the provided documentation, making it inherently risky to run in an environment exposed to untrusted input. The ability to run 'dotnet applications, executables, and C# code snippets' is a critical risk.
Updated: 2026-01-19GitHub→
0
0
Low Cost
pcjx8 icon
Sec5

Production-ready Model Context Protocol (MCP) server for Electronic Health Records with OAuth 2.0 authentication.

Setup Requirements

  • ⚠️Requires `oauth_clients_credentials.json` file to be present in the working directory for testing and deployment, containing plaintext client secrets. This file must be kept secure and never committed to version control.
  • ⚠️The default `JWT_SECRET_KEY` must be changed in the `.env` file for production deployments. Failure to do so poses a critical security risk.
  • ⚠️The server includes an authentication bypass for convenience if no access token is provided, which must be removed or properly secured for production use in an EHR context.
  • ⚠️CORS is configured with `allow_origins=['*']` in the SSE server, requiring explicit tightening for production deployments.
Review RequiredView Analysis
The system implements OAuth 2.0 with JWT tokens and SHA-256 hashed secrets, along with role-based and scope-based access control, which are good practices. However, it has several critical security vulnerabilities and anti-patterns: 1) A default `JWT_SECRET_KEY` (`'your-secret-key-change-in-production'`) is used if `JWT_SECRET_KEY` is not set via environment variables. This is a major security risk for production. 2) The `server.py` explicitly includes a bypass for token validation (`'No access token provided, bypassing authentication for demo/testing'`) if no `access_token` is present, which is highly inappropriate for an EHR system in production. 3) The `sse_server.py` uses `CORS(allow_origins=['*'])`, which opens up the API to cross-origin attacks. 4) The `oauth_clients_credentials.json` file is expected to exist in the working directory (and is used by test scripts) containing plaintext client secrets, a significant credential management risk. 5) Sensitive data (request bodies, headers) are logged by a middleware in `sse_server.py`, potentially exposing PII or secrets. These issues make the system unsafe for a production EHR environment without substantial hardening.
Updated: 2025-12-04GitHub→
PreviousPage 703 of 760Next