mPower Social
mPower Social Enterprises Ltd. is a Dhaka, Bangladesh technology-for-development company founded in 2008 by Harvard and MIT graduate students as ClickDiagnostics — winner of the MIT $100K competition — and renamed after moving its center of gravity to Bangladesh in 2010. mPower designs, builds and operates information systems for governments, UN agencies, donor organizations and international NGOs across health and nutrition, water and sanitation, agriculture and livestock, education, governance and rights, livelihood and poverty alleviation, climate and environment, and humanitarian response, and states it has deployed more than 300 ICT solutions across 17 countries in the Global South. Its engineering practice is built on open-source digital public goods — DHIS2, OpenMRS, OpenSRP / FHIR Core, Bahmni and Moodle — which it customizes, integrates and supports for national health management information systems, electronic medical records and shared health records, rather than shipping a hosted product of its own. The company is ISO 9001:2015 certified. mPower publishes no public API, developer portal, or machine-readable contract; its public software surface is a GitHub organization made up largely of downstream forks of the open-source health platforms it implements, plus a set of first-party Android apps on Google Play.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles mPower Social the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — mPower Social scores 13.0/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
mPower Social is an ICT4D implementer that builds bespoke DHIS2, OpenMRS, OpenSRP/FHIR Core, Bahmni and Moodle systems inside client governments and NGOs, so the only APIs in its work belong to those upstream projects; mpower-social.com is a WordPress marketing site with no /developers or /api page, api./docs./developer. do not resolve in DNS, and the one technical subdomain that does resolve — dhis2.mpower-social.com — never answers on port 443 from the public internet.
This is an honest zero, not a gap in our research. mPower Social does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://mpower-social.com/openapi.json→ HTTP 404https://mpower-social.com/api-docs→ HTTP 404https://mpower-social.com/llms.txt→ HTTP 404https://mpower-social.com/.well-known/agent-card.json→ HTTP 404https://mpower-social.com/.well-known/security.txt→ HTTP 404https://dhis2.mpower-social.com/api/system/info→ HTTP 0
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Put this on your own site. The badge is drawn live from mPower Social's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/clickdiagnostics/"
title="mPower Social on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/clickdiagnostics.svg"
alt="mPower Social Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/clickdiagnostics/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/clickdiagnostics/"
title="mPower Social on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/clickdiagnostics/card.svg"
alt="mPower Social Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile mPower Social
Each block below is one kind of artifact we hold for mPower Social. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for mPower Social — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 10
The organization behind the API
Scroll within the panel for all 10 ·
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/clickdiagnostics · machine-readable index on apis.io
This is an independent, third-party profile of mPower Social, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.