MCP server providing secure API Setu query methods to Claude for accessing MeitY (Ministry of Electronics and Information Technology) India DPI (Digital Public Infrastructure) services, with regional deployment evaluation and neuro-symbolic mathematical verification capabilities.
Single tool with basic schema and description. Tool name 'query_apisetu_registry' lacks action verb prefix (should be 'get_' or 'fetch_'). Description is adequate (127 chars, within 10-1024 range) but lacks WHEN/WHY guidance. Input schema present with types and descriptions, but output is unstructured string rather than typed object. No error handling guidance for LLM recovery. No parameter constraints (enums, ranges). Missing idempotency declaration and permission scope documentation.
Exposes a secure API Setu query method to Claude. Enforces strict structural string checking at the perimeter before querying MeitY services.
Tool name lacks action verb prefix. 'query_apisetu_registry' should be 'get_apisetu_document' or 'fetch_apisetu_registry' to signal intent clearly.
Output is unstructured string (e.g., '[INDIA_DPI_SUCCESS] Data verified...') instead of typed JSON object. LLM cannot parse fields reliably or chain to downstream tools.
No error handling guidance. Errors return strings like '[PERIMETER_REJECTION]' and '[INDIA_DPI_ERROR]' without actionable recovery hints (e.g., 'Try with uppercase document_type').
Input parameters lack constraints. 'document_type' and 'document_id' are free-form strings with no enum, regex, or length bounds documented in descriptions.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 42 | <=2025-11-25 | v2 |
No permission scope or security declaration. Tool accesses MeitY gateway but does not declare required scopes (e.g., 'read:apisetu_documents') or audit trail requirements.