Model Context Protocol server for Signal Protocol with formal verification
Signal MCP has critical definition gaps. All 3 tools lack complete input schemas in the visible code, only partial property definitions shown without full JSON Schema structure (no 'required' arrays, no type constraints on nested objects). Tool descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameter descriptions exist but are minimal ('Recipient identifier', 'Message plaintext'). No output schemas documented. The codebase shows placeholder implementations (TODO comments, hardcoded responses like 0xDEADBEEF), indicating incomplete development. Tool definitions appear inferred from macro decorators rather than explicit registration with full schemas.
Encrypt a message using Signal Protocol (Double Ratchet + Sealed Sender)
Initialize a new Signal Protocol session using X3DH key agreement
Compute and verify safety numbers (fingerprints) for identity verification
Input schemas incomplete: properties shown but no 'required' array, no type constraints on 'prekey_bundle' object, no format/pattern specs. Violates JSON Schema completeness.
No output schemas documented. LLMs cannot infer response structure (e.g., EncryptionResponse fields, SafetyNumber format). Violates pattern:tool requirement.
Placeholder implementations with TODO comments and hardcoded test values (0xDEADBEEF, '123456789012345678901234567890'). Tools do not actually perform Signal Protocol operations.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | <=2025-11-25 | v2 |
Parameter descriptions are minimal (10-20 chars). 'Recipient identifier' and 'Message plaintext' lack context on format, constraints, or when to use. Below 72-char baseline for param annotations.
No error handling guidance. Tools return generic success/failure with no recovery hints. Missing pattern:recovery-guide implementation.