Related Servers

The tool set spans four distinct managers (Evidence, Signature, Notification, Chat) with mostly clear boundaries, but within Evidence there is significant overlap: evidence_download_url_create vs evidence_group_evidence_download_url_create, evidence_upload_url_create vs evidence_group_evidence_upload_url_create, and legacy tools (generate_evidence, get_evidence) that duplicate group-scoped equivalents. An agent could easily pick the wrong variant.

Naming is highly inconsistent: evidence tools use a mix of noun_verb (evidence_case_file_create), verb_noun (generate_evidence, get_evidence), and composite patterns (evidence_create_sealed), while signature and notification tools use bare verb_noun (create_signature_request, activate_signature_request, notification_receiver_add). Legacy top-level names (generate_evidence, get_evidence) break the evidence_* prefix convention, and there are near-duplicate names differing only by scope (evidence_download_url_create vs evidence_group_evidence_download_url_create).

64 tools is far beyond the typical well-scoped MCP server range. While the server covers four distinct domains, the count is inflated by redundant legacy tools, bulk variants, and multiple URL-creation tools that could be consolidated. The sheer number makes it hard for an agent to discover and choose the right tool.

The Evidence manager covers the full lifecycle (create case file, groups, register/upload evidence, close/seal, generate reports, delete), and Signature/Notification have create, update, activate, status, and certificate flows. Minor gaps exist: there is no evidence_case_file_delete for a single case file (only bulk), no signature request update tool, and no chat tools are actually present despite the help text mentioning a Chat manager.