Orcho MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORCHO_API_KEY | No | Your Orcho API key for risk assessment. Get your API key from app.orcho.ai. The test key has limited functionality and rate limits. | test_key_orcho_12345 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assess_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.