The inspection found no issues.
MCP GUARD / DOCS
What should you verify before connecting?
Identify the server, interpret the result, enforce its required controls, and review changes. Use MCP Guard evidence to make a deployment decision for your own environment.
Find an MCP serverAgent data schema
The three fixed evidence, setup, and control slots distinguish available, Pro required, and information not obtained. The free assessment carries the connection decision and required controls. A setup template requires an explicitly selected supported client environment, and substitution still requires a new exact match and control verification.
Read the public Agent schema JSON MCP REVIEW
Check a server before connecting
Check the publisher, inspection time, saved verdict, and required connection conditions in the public record. Pro can show detailed evidence such as detected permissions and external connections when verified content exists for that target.
If you give the request to an Agent, keep your token and password private. Approve a short-lived read grant only after checking its scopes. Free includes simplified results and one target handoff at a time.
Show the request
Use MCP Guard to review the risks of the MCP servers I use. Follow https://mcp-guard.org/agent-guide.md. Match the publisher, package, and endpoint. Summarize the saved status, inspection time, required controls, and missing evidence. If account access is needed, create a read-only request and give me only its approval URL. Do not ask for tokens or passwords. Report your findings before sending secrets or changing settings.
Four checks before connecting
- 1
Identify the server
Match the publisher, package, and endpoint as well as the name. Before sign-in, you can review the public diagnosis and connection conditions for one selected MCP.
- 2
Read the result and its limits
Check the public status, reasons, required controls, and missing evidence. Establish whether the artifact or configuration changed after the inspection.
- 3
Enforce required controls
Limit folders, credential scopes, and destinations at the specified OS, container, or provider boundary. Use harmless data to verify that out-of-scope operations are denied.
- 4
Review after changes
Package updates, ownership changes, new permissions, and new destinations can invalidate an earlier decision. Retain evidence for the artifact and configuration you actually deploy.
Inspection scope and counting units
Inspections review declared capabilities, provenance and implementation, and observations obtained in an isolated environment. Applicable procedures and available evidence depend on the target.
Complete procedure catalog
25
Procedures selected according to the target
Local MCP baseline
22
Baseline for local targets with an artifact and launch configuration
Public HTTPS baseline
13
Baseline for publicly reachable remote endpoints
18 operation categories, 4 dependency-review categories, and 17 consistency-review categories organize the observations.
A result is different from inspection progress
How to read inspection results
PASS, WARN, RESTRICT, and BLOCK are ordered by how strictly use must be controlled. NEED_REVIEW is separate: the available evidence was insufficient to determine safety.
The inspection found items that require caution.
The inspection found high-risk behavior, permissions, or vulnerabilities. Use only after every required technical control is enforced and verified.
The inspection met high-impact prohibition criteria. Do not use this server.
Separate from the risk scale
NEED_REVIEWUnable to determine
The available evidence was insufficient, so safety could not be determined.
In progress, failed, and held describe the inspection process. A failure does not prove safety or clear a previously stored RESTRICT or BLOCK result. Review the error and missing evidence before reassessing under the required conditions.
Vulnerabilities, powerful permissions, and missing evidenceWhat Free and Pro include
| Feature | Free | Pro |
|---|---|---|
| Public diagnosis and controls for one selected MCP | Available before sign-in | Included |
| Simplified all-server search and filters | After sign-in | Included |
| Agent handoff copy for one selected MCP | After sign-in | Included |
| Detailed evidence, permissions, and connections | Not included | Included |
| Registry row copy and bulk CSV/JSON export | Not included | Included |
| Update differences and drift review | Not included | Included |
Statuses and required actions have the same meaning across plans. Setup and control instructions can be read only when verified content exists for the matching target and release. Legacy Local Pro Agent distribution and proxy connections are not currently provided.
Pricing and access