@ekoindia/eps-context-mcp 0.1.20 → 0.1.22

package/README.md

@@ -28,6 +28,33 @@ status to **stderr** and waits for an MCP client on stdin/stdout.
 
 Requires **Node.js ≥ 18**.
 
+## Hosted (remote) server
+
+The same tools are also served over streamable HTTP, with nothing to install:
+
+```
+https://mcp.eko.in/context/mcp
+```
+
+No auth, no key, no signup — every tool is a read-only lookup over the public
+API bundle. Use it when your agent cannot spawn a local process (claude.ai
+connectors, Lovable, other hosted agents), or when you would rather not manage a
+version at all: the hosted server re-validates the bundle against the live site,
+so it always answers from current docs.
+
+```bash
+# Claude Code, as a remote server
+claude mcp add eps --transport http https://mcp.eko.in/context/mcp
+```
+
+`POST` only (per the MCP streamable-HTTP spec — the server keeps no session), and
+`GET https://mcp.eko.in/context/healthz` reports the bundle version it is serving.
+Rate-limited per IP at the proxy.
+
+**stdio is still the better fit for CLI agents** (Claude Code, Cursor, Codex):
+it starts instantly, works offline from the baked bundle, and costs no network
+round trip per tool call.
+
 ## Tools
 
 All tools are read-only and **secret-free** — none of them accept an

package/data/eps.json

@@ -2,7 +2,7 @@
   "meta": {
     "org": "ekoindia",
     "apiVersion": "v3",
-    "bundleVersion": "73ed06cf",
+    "bundleVersion": "e6084a34",
     "environments": [
       {
         "id": "sandbox",
@@ -7001,6 +7001,14 @@
           "description": "State code, where the operator requires it.",
           "example": "1",
           "in": "query"
+        },
+        {
+          "name": "communication",
+          "type": "number",
+          "required": false,
+          "description": "Payment mode: `0` (default) = online — instant settlement, lower commission. `1` = offline — higher commission, but the bill takes a minimum of 6 working hours to settle. Pass the same value to Pay Bill.",
+          "example": 0,
+          "in": "query"
         }
       ],
       "sampleRequest": {},
@@ -7292,6 +7300,14 @@
           "description": "District-level distribution company code. Required for **operator 190 (UPPCL) only** — pass the same value used at Fetch Bill.",
           "example": "Lucknow-MVVNL",
           "in": "body"
+        },
+        {
+          "name": "communication",
+          "type": "number",
+          "required": false,
+          "description": "Payment mode: `0` (default) = online — instant settlement, lower commission. `1` = offline — higher commission, but the bill takes a minimum of 6 working hours to settle. Pass the same value used at Fetch Bill.",
+          "example": 0,
+          "in": "body"
         }
       ],
       "sampleRequest": {
@@ -7305,7 +7321,8 @@
         "utilitycustomername": "Amit Kumar",
         "client_ref_id": "2026010100123456789",
         "source_ip": "192.168.1.1",
-        "district_discome": "Lucknow-MVVNL"
+        "district_discome": "Lucknow-MVVNL",
+        "communication": 0
       },
       "responseFields": [
         {
@@ -18329,8 +18346,8 @@
           "name": "dl_number",
           "type": "string",
           "required": true,
-          "description": "Driving license number to verify (e.g. MH0220190001234).",
-          "example": "MH0220190001234",
+          "description": "Driving license number to verify (e.g. KA0120198900984).",
+          "example": "KA0120198900984",
           "in": "body"
         },
         {
@@ -18338,15 +18355,15 @@
           "type": "string",
           "required": true,
           "description": "Date of birth of the DL holder in YYYY-MM-DD format. Used to cross-validate the license.",
-          "example": "1994-08-29",
+          "example": "1994-08-05",
           "in": "body"
         }
       ],
       "sampleRequest": {
         "initiator_id": "9962981729",
         "client_ref_id": "2026010100123456789",
-        "dl_number": "MH0220190001234",
-        "dob": "1994-08-29"
+        "dl_number": "KA0120198900984",
+        "dob": "1994-08-05"
       },
       "responseFields": [
         {
@@ -18384,7 +18401,7 @@
               "type": "string",
               "description": "The driving license number that was verified.",
               "imp": true,
-              "example": "MH0220190001234"
+              "example": "KA0120198900984"
             },
             {
               "name": "dob",
@@ -18392,7 +18409,7 @@
               "type": "string",
               "description": "Date of birth of the DL holder as returned by the authority.",
               "imp": true,
-              "example": "1994-08-29"
+              "example": "1994-08-05"
             },
             {
               "name": "status",
@@ -18882,12 +18899,6 @@
               "description": "Number of previous owners, including the current one.",
               "example": 1
             },
-            {
-              "name": "mobile_number",
-              "type": "string",
-              "description": "Mobile number of the owner as registered with the RTO, if available.",
-              "example": "98XXXXXXXX"
-            },
             {
               "name": "present_address",
               "type": "string",
@@ -20679,18 +20690,18 @@
       "responseTypes": []
     },
     {
-      "slug": "passport",
-      "productId": "passport",
-      "productName": "Passport Verification",
-      "name": "Passport Verification",
+      "slug": "passport-application",
+      "productId": "passport-application",
+      "productName": "Passport Application Validation",
+      "name": "Passport Application Validation",
       "method": "POST",
       "path": "/tools/kyc/passport",
-      "summary": "Verify Indian passport application details using passport file number and date of birth.",
+      "summary": "Validate Indian passport application details using passport file number and date of birth.",
       "category": "verification",
       "relevance": "M",
-      "description": "The Passport Verification API enables businesses to validate passport holder details using passport file number and date of birth. Returns holder name, DOB, application type, and application received date — suitable for KYC, employee background verification, travel compliance, and fintech onboarding workflows. Supports Indian passports only; not an OCR or MRZ scan API.",
+      "description": "The Passport Application Validation API enables businesses to validate passport holder details using passport file number and date of birth. Returns holder name, DOB, application type, and application received date — suitable for KYC, employee background verification, travel compliance, and fintech onboarding workflows. Supports Indian passports only; not an OCR or MRZ scan API.",
       "bestFor": "Employee BGV, travel-platform KYC, fintech onboarding, and immigration-assistance workflows that need structured passport data from the government source.",
-      "docsUrl": "https://eps.eko.in/docs/passport",
+      "docsUrl": "https://eps.eko.in/docs/passport-application",
       "headers": [
         {
           "name": "developer_key",
@@ -21584,7 +21595,7 @@
       "summary": "Check income tax return filing and compliance status for a PAN holder in real time — ideal for lending, credit assessment, and financial due-diligence workflows.",
       "category": "verification",
       "relevance": "M",
-      "description": "The ITR Compliance Check API verifies whether a given PAN holder has filed income tax returns and returns their compliance status, ITR filing flag, and the relevant assessment year. Built on the Eko TOURAS network, it gives lenders, NBFCs, and compliance teams an instant signal of a borrower's or vendor's tax-filing behaviour without requiring manual document collection. A single PAN input is all that is needed — no document uploads or consent flows.",
+      "description": "The ITR Compliance Check API verifies whether a given PAN holder has filed income tax returns and returns their compliance status, ITR filing flag, and the relevant assessment year. It gives lenders, NBFCs, and compliance teams an instant signal of a borrower's or vendor's tax-filing behaviour without requiring manual document collection. A single PAN input is all that is needed — no document uploads or consent flows.",
       "bestFor": "Lending platforms, NBFCs, and compliance teams that need an instant, automated ITR filing signal for a PAN holder during credit assessment or onboarding.",
       "docsUrl": "https://eps.eko.in/docs/itr-compliance",
       "headers": [

package/package.json

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