MCP server that provides access to one-time password (OTP) codes from a 2FA browser extension. Allows requesting OTP codes with optional search queries to find specific accounts.
Single tool 'otp_request' has a complete input schema with proper enum constraint on 'cmd' parameter and optional 'query' parameter. Output schema is well-structured with oneOf union type supporting both success (OTP response) and error cases. However, descriptions lack depth and actionability. Tool description (95 chars) is below the 194-char baseline and does not explain WHEN to use it or what prerequisites exist. Parameter descriptions are minimal: 'cmd' description merely restates the enum value; 'query' description provides examples but no guidance on search behavior or expected format. Error handling is structurally present but lacks recovery guidance, no indication of what the LLM should do if OTP is not found or how to retry. No tool annotations (readOnlyHint, idempotentHint) despite being READ_ONLY. Transport mechanism unknown from source code.
Request a one-time password (OTP) code from the 2FA extension. The extension searches stored OTP accounts using the optional query.
Tool description lacks actionability and context. At 95 characters, it falls short of the 194-char baseline and does not explain WHEN to call this tool, what prerequisites exist (e.g., 2FA extension must be installed), or what happens on error.
Parameter 'query' description provides examples ('github', 'google', 'my account') but lacks format guidance. LLMs may pass arbitrary strings. Should specify: is partial matching supported? Case-sensitive? What happens if multiple matches exist?
Error response structure is defined but lacks recovery guidance. When error object is returned, the description does not tell the LLM what to do next (e.g., 'Try a different query', 'Ensure 2FA extension is active'). Violates recovery-guide pattern.
Tool is marked READ_ONLY but lacks tool annotations (readOnlyHint). Modern MCP spec supports structured annotations to signal intent to LLMs and clients.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2025-06-18+ | v2 |
Transport mechanism is UNKNOWN from source code. Only a static JSON schema file is visible (v3/mcp/mcp.json). No evidence of HTTP, SSE, or STDIO transport implementation. Cannot assess protocol readiness without transport details.