@ekoindia/eps-context-mcp 0.1.10 → 0.1.11

package/data/eps.json

@@ -2,7 +2,7 @@
   "meta": {
     "org": "ekoindia",
     "apiVersion": "v3",
-    "bundleVersion": "ff0f581a",
+    "bundleVersion": "76929d24",
     "environments": [
       {
         "id": "sandbox",
@@ -13974,7 +13974,7 @@
       "summary": "Check the activation status of every service for one of your agents.",
       "category": "util",
       "relevance": "M",
-      "description": "Returns the list of services for the given `user_code` with each service's status (ACTIVATED / PENDING), verification status, and timestamps.",
+      "description": "Returns every service enabled for the given `user_code`, with each service's\nactivation status, ops-verification status and timestamps. Use it to audit which\nservices one of your agents can actually transact on.\n\n## Service status (`service_status_list[].status`)\n\nNot to be confused with the top-level `status` — this one lives on each\nentry of `service_status_list`.\n\n| `status` | `status_desc` | Meaning |\n|---|---|---|\n| 0 | `DEACTIVATED` | Agent must re-upload their documents using the Activate Service API |\n| 1 | `ACTIVATED` | Service is live and usable |\n| 2 | `PENDING` | Activation pending for this agent |\n\n> [!NOTE]\n> Once the agent re-uploads their documents from the DEACTIVATED state, the\n> service moves to PENDING — not straight back to ACTIVATED.\n\n## Verification status (`verification_status`)\n\nTells you the action taken by the Eko operations team on the agent's documents\nfor that service.\n\n| `verification_status` | Meaning |\n|---|---|\n| 0 | Not applicable — this service needs no ops verification |\n| 1 | Verified — documents verified by the ops team |\n| 2 | Rejected — rejection reason is in the entry's `comments` field |\n| 3 | Pending — action pending from the ops team |",
       "bestFor": "Auditing which services are active for an agent.",
       "docsUrl": "https://eps.eko.in/docs/get-user-services",
       "headers": [
@@ -14024,6 +14024,14 @@
           "description": "Unique reference ID per API call, generated by your system (max 20 characters).",
           "example": "2026010100123456789",
           "in": "query"
+        },
+        {
+          "name": "user_code",
+          "type": "string",
+          "required": true,
+          "description": "Unique code of your user/agent/retailer the service is run for. Use `Onboard Agent` API to register your users",
+          "example": "20810200",
+          "in": "query"
         }
       ],
       "sampleRequest": {},
@@ -14074,21 +14082,27 @@
                   "name": "status_desc",
                   "type": "string",
                   "imp": true,
-                  "description": "Human-readable status (ACTIVATED / PENDING).",
+                  "description": "Human-readable status (ACTIVATED / PENDING / DEACTIVATED).",
                   "example": "ACTIVATED"
                 },
                 {
                   "name": "status",
                   "type": "number",
-                  "description": "Numeric status (1 = active, 2 = pending).",
+                  "description": "Activation status — 0 = deactivated (agent must re-upload documents via Activate Service), 1 = activated, 2 = pending.",
                   "example": 1
                 },
                 {
                   "name": "verification_status",
                   "type": "number",
-                  "description": "Verification state of the service.",
+                  "description": "Ops-team verification state — 0 = not applicable, 1 = verified, 2 = rejected (reason in `comments`), 3 = pending.",
                   "example": 3
                 },
+                {
+                  "name": "comments",
+                  "type": "string",
+                  "description": "Ops-team remark — holds the rejection reason when `verification_status` is 2, otherwise null.",
+                  "example": null
+                },
                 {
                   "name": "createdAt",
                   "type": "string",
@@ -14306,13 +14320,13 @@
       "slug": "get-wallet-balance",
       "productId": "user-management",
       "productName": "User & Agent Management",
-      "name": "Get Settlement Account Balance",
+      "name": "Get Wallet Balance",
       "method": "GET",
       "path": "/user/account/balance",
-      "summary": "Fetch the settlement-account (wallet) balance for a user.",
+      "summary": "Fetch the wallet balance for a user.",
       "category": "util",
       "relevance": "M",
-      "description": "Returns the current settlement-account balance for the given registered mobile number.",
+      "description": "Returns the current wallet (settlement account) balance for the given registered mobile number (for your own account or that of your users/agents).",
       "bestFor": "Checking an agent's wallet/settlement balance.",
       "docsUrl": "https://eps.eko.in/docs/get-wallet-balance",
       "headers": [

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ekoindia/eps-context-mcp",
-	"version": "0.1.10",
+	"version": "0.1.11",
 	"description": "Local MCP server giving AI coding agents context for Eko Platform Services (EPS) APIs.",
 	"license": "MIT",
 	"type": "module",