Existing Digital Public Goods expose callable functions that can act as AI Blocks within DPI Workflows. A growing ecosystem is becoming MCP-compatible — enabling AI agents to invoke them directly.
The DPG ecosystem creates a reinforcing cycle: existing DPGs provide callable infrastructure (identity verification, civil registration, health records, payments) that AI Blocks can invoke. New DPGs can be purpose-built as AI Blocks from the outset. And AI Blocks can themselves qualify as Digital Public Goods when they meet the DPGA standards.
Open-source civil registration and vital statistics system. Enables birth, death, and marriage registration with biometric identity linkage.
Open-source payment platform designed for interoperable, real-time, inclusive digital payments. Used for benefit disbursements, G2P payments, and merchant payments.
The world's largest health information management system. Aggregates health data from facility to national level, enabling evidence-based health policy and AI decision support.
Open-source insurance management information system for social health protection programs. Manages enrollment, eligibility, claims, and benefit payments.
Open-source digital infrastructure for education. Powers DIKSHA (India's national education platform) and deployed in multiple countries. Supports personalized learning, teacher training, and student assessment.
Open-source workflow automation platform designed for the social sector. Connects DPGs and enables DPI Workflow orchestration. Used by UN agencies, governments, and NGOs in 40+ countries.
Open-source consent management and data governance infrastructure. Enables citizens to manage data permissions, view consent records, and revoke access — a critical AI Block for any DPI Workflow involving personal data.
Open geospatial data infrastructure. Critical for crisis response workflows — identifying affected populations, routing aid, and mapping service coverage. Provides the data layer for area_classify() AI Blocks.
Modular Open Source Identity Platform — one of the most widely deployed open-source identity platforms globally. Used by countries across Africa and Asia to issue national IDs with biometric verification. Exposes robust identity APIs that are AI Block-ready for identity_verify() and enrollment workflows. Comprehensive OpenAPI/Swagger specs across all versions; eSignet provides OpenID Connect layer.
Inji is an open-source verifiable credentials wallet and issuance platform from the MOSIP Foundation. Enables citizens to hold and present tamper-proof digital credentials (ID, health records, education certificates) via mobile. Critical for AI workflows that need to verify credentials without querying a central registry on every interaction. Implements OpenID4VCI draft 13 — structured REST endpoints, predictable for MCP wrapping.
CREDEBL is an open-source Self-Sovereign Identity (SSI) platform that enables governments and institutions to issue, manage, and verify W3C Verifiable Credentials at scale. Now an LF Decentralized Trust project. Built for high-volume credential issuance with enterprise-grade governance. Microservices REST architecture (API Gateway); supports multiple ledgers and ledger-less issuance (did:web, did:key, did:peer).
walt.id provides open-source infrastructure for decentralised identity and verifiable credentials. Widely used by developers building identity-first applications. Supports W3C DID, W3C VCs, SD-JWT (selective disclosure), and OpenID4VC protocols — making it the most interoperable VC toolkit available. Excellent for wrapping as an AI Block in identity verification workflows.
The Model Context Protocol (MCP) enables AI agents to invoke DPGs as callable tools with governed context exchange. None of the platforms below have native MCP support yet — but all can be wrapped as MCP tool servers via their REST APIs. Native integration is an emerging capability across the ecosystem.
Evaluated March 2026. No native MCP support found in any repository. All three expose REST APIs wrappable as MCP tool servers.
Most mature API surface of the three. Comprehensive OpenAPI/Swagger specs across all versions (1.1.5, 1.2.0+). eSignet exposes an OpenID Connect authentication layer. No native MCP; straightforward to wrap identity.verify() and authenticate() endpoints as MCP tools. High wrappability.
OpenID4VCI-compliant REST APIs (draft 13). Inji Certify exposes structured credential issuance endpoints; Inji Web adds a browser wallet layer. Standards compliance (W3C VC, OpenID4VCI) makes MCP wrapping predictable and interoperable. No native MCP. Moderate-to-high wrappability.
Microservices REST architecture (API Gateway port 5000/api). Built on Hyperledger Aries/Indy; supports W3C DIDs, AnonCreds, and ledger-less issuance (did:web, did:key). Now an LF Decentralized Trust project. API docs less publicly indexed than MOSIP/Inji — review GitHub directly. Moderate wrappability; no native MCP.
DPGs with well-documented REST APIs are MCP-ready in principle — they can be wrapped as MCP servers without code changes to the DPG itself.
REST API well-documented. Can be wrapped as MCP tool server.
Open API spec published. MCP wrapper straightforward.
Comprehensive REST API. Active developer community.
Exploring MCP integration for workflow triggers.
AI/ML API extensions under active development.
GraphQL API available; MCP wrapper community request.
Any DPG with a REST API can be wrapped as an AI Block. The pattern is always the same: wrap the API call, declare the governance spec, and make it callable from a workflow engine.
→ This block can now be called from any DPI Workflow as ai.civil_registry_verify_v1() — with governance, audit logging, and replaceability built in.
→ Learn more about AI Block specifications · → Implementation Guide