{"repo":"genesiscode2026/genesis-mcp-production-readiness","private":true,"description":null,"default_branch":"main","stars":0,"forks":0,"pushed_at":"2026-09-17T10:21:38Z","languages":{"JavaScript":13587},"files":13,"tree":[".gitignore","CHANGELOG.md","LICENSE","QUICKSTART.md","README.md","SECURITY.md","VERSION","bin/genesis-mcp-readiness.js","package.json","src/harness.js","src/index.js","tests/fixtures/mock_mcp_server/server.js","tests/test_harness.js"],"sizes":{".gitignore":103,"CHANGELOG.md":588,"LICENSE":961,"QUICKSTART.md":476,"README.md":3015,"SECURITY.md":274,"VERSION":6,"bin/genesis-mcp-readiness.js":2781,"package.json":701,"src/harness.js":8806,"src/index.js":119,"tests/fixtures/mock_mcp_server/server.js":2253,"tests/test_harness.js":1881},"readme":"# Genesis MCP Production Readiness Kit\n\nDeterministic pre-production stress-testing, protocol conformance, and vulnerability audit harness for Model Context Protocol (MCP) servers.\n\n---\n\n### 1. What Problem Does This Solve?\nDeploying an MCP server into production coding agents (Codex, Claude, Cursor) frequently triggers severe runtime failures:\n- Broken JSON-RPC 2.0 framing that hangs agent sessions indefinitely.\n- Invalid or incomplete JSON Schema definitions in `tools/list` that cause LLMs to generate malformed tool calls.\n- Process crashes when agents pass unexpected arguments or invoke nonexistent tools.\n- Deadlocks under parallel concurrent tool calls.\n- Accidental leakage of internal environment variables and secret tokens in error traces.\n\n`genesis-mcp-production-readiness` automates pre-deployment certification via automated protocol negotiation, schema validation, parallel stress testing, and response payload auditing.\n\n### 2. Who Buys It?\n- Developers and enterprise teams building custom MCP servers in Node, Python, Go, or Rust.\n- Platform engineers certifying third-party MCP servers before organization-wide rollout.\n- Devops teams building CI/CD test gates for autonomous agent tooling.\n\n### 3. What Does It Output?\n- Human-readable terminal conformance scorecard with exact protocol traces.\n- Machine-readable JSON output (`--json`) with exit code `0` (PASS) or `1` (FAIL) for CI/CD automation.\n\n### 4. How Fast Can You Test It?\nUnder 5 seconds. Run:\n```bash\n./bin/genesis-mcp-readiness.js --server \"node ./tests/fixtures/mock_mcp_server/server.js\"\n```\n\n### 5. Why Is This Different From Runtime Gateways?\nRuntime gateways (like MCP Agent Security Gateway) proxy calls during live agent execution. `genesis-mcp-production-readiness` is a **pre-production testing harness** that rigorously stress-tests and audits your server *before* an agent ever interacts with it.\n\n---\n\n## Installation & Usage\n\n```bash\n# Audit a local Node.js MCP server\nnpx genesis-mcp-readiness --server \"node ./dist/index.js\"\n\n# Audit a Python MCP server\nnpx genesis-mcp-readiness --server \"python3 -m my_mcp_package\"\n\n# Output machine-readable JSON for CI pipelines\nnpx genesis-mcp-readiness --server \"npx my-mcp-server\" --json\n```\n\n## Checks Executed\n\n| Check ID | Phase | Evaluation Description |\n| :--- | :---: | :--- |\n| `PROC_START` | Stdio Binding | Verifies standard input/output pipes open cleanly without crash |\n| `PROTO_INIT` | Handshake | Validates protocol version negotiation and capability declaration |\n| `TOOLS_SCHEMA`| Schema Audit | Validates JSON Schema compliance for all advertised tool parameters |\n| `ERROR_HANDLING` | Fault Tolerance | Confirms graceful JSON-RPC error returns on nonexistent tools |\n| `CONCURRENCY_LOAD`| Stress Test | Fires parallel requests to verify frame ordering and lock freedom |\n| `SECRET_AUDIT`| Leak Prevention | Audits server output buffers against API key and private key patterns |\n\n## License\nCommercial — Genesis Code (genesiscode2026). See `LICENSE`.\n","price_usd":"79.00","clone_checkout":"https://api.checkout402.com/c/chk_hivxWZZ8h5k1Zkqy","rehearse_checkout":"https://api.checkout402.com/c/chk_hivxWZZ8h5k1Zkqy/test","preview":"/r/genesiscode2026/genesis-mcp-production-readiness/f/<path> serves file CONTENTS for the seller's preview paths; other paths answer with the price","how_to_buy":"pay clone_checkout with x402 (pay402 does it in one call); the goods arrive as payload_base64, a tar.gz of the full repo. Rehearse first at rehearse_checkout: same flow, simulated money.","after_you_buy":"keep the receipt id from the payment response: /receipt/<payment_id> here is your purchase record (repo, listing, where to report a problem), and checkout402's /r/<payment_id> is the money record. Tell your human both URLs."}