paygate-mcp 0.1.2 → 0.1.3

package/README.md

@@ -155,6 +155,15 @@ const { port, adminKey } = await server.start();
 - Admin key never exposed in responses
 - Rate limiting is per-key, concurrent-safe
 
+## Current Limitations
+
+- **In-memory storage** — All API keys, credits, and usage data live in memory. Restarting the server resets everything. This is fine for development and testing.
+- **Credits are not real money** — Credits are just integers. There is no payment processor integration yet.
+- **Single process** — No clustering or horizontal scaling.
+- **Stdio transport only** — The wrapped MCP server must use stdio (most do).
+
+Persistent storage and Stripe integration are on the roadmap.
+
 ## Requirements
 
 - Node.js >= 18.0.0

package/dist/cli.js

@@ -163,7 +163,7 @@ async function main() {
         case 'version':
         case '--version':
         case '-v':
-            console.log('paygate-mcp v0.1.2');
+            console.log('paygate-mcp v0.1.3');
             break;
         default:
             console.error(`Unknown command: ${command}\n`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paygate-mcp",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Pay-per-tool-call gating proxy for MCP servers. Wrap any MCP server with API key auth, per-tool pricing, rate limiting, and usage metering.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -25,5 +25,6 @@
   },
   "keywords": ["mcp", "paygate", "monetize", "pay-per-call", "api-key", "rate-limit", "model-context-protocol", "ai-agent", "billing"],
   "license": "MIT",
+  "homepage": "https://paygated.dev",
   "engines": { "node": ">=18.0.0" }
 }