Orcho MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Orcho MCP Server assess_risk: Write a script that deletes all files in the /tmp directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Orcho MCP Server for Cursor
Risk assessment for AI coding prompts - Automatically analyze your coding requests for security and safety risks before execution.
š Quick Install
Click this link to automatically install in Cursor:
cursor://anysphere.cursor-deeplink/mcp/install?name=orcho&config=eyJuYW1lIjoib3JjaG8iLCJ0eXBlIjoic3RkaW8iLCJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBvcmNob19yaXNrL21jcC1zZXJ2ZXIiXSwiZW52Ijp7Ik9SQ0hPX0FQSV9LRVkiOiJ0ZXN0X2tleV9vcmNob18xMjM0NSJ9fQ==How to use:
Copy the link above
Paste it into your browser's address bar and press Enter
Cursor will open and automatically configure the MCP server
Replace the test API key with your real key (see API Configuration)
Restart Cursor to activate
Replace the test API key with your real key (see API Configuration)
Restart Cursor to activate the MCP server
Related MCP server: aigently
What is Orcho??
Orcho analyzes your coding prompts in real-time to identify potential security risks, dangerous operations, and safety concerns before code is generated or executed.
Features
š Real-time Risk Assessment - Analyze prompts using Orcho's risk analysis API
š Context-Aware - Automatically includes file context for accurate blast radius and complexity analysis
š”ļø Security First - Identifies high-risk prompts before execution
š Seamless Integration - Works natively with Cursor's Model Context Protocol
Installation
Option 1: One-Click Install (Recommended)
Copy and paste this link into your browser:
cursor://anysphere.cursor-deeplink/mcp/install?name=orcho&config=eyJuYW1lIjoib3JjaG8iLCJ0eXBlIjoic3RkaW8iLCJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBvcmNob19yaXNrL21jcC1zZXJ2ZXIiXSwiZW52Ijp7Ik9SQ0hPX0FQSV9LRVkiOiJ0ZXN0X2tleV9vcmNob18xMjM0NSJ9fQ==This automatically:
ā Configures the MCP server in Cursor
ā Sets up auto-installation via npx
ā ļø Next step: Replace the test API key with your real key (see below)
ā ļø Then: Restart Cursor
Option 2: Manual Installation
Install the package:
npm install -g @orcho_risk/mcp-serverConfigure Cursor:
Create or edit
~/.cursor/mcp.json(Windows:C:\Users\<YourUsername>\.cursor\mcp.json):{ "mcpServers": { "orcho": { "command": "npx", "args": ["-y", "@orcho_risk/mcp-server"], "env": { "ORCHO_API_KEY": "your-api-key-here" } } } }Restart Cursor completely (quit and reopen)
API Configuration
Get Your API Key
Sign up at app.orcho.ai
Navigate to API Settings (Dashboard ā API Keys)
Create or copy your API key
Update your
mcp.jsonfile:Location:
~/.cursor/mcp.json(orC:\Users\<YourUsername>\.cursor\mcp.jsonon Windows)Replace
test_key_orcho_12345with your actual API key
Test API Key
For initial testing, you can use:
test_key_orcho_12345Note: The test key has limited functionality and rate limits. Get your own API key from app.orcho.ai for production use.
Security Best Practices
ā Store API keys only in
~/.cursor/mcp.json(not in your project)ā Never commit API keys to version control
ā Rotate keys immediately if accidentally exposed
Usage
Manual Assessment
In Cursor chat, type:
@orcho assess_risk: Your prompt hereAutomatic Assessment (Recommended)
Enable automatic risk assessment for all prompts by adding a Cursor rule to your project.
Option 1: Project Rules (Modern - Recommended)
Copy the rule file to your project:
# Create .cursor/rules directory
mkdir -p .cursor/rules
# Copy the rule file
cp node_modules/@orcho_risk/mcp-server/.cursor/rules/orcho-risk-assessment.mdc .cursor/rules/Or manually copy from:
node_modules/@orcho_risk/mcp-server/.cursor/rules/orcho-risk-assessment.mdcOption 2: Legacy .cursorrules File
Copy the example rules file:
cp node_modules/@orcho_risk/mcp-server/.cursorrules.example .cursorrulesNote: Project Rules (Option 1) are the modern approach and support more features.
How It Works
Context-Aware Assessment
Orcho automatically gathers context when available:
Current File: Detects the file open in your editor
Other Files: Analyzes which files will be modified by the prompt
Dependency Graph: Optional project dependency information
Blast Radius: Calculates impact scope of changes
Example
User: "Delete all user data from the database"
ā Cursor calls: @orcho assess_risk with context
ā Risk: HIGH (score: 95)
ā Cursor warns: "ā ļø HIGH RISK: This could cause data loss. Proceed?"Tool Parameters
task(required): The prompt to assesscurrent_file(recommended): Path to currently open fileother_files(recommended): Array of files that will be modifieddependency_graph(optional): Project dependency graphweights(optional): Custom risk calculation weightsaiignore_file(optional): Path to .aiignore file
Troubleshooting
MCP Server Not Loading
Check
mcp.jsonlocation:Mac/Linux:
~/.cursor/mcp.jsonWindows:
C:\Users\<YourUsername>\.cursor\mcp.json
Verify Node.js is installed:
node --version # Requires v18+Check Cursor Developer Tools:
Help ā Toggle Developer Tools
Look for MCP-related errors in Console
API Errors
Invalid API Key: Verify the key is correct in
mcp.jsonRate Limits: Check your account quota at app.orcho.ai
No API Key: The server will use the test key by default (limited functionality)
Still Having Issues?
Check that Cursor is fully restarted (quit and reopen)
Verify your API key is valid at app.orcho.ai
Ensure you have internet connectivity
License
MIT
Support
For issues and questions:
GitHub Issues: [Your Repo URL]
Orcho Support: [Support URL]
Available Tools
1 toolassess_riskA
Assess the risk level of your coding prompt using Orcho risk analysis API. CRITICAL: You (Cursor AI) have access to the editor state - ALWAYS include context when available: 1) Pass the currently open/active file path as current_file (you can see this in the editor tabs), 2) Analyze the user prompt to determine which files will be modified and pass them as other_files array. Without context, only basic risk assessment is available. With context, you get blast radius and complexity analysis.
Inputs: task (required), current_file, other_files, dependency_graph, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool 'assess_risk' has a single, clearly defined purpose: to evaluate the risk level of coding prompts using the Orcho API. This eliminates any ambiguity in tool selection.
The naming follows a consistent verb_noun pattern with 'assess_risk', which is clear and descriptive. Since there is only one tool, there is no inconsistency or mixing of conventions to evaluate, making it perfectly consistent by default.
A single tool is generally too few for most server purposes, as it limits functionality and can feel thin. For a risk analysis server, one tool might suffice if it covers all necessary operations, but typical MCP servers benefit from multiple tools to handle different aspects of a domain, making this count borderline inadequate.
The tool 'assess_risk' provides a core risk assessment function, but there are notable gaps in coverage. For a risk analysis domain, one might expect additional tools for managing risk profiles, retrieving historical assessments, or configuring risk thresholds. However, the single tool does address the primary need, leaving room for expansion.
Maintenance
Related MCP Connectors
AI code governance and code review for Claude Code, Copilot and Cursor. Checks rules and security.
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Security scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.
Security scanner for AI agents: prompt injection, leaked secrets, PII, and SSRF-risk URL detection.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceProvides AI coding assistants with real-time security scanning superpowers, including SAST, secrets detection, dependency CVE scanning, and web vulnerability assessment.15 npmApache 2.0- FlicenseNot gradedqualityCmaintenanceSecurely feeds summarized expert security rules into your coding assistance Claude Code, Cursor, etc ā zero config, no API key.-
- AlicenseAqualityDmaintenanceActs as a production-grade safety layer for AI-assisted coding, monitoring Git hygiene, scanning for security issues (PII, secrets, injection), and enabling semantic history search.9MIT

shipsafe-mcpofficial
AlicenseAqualityCmaintenanceEnables AI coding assistants to scan projects for security issues such as leaked API keys, missing Supabase RLS, open Firebase rules, unauthenticated routes, and hallucinated packages, then fix and verify the results.81MIT