Production-grade MCP server with OAuth 2.1, elicitation, and observability for financial data access including stock quotes, exchange rates, and price alerts
Server has 9 tools with complete schemas and descriptions. Naming follows verb_noun convention (get_, set_, delete_, update_, confirm_, scan_). Descriptions are present and mostly adequate (avg ~120 chars). However, several tools lack parameter descriptions (e.g., confirm_operation has no description for 'operation_id'), and output schemas are not documented. Error handling is basic. Two-phase write pattern (elicitation) is well-structured but not reflected in tool annotations. STDIO transport caps protocol readiness.
Confirms and executes a pending elicitation operation. Phase 2 of the two-phase write pattern.
Converts an amount from one currency to another using current exchange rates
Deletes an existing price alert. Requires elicitation confirmation.
Retrieves current exchange rates for a base currency against multiple target currencies
Retrieves a summary of portfolio holdings with current valuations
Retrieves current stock quote information for a given symbol
confirm_operation lacks parameter description for 'operation_id'. LLMs cannot infer what an operation_id is or how to obtain it without explicit guidance.
delete_price_alert and update_alert_threshold have minimal descriptions (60 chars). They do not explain the two-phase elicitation flow or that confirmation is required. LLMs may not understand the workflow.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., alert_id from set_price_alert response). This breaks tool chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
Runs the RedForge security scan against all registered MCP tool definitions. Returns a security scorecard with risk rating, per-check findings, and remediation guidance. Requires admin scope.
Sets a price alert for a stock symbol at a target price. Requires elicitation confirmation.
Updates the price threshold of an existing alert. Requires elicitation confirmation.
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are missing. The server declares risk levels in metadata but does not expose them via MCP tool annotations, limiting client-side safety guardrails.
confirm_operation description does not explain what 'pending operation' means or how to obtain an operation_id. The two-phase pattern is underdocumented for LLM consumption.