# How to vet an MCP server before use

URL: https://mcpservercybersecurity.com/guides/how-to-vet-an-mcp-server-before-use/
Updated: 2026-11-16

Vet an MCP server before it runs by confirming the publisher, reading the source and startup command, inspecting every tool description and schema, checking requested scopes and pinning what you approved. Stop on look-alike package names, commands that touch sensitive paths, or descriptions that address the model. Sources were read on 16 Nov 2026.

## What do you check in a server before it runs?

Check who published it, what it executes at startup, what each tool claims to do and which credentials it asks for. OWASP's supply chain guidance is to install servers only from trusted, verified sources, review source code and tool definitions first, verify package integrity with checksums or signing, and scan dependencies for known vulnerabilities.

The MCP specification adds that a client must show the exact startup command, untruncated, and get explicit approval before a one-click local server runs. Apply the same rule to config files you receive from a teammate or a repository.

Do the check on a disposable container or a clean machine, never on a laptop that holds production credentials. A server that is only being reviewed should not be able to read anything real.

- Publisher identity and the exact package name.
- Source code for command construction, file access and outbound requests.
- The startup command with every argument.
- Every tool name, description and input schema.
- Requested OAuth scopes and where tokens are stored.
- Dependencies and their known advisories.

Sources: [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html); [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices).

## Which signals show a server is unsafe?

Unsafe servers show up as look-alike names, risky startup commands and descriptions written for the model. OWASP calls typosquatting a common attack, with a package name one character from a popular one as the example, and says tool descriptions, parameter names and return schemas can all carry hidden instructions.

The specification lists startup patterns a client should highlight: commands with sudo, deletion of files, network operations, or file access outside expected directories, and anything that reaches the home directory, SSH keys or system directories. A server that changes its tool definitions after approval, often called a rug pull, is a third signal, which is why OWASP asks for monitoring of tool descriptions after installation.

Sources: [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html); [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices).

## How do you verify who published a server?

Check the publisher against a source the server's author does not control. The MCP Registry requires publishers to prove ownership of a namespace through GitHub, DNS or HTTP challenges, which tells you who owns a name but nothing about the code.

Some tools add publisher signals. Backslash Security's free MCP Server Security Hub, published 2025-06-16, shows GitHub publisher verification and an attack vector per server, and Snyk documents trust signals in its MCP Risk Score: popularity, official first-party status, URL reputation and maintainer identity. These are vendor statements about their own services.

Sources: [MCP Registry: About](https://modelcontextprotocol.io/registry/about); [Backslash Security: MCP Server Security Hub](https://www.backslash.security/blog/mcp-server-security-hub); [Snyk documentation: Agent Supply Chain Security](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/agent-supply-chain-security.md).

## What do automated scanners add to a manual review?

Scanners add speed and consistency on tool descriptions, prompts and packages, and they do not replace reading the code. Cisco's open-source MCP Scanner combines YARA rules and LLM-based analysis and scans a server's tools, prompts, resources and instructions, and Snyk says a local stdio server is matched against its catalog and assessed from its signature without starting it.

Use scanner output as a prompt for review. OWASP warns that filters for instruction-like text cannot establish that the remaining text is safe.

Sources: [Cisco AI Defense MCP Scanner repository](https://github.com/cisco-ai-defense/mcp-scanner); [Snyk documentation: Agent Supply Chain Security](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/agent-supply-chain-security.md); [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html).

## How do you decide to approve, restrict or reject?

Approve a server only for the tools and scopes you reviewed, restrict the rest, and reject on any unresolved signal. Cursor's allowlist can limit which tools of an approved server run automatically, and Pillar Security says per-server tool allow-lists run in Monitor or Block mode, so a partial approval is possible in practice.

Record the decision with the version or hash reviewed, then re-review on any change. OWASP asks clients to re-prompt for consent when tool definitions change.

Sources: [Cursor documentation: Model Context Protocol](https://cursor.com/docs/context/mcp); [Pillar Security: agentic endpoint](https://www.pillar.security/platform/agentic-endpoint); [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html).

## Sources

- [OWASP MCP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/MCP_Security_Cheat_Sheet.html) (cheatsheetseries.owasp.org), read 2026-11-16
- [MCP specification: Security Best Practices (2025-11-25)](https://modelcontextprotocol.io/specification/2025-11-25/basic/security_best_practices) (modelcontextprotocol.io), read 2026-11-16
- [MCP Registry: About](https://modelcontextprotocol.io/registry/about) (modelcontextprotocol.io), read 2026-11-16
- [Cisco AI Defense MCP Scanner repository](https://github.com/cisco-ai-defense/mcp-scanner) (github.com), read 2026-11-16
- [Snyk documentation: Agent Supply Chain Security](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/agent-supply-chain-security.md) (docs.snyk.io), read 2026-11-16
- [Backslash Security: MCP Server Security Hub](https://www.backslash.security/blog/mcp-server-security-hub) (backslash.security), read 2026-11-16
- [Cursor documentation: Model Context Protocol](https://cursor.com/docs/context/mcp) (cursor.com), read 2026-11-16
- [Pillar Security: agentic endpoint](https://www.pillar.security/platform/agentic-endpoint) (pillar.security), read 2026-11-16

## Related pages

- [How to Review an MCP Server for Security: Code and Tools](/guides/how-to-review-an-mcp-server-security/)
- [Building an Approved MCP Server Catalog for Your Company](/guides/building-an-approved-mcp-server-catalog/)
- [Typosquatted server (glossary)](/glossary/typosquatted-server/)
- [Server pinning (glossary)](/glossary/server-pinning/)
- [All guides](/guides/)
- [MCP Audit Logging: What to Record and How Long to Keep It](/guides/mcp-audit-logging-what-to-record/)
- [The ranking](/ranking/)
- [Glossary](/glossary/)
