@atbas/m-mcp 0.1.0 → 0.1.1

package/README.md

@@ -1,10 +1,10 @@
-# JazzCash MCP Integration Server
+# Payment Gateway MCP Integration Server
 
-An MCP server that performs JazzCash payment-gateway integrations inside a merchant's own AI tooling — Claude Desktop, Claude Code, Cursor, or any other MCP client.
+An MCP server that performs payment-gateway integrations inside a merchant's own AI tooling — Claude Desktop, Claude Code, Cursor, or any other MCP client.
 
 ## The problem
 
-Merchant onboarding at JazzCash depends on two resident engineers, one seat vacant, walking every merchant's developer through the same hosted checkout, the same credentials, the same hash generation, the same return URLs, the same sandbox tests. Go-live speed is capped by engineer hours rather than by how ready the merchant is, and the knowledge leaves with the people.
+Merchant onboarding at a payment gateway depends on two resident engineers, one seat vacant, walking every merchant's developer through the same hosted checkout, the same credentials, the same hash generation, the same return URLs, the same sandbox tests. Go-live speed is capped by engineer hours rather than by how ready the merchant is, and the knowledge leaves with the people.
 
 This server encodes what those engineers know so the merchant's own AI can do the integration: look up the official guidance, generate correct code, validate parameters and secure hashes, run sandbox transactions, and diagnose failures — while the engineers keep the parts that need judgement.
 
@@ -24,7 +24,7 @@ The MCP server is what most of this README documents. [The hosted tier](#the-hos
 
 ## Safety first
 
-Sandbox and production share **identical gateway URLs** in every official JazzCash guide. The environment is a property of the _credentials_, not the endpoint.
+Sandbox and production share **identical gateway URLs** in every official gateway guide. The environment is a property of the _credentials_, not the endpoint.
 
 - Every network tool requires an explicit `environment` argument.
 - Production money movement requires **both** `JAZZCASH_ALLOW_LIVE=true` in the server environment **and** `confirmLiveEnvironment: true` on the call.
@@ -35,15 +35,15 @@ Read [`docs/mcp/SAFETY.md`](docs/mcp/SAFETY.md) before pointing this at producti
 
 ## What it knows
 
-The knowledge corpus is transcribed from the fourteen 2026 JazzCash merchant guides in `docs/integration_documents/`, covering **14 integration flows**: card and BNPL hosted checkout, MWallet REST v1.1 and v2.0, token payment, wallet linking, token inquiry and delete, Status Inquiry v1.1 and v2.0, and four refund variants — plus IPN, the merchant portal, WooCommerce and Shopify.
+The knowledge corpus is transcribed from the fourteen 2026 merchant guides in `docs/integration_documents/`, covering **14 integration flows**: card and BNPL hosted checkout, MWallet REST v1.1 and v2.0, token payment, wallet linking, token inquiry and delete, Status Inquiry v1.1 and v2.0, and four refund variants — plus IPN, the merchant portal, WooCommerce and Shopify.
 
 It also encodes the places those guides contradict themselves, because those are where merchants get stuck. Among them: the official PHP sample silently drops a value of integer `0` from the hash; the wallet-linking sample publishes the Integrity Salt in browser JavaScript; card and BNPL refunds return unprefixed response fields; the MWallet v2.0 sample sets an expiry two days out while the same page says one; the token payment sample sets an expiry two months _before_ its transaction. All are recorded, tested against, and corrected in generated code.
 
-Open questions raised by this work are collected in [`docs/mcp/JAZZCASH-CLARIFICATIONS.md`](docs/mcp/JAZZCASH-CLARIFICATIONS.md) for the acquiring team.
+Open questions raised by this work are collected in [the clarifications register](docs/mcp/JAZZCASH-CLARIFICATIONS.md) for the acquiring team.
 
 ## Install
 
-### For merchants — once published
+### For merchants
 
 ```bash
 npx -y @atbas/m-mcp        # nothing to clone, nothing to build
@@ -55,9 +55,11 @@ Or register it directly with your AI tool and let the tool fetch it:
 { "mcpServers": { "m-mcp": { "command": "npx", "args": ["-y", "@atbas/m-mcp"] } } }
 ```
 
-`npx` keeps merchants on the current corpus automatically, which matters because JazzCash reissues these guides yearly.
+`npx` keeps merchants on the current corpus automatically, which matters because the gateway reissues these guides yearly.
 
-> **Not yet published.** Nothing is on npm under either name: `npm view jazzcash-mcp` returned a 404 on 2026-08-23, and the package was renamed to `@atbas/m-mcp` later the same day without a version ever being published under it — so neither command above resolves anything today. What was holding it is settled: redistribution of the transcribed corpus was authorised by the product director on 2026-08-23 (assumption A7), the licence decision is MIT, and `package.json` now carries that licence and no `"private"` key. `npm pack` works and the tarball has been verified end to end; [`docs/mcp/PUBLISHING.md`](docs/mcp/PUBLISHING.md) lists the steps that remain, and the one question — trademark — that is still JazzCash's to answer.
+> **Published.** `@atbas/m-mcp` 0.1.0 went to npm on 2026-08-23 — <https://www.npmjs.com/package/@atbas/m-mcp> — so both commands above resolve today. What had been holding it is settled: redistribution of the transcribed corpus was authorised by the product director on 2026-08-23 (assumption A7), the licence decision is MIT, and `package.json` carries that licence and no `"private"` key.
+>
+> The connector is a **separate package and is not on npm yet**, so every snippet naming `@atbas/m-mcp-connector` still resolves nothing. [`docs/mcp/PUBLISHING.md`](docs/mcp/PUBLISHING.md) lists the steps that remain for it, and the one question — the mark — that is still the acquirer's to answer.
 
 ### From this repository
 
@@ -130,7 +132,7 @@ The intended entry points are the prompt and one tool:
 A typical session:
 
 ```
-"Add JazzCash mobile wallet payments to my checkout."
+"Add mobile wallet payments to my checkout."
   → jazzcash_list_integration_flows        pick a flow
   → jazzcash_get_onboarding_checklist      what to do in the portal first
   → jazzcash_generate_integration_code     working PHP, Node or Python
@@ -295,12 +297,12 @@ knowledge/      the data: flows, docs, templates, diagnostics
 
 Two properties are worth preserving if you extend this:
 
-- **The corpus is data, not code.** Flow specifications, documentation, templates and diagnostics all live in `knowledge/`. A correction from JazzCash should be a data change.
+- **The corpus is data, not code.** Flow specifications, documentation, templates and diagnostics all live in `knowledge/`. A correction from the gateway should be a data change.
 - **Citations are tested.** Every `docRef` on every flow, and every reference in the diagnostics base, is asserted to resolve to a real document _and_ section. An anchor on a heading too deep to be addressable fails at load rather than producing a dead link.
 
 ### Testing notes
 
-No test reaches the JazzCash gateway. `tests/helpers/stub-gateway.ts` is a local HTTP server, and the production guard is separately asserted to fire before any request is recorded.
+No test reaches the live gateway. `tests/helpers/stub-gateway.ts` is a local HTTP server, and the production guard is separately asserted to fire before any request is recorded.
 
 `src/domain/secure-hash.ts`, `src/domain/amount.ts`, `src/gateway/guards.ts` and `src/telemetry/redaction.ts` are held at 100 % statement, branch, function and line coverage by per-file thresholds in `vitest.config.ts` — the run fails, not warns, if that regresses.
 
@@ -359,6 +361,6 @@ When a project's `engines.node` moves, move its `@types/node` in the same change
 
 ## Licence
 
-**MIT**, decided on 2026-08-23 alongside the same day's authorisation of the corpus for redistribution and sale (assumption A7), and carried in `package.json` since. The knowledge corpus is derived from JazzCash merchant guides: MIT covers this repository's own work and makes no claim over JazzCash's documentation, specifications or marks. The use of the mark itself is the one part of item 13 in [`docs/mcp/JAZZCASH-CLARIFICATIONS.md`](docs/mcp/JAZZCASH-CLARIFICATIONS.md) that no decision here can answer, and it is still open.
+**MIT**, decided on 2026-08-23 alongside the same day's authorisation of the corpus for redistribution and sale (assumption A7), and carried in `package.json` since. The knowledge corpus is derived from the gateway's own merchant guides: MIT covers this repository's own work and makes no claim over that documentation, those specifications or the marks on them. The use of the mark itself is the one part of item 13 in [the clarifications register](docs/mcp/JAZZCASH-CLARIFICATIONS.md) that no decision here can answer, and it is still open.
 
-`connector/` carries the same licence. `@atbas/m-mcp-connector` is MIT, © 2026 Eren Atbas: it ships the 14 flow specifications and the credential half of this server, and none of the transcribed documents, the templates or the diagnostics base. [`docs/mcp/PUBLISHING.md`](docs/mcp/PUBLISHING.md) records exactly what that package and its public mirror each carry, what stays here, and the steps neither package has been through — as of 2026-08-23, neither is on npm.
+`connector/` carries the same licence. `@atbas/m-mcp-connector` is MIT, © 2026 Eren Atbas: it ships the 14 flow specifications and the credential half of this server, and none of the transcribed documents, the templates or the diagnostics base. [`docs/mcp/PUBLISHING.md`](docs/mcp/PUBLISHING.md) records exactly what that package and its public mirror each carry, what stays here, and the steps it has not been through — as of 2026-08-23 the server is on npm and the connector is not.

package/dist/version.d.ts

@@ -12,7 +12,7 @@
  * name with its scope removed, so the two still cannot drift apart.
  */
 export declare const SERVER_NAME = "m-mcp";
-export declare const SERVER_VERSION = "0.1.0";
+export declare const SERVER_VERSION = "0.1.1";
 /**
  * Version stamp of the JazzCash documentation corpus this build encodes.
  *

package/dist/version.js

@@ -12,7 +12,7 @@
  * name with its scope removed, so the two still cannot drift apart.
  */
 export const SERVER_NAME = 'm-mcp';
-export const SERVER_VERSION = '0.1.0';
+export const SERVER_VERSION = '0.1.1';
 /**
  * Version stamp of the JazzCash documentation corpus this build encodes.
  *

package/package.json

@@ -1,9 +1,9 @@
 {
   "name": "@atbas/m-mcp",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "packageManager": "npm@12.0.2",
   "license": "MIT",
-  "description": "MCP server that performs JazzCash payment-gateway integrations inside a merchant's own AI tooling.",
+  "description": "MCP server that performs payment-gateway integrations inside a merchant's own AI tooling.",
   "author": "Eren Atbas <eren.atbas@gmail.com>",
   "repository": {
     "type": "git",
@@ -14,7 +14,6 @@
     "url": "https://github.com/eatbas/m-mcp/issues"
   },
   "keywords": [
-    "jazzcash",
     "mcp",
     "model-context-protocol",
     "payments",