agentpay-mcp 4.1.4 → 4.1.6

package/Dockerfile

@@ -0,0 +1,15 @@
+FROM node:20-slim AS builder
+WORKDIR /app
+COPY package*.json ./
+RUN npm ci
+COPY tsconfig.json ./
+COPY src/ ./src/
+RUN npm run build
+
+FROM node:20-slim
+WORKDIR /app
+COPY --from=builder /app/dist ./dist
+COPY --from=builder /app/node_modules ./node_modules
+COPY package*.json ./
+ENV NODE_ENV=production
+ENTRYPOINT ["node", "dist/index.js"]

package/README.md

@@ -90,6 +90,7 @@ AgentPay MCP is built for enterprise MCP deployments where supply chain security
 - **x402 multi-SDK batch-settlement parity.** For providers testing x402 TypeScript and Go batch-settlement clients, use the [multi-SDK batch-settlement parity recipe](docs/x402-multi-sdk-batch-settlement-parity.md) to prove shared channel state, phased e2e results, signer separation, refund/recovery visibility, and proof bundle shape.
 - **x402 TVM readiness.** For TVM/TON exact-payment offers from emerging x402 examples, use the [x402 TVM readiness note](docs/x402-tvm-readiness.md) to confirm unsupported TVM requirements fail closed until deliberate signing, gas, jetton, and settlement support exists.
 - **x402 MCP funding UX.** For hosted fund-link and managed-wallet comparisons, use the [x402 MCP funding UX benchmark](docs/x402-mcp-funding-ux-benchmark.md) to keep onboarding speed separate from approval gates, daily caps, auditability, and non-custodial controls.
+- **Directory introspection readiness.** For Glama, Smithery, and other MCP catalogs, use the [directory introspection readiness note](docs/directory-introspection-readiness.md) for verified `npx`, Docker, MCP name, and non-custodial metadata paths.
 - **WhatsApp and SMB agent controls.** For channel-native paid agents, use the [WhatsApp and SMB paid-agent controls recipe](docs/whatsapp-smb-agent-controls.md).
 - **Channel-agent affiliate payout controls.** For Axon-style affiliate and referral revenue shares, use the [channel-agent affiliate controls spec](docs/channel-agent-affiliate-controls.md) to keep payout caps, per-contact approval, audit rows, and optional x402 settlement separate from paid tool spend approval.
 - **x402 chain drift.** AgentPay MCP tracks the x402 Foundation paywall-template baseline with `viem` `^2.47.12` or newer, and fails closed for unmapped chains. For PaymentWrapper and paywall template changes, follow the [x402 chain-drift compatibility note](docs/x402-chain-drift-compatibility.md).

package/dist/index.js

@@ -42,7 +42,7 @@ const otel_budget_js_1 = require("./tools/otel-budget.js");
 // ─── Server configuration ──────────────────────────────────────────────────
 const SERVER_INFO = {
     name: 'agentpay-mcp',
-    version: '4.0.0',
+    version: '4.1.6',
 };
 const SERVER_CAPABILITIES = {
     tools: {},
@@ -261,7 +261,7 @@ async function main() {
     });
     await server.connect(transport);
     // Log to stderr (not stdout — stdout is reserved for MCP protocol)
-    process.stderr.write(`AgentPay MCP v1.1.0 started. ` +
+    process.stderr.write(`AgentPay MCP v4.1.6 started. ` +
         `Wallet: ${process.env['AGENT_WALLET_ADDRESS'] ?? '(not configured)'} | ` +
         `Chain: ${process.env['CHAIN_ID'] ?? '8453 (Base Mainnet)'} | ` +
         `Session TTL: ${process.env['SESSION_TTL_SECONDS'] ?? '3600'}s\n`);

package/docs/directory-introspection-readiness.md

@@ -0,0 +1,77 @@
+# AgentPay MCP directory introspection readiness
+
+Paid MCP servers are starting to get ranked by catalog proof, not only by README claims. This note records the install paths a directory crawler can verify without changing AgentPay MCP's custody model.
+
+## Machine-readable package identity
+
+- npm package: `agentpay-mcp`
+- MCP server name in `package.json`: `io.github.up2itnow0822/agentpay`
+- MCP runtime name from `initialize`: `agentpay-mcp`
+- CLI binary: `agentpay-mcp`
+- Repository: `https://github.com/up2itnow0822/agentpay-mcp`
+- Docker entrypoint: `node dist/index.js`
+
+The package does not create or manage a hot wallet by default. Directory installs should require explicit operator-supplied wallet configuration.
+
+## npx path
+
+Use this for local MCP clients and catalog recipes that execute npm packages directly:
+
+```json
+{
+  "mcpServers": {
+    "agentpay": {
+      "command": "npx",
+      "args": ["-y", "agentpay-mcp"],
+      "env": {
+        "AGENT_PRIVATE_KEY": "0x...",
+        "AGENT_WALLET_ADDRESS": "0x...",
+        "CHAIN_ID": "8453",
+        "RPC_URL": "https://mainnet.base.org"
+      }
+    }
+  }
+}
+```
+
+AGENT_PRIVATE_KEY stays local to the MCP runtime. AgentPay MCP does not ask a catalog to custody keys, generate first-run wallets, or opt users into a managed-wallet path.
+
+## Docker path for Glama-style introspection
+
+Build from the repository root:
+
+```bash
+docker build -t agentpay-mcp:glama-introspection .
+```
+
+Run stdio introspection with a placeholder address. Tool listing does not require a private key because tools are registered before any payment call loads spend policy state:
+
+```bash
+printf '%s\n' \
+  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"catalog-check","version":"0.0.1"}}}' \
+  '{"jsonrpc":"2.0","method":"notifications/initialized","params":{}}' \
+  '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' |
+  docker run --rm -i \
+    -e AGENT_WALLET_ADDRESS=0x0000000000000000000000000000000000000000 \
+    agentpay-mcp:glama-introspection
+```
+
+Expected proof points:
+
+- `initialize` returns server name `agentpay-mcp`.
+- `tools/list` returns payment tools such as `x402_pay`, `check_budget`, `set_spend_policy`, and `otel_evaluate_spend`.
+- No default managed wallet is created during introspection.
+
+## Glama metadata
+
+`glama.json` is present at the repository root with schema `https://glama.ai/mcp/schemas/server.json` and maintainer `up2itnow0822`. Glama-style crawlers can use this alongside the Dockerfile to identify the server without asking users to move private keys into a hosted catalog.
+
+## Smithery-compatible metadata
+
+`smithery.yaml` declares the same stdio start command and wallet environment variables. The schema marks private-key input as a password field and keeps `CHAIN_ID` constrained to supported Base values.
+
+This is a catalog metadata file, not a hosting custody model. Hosted directory operators should still treat AgentPay MCP as a user-controlled, non-custodial server.
+
+## Listing status
+
+As of 2026-05-01, the Glama listing is live at `https://glama.ai/mcp/servers/up2itnow0822/claw-pay-mcp` and returned HTTP 200 during validation. The current Glama slug still reflects the older `claw-pay-mcp` crawl identity, so keep `glama.json`, the npm package name, and the MCP `mcpName` aligned for the next catalog refresh. Smithery listing URLs checked today returned HTTP 404, so do not claim a live Smithery listing until Smithery verifies it. The verified live paths today are npm, GitHub, Glama, repository metadata (`glama.json`, `smithery.yaml`, `Dockerfile`), and the open AgentPay MCP PR carrying this readiness note.

package/glama.json

@@ -0,0 +1,4 @@
+{
+  "$schema": "https://glama.ai/mcp/schemas/server.json",
+  "maintainers": ["up2itnow0822"]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentpay-mcp",
-  "version": "4.1.4",
+  "version": "4.1.6",
   "mcpName": "io.github.up2itnow0822/agentpay",
   "description": "AgentPay MCP Server - Non-custodial x402 payment layer for AI agents. Multi-chain wallets, spending limits, and machine-to-machine payments. Patent Pending.",
   "main": "dist/index.js",
@@ -13,7 +13,11 @@
     "README.md",
     "claude_desktop_config.json",
     ".env.example",
-    "docs/*.md"
+    "docs/*.md",
+    "Dockerfile",
+    "smithery.yaml",
+    "glama.json",
+    "docs/directory-introspection-readiness.md"
   ],
   "scripts": {
     "build": "tsc",
@@ -46,7 +50,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "https://github.com/up2itnow0822/agentpay-mcp"
+    "url": "git+https://github.com/up2itnow0822/agentpay-mcp.git"
   },
   "author": "AgentNexus",
   "engines": {
@@ -54,7 +58,7 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.0.4",
-    "agentwallet-sdk": "^6.1.0",
+    "agentwallet-sdk": "^6.2.1",
     "viem": "^2.47.12",
     "zod": "^3.22.4"
   },

package/smithery.yaml

@@ -0,0 +1,37 @@
+# Smithery deployment config for AgentPay MCP
+# Catalog metadata only. AgentPay MCP remains non-custodial: users provide their own wallet key and wallet address.
+
+runtime: typescript
+startCommand:
+  type: stdio
+  command: node
+  args: ["dist/index.js"]
+configSchema:
+  type: object
+  required:
+    - AGENT_PRIVATE_KEY
+    - AGENT_WALLET_ADDRESS
+  properties:
+    AGENT_PRIVATE_KEY:
+      type: string
+      title: Agent private key
+      description: User-controlled 0x-prefixed agent hot wallet private key. Keep this local to the MCP runtime.
+      format: password
+    AGENT_WALLET_ADDRESS:
+      type: string
+      title: Agent wallet address
+      description: Deployed AgentAccountV2 contract address controlled by the operator.
+    CHAIN_ID:
+      type: string
+      title: Chain ID
+      description: Supported x402 exact-payment chain. Defaults to Base mainnet.
+      enum: ["8453", "84532"]
+      default: "8453"
+    RPC_URL:
+      type: string
+      title: RPC URL
+      description: Optional RPC endpoint. Defaults to public Base RPC when omitted.
+    SESSION_TTL_SECONDS:
+      type: string
+      title: Session TTL seconds
+      description: Optional x402 session token TTL. Defaults to 3600 seconds.