mcp-drill 0.0.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or Derivative
95
+ Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Timur Rakhmatullin
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,92 @@
1
+ Metadata-Version: 2.4
2
+ Name: mcp-drill
3
+ Version: 0.0.1
4
+ Summary: Fault injection and reliability scoring for Model Context Protocol (MCP) servers.
5
+ Author: Timur Rakhmatullin
6
+ License: Apache-2.0
7
+ Project-URL: Repository, https://github.com/TimurRakhmatullin86/mcp-drill
8
+ Project-URL: Issues, https://github.com/TimurRakhmatullin86/mcp-drill/issues
9
+ Keywords: mcp,model-context-protocol,fault-injection,chaos-engineering,reliability,testing,llm,agents
10
+ Classifier: Development Status :: 3 - Alpha
11
+ Classifier: Intended Audience :: Developers
12
+ Classifier: License :: OSI Approved :: Apache Software License
13
+ Classifier: Programming Language :: Python :: 3
14
+ Classifier: Topic :: Software Development :: Testing
15
+ Requires-Python: >=3.10
16
+ Description-Content-Type: text/markdown
17
+ License-File: LICENSE
18
+ Provides-Extra: scan
19
+ Requires-Dist: jsonschema>=4.20; extra == "scan"
20
+ Provides-Extra: dev
21
+ Requires-Dist: pytest>=8; extra == "dev"
22
+ Requires-Dist: jsonschema>=4.20; extra == "dev"
23
+ Dynamic: license-file
24
+
25
+ # mcp-drill
26
+
27
+ **Fault injection and reliability testing for MCP servers and AI agents.**
28
+ Wrap any Model Context Protocol server in one command; inject timeouts, malformed JSON-RPC,
29
+ truncated and corrupted-but-valid tool outputs; measure whether the server degrades cleanly —
30
+ and whether your agent *notices* or silently acts on the garbage.
31
+
32
+ ```bash
33
+ uvx mcp-drill wrap --faults timeout,corrupt -- npx -y @modelcontextprotocol/server-filesystem /tmp
34
+ ```
35
+
36
+ MCP is JSON-RPC over stdio/SSE with bidirectional notifications, so ordinary HTTP fault-injectors
37
+ and chaos tools don't fit. `mcp-drill` speaks MCP: it sits transparently between an MCP client and
38
+ a backend server and perturbs the traffic, so you can test failure paths in CI without a live LLM.
39
+
40
+ ## Why
41
+
42
+ Real MCP deployments fail in ways integration tests never cover: a tool times out, a server
43
+ returns a well-formed-but-wrong payload, a response is truncated mid-stream. Most agents were
44
+ never exercised against these paths. `mcp-drill` makes them reproducible:
45
+
46
+ - 🧪 **Fault injection** — deterministically inject timeouts, malformed/oversized/truncated
47
+ responses, corrupted-but-schema-valid payloads, dropped tools, and latency.
48
+ - 🎬 **CI-first** — a CLI and a GitHub Action; no live model or API keys required in the loop.
49
+ - 📊 **Reliability scorecard** — a model-free scan that grades how a server responds to bad
50
+ input and how machine-checkable its tool output contracts are.
51
+
52
+ ## Install
53
+
54
+ Until the first PyPI release, install from source:
55
+
56
+ ```bash
57
+ pip install "mcp-drill[scan] @ git+https://github.com/TimurRakhmatullin86/mcp-drill"
58
+ ```
59
+
60
+ ## Quickstart
61
+
62
+ ```bash
63
+ # wrap a server and inject faults into its responses
64
+ mcp-drill wrap --faults timeout,truncate -- npx -y @modelcontextprotocol/server-everything
65
+
66
+ # score a server's fault handling and output-schema hygiene (no LLM involved)
67
+ mcp-drill scan -- npx -y @modelcontextprotocol/server-filesystem /tmp
68
+ ```
69
+
70
+ ## What it measures (model-free)
71
+
72
+ The `scan` command is deterministic and involves no language model, so its numbers are properties
73
+ of the server and the protocol — not of whichever agent happens to call it:
74
+
75
+ 1. **Error conformance** — on invalid requests (unknown method, unknown tool, missing required
76
+ arguments), does the server return a spec-compliant JSON-RPC error, a proper tool error, or
77
+ does it hang / crash / answer as if nothing was wrong?
78
+ 2. **Output-contract coverage** — what fraction of a server's tools declare a machine-checkable
79
+ `outputSchema` at all? Tools without one give downstream validators nothing to check.
80
+ 3. **Output-contract enforceability** — of the tools that declare an `outputSchema`, how many would
81
+ actually *reject* a corrupted (well-typed but wrong) response? Many declared schemas validate
82
+ shape only, so a corrupted payload still passes the server's own contract.
83
+
84
+ ## Status
85
+
86
+ Early development. The proxy/injector core is pure-stdlib; schema scoring uses `jsonschema`
87
+ (the `scan` extra). Install from source until the first PyPI release. Telemetry is **off** —
88
+ the tool never phones home.
89
+
90
+ ## License
91
+
92
+ Apache-2.0 (see `LICENSE`).
@@ -0,0 +1,68 @@
1
+ # mcp-drill
2
+
3
+ **Fault injection and reliability testing for MCP servers and AI agents.**
4
+ Wrap any Model Context Protocol server in one command; inject timeouts, malformed JSON-RPC,
5
+ truncated and corrupted-but-valid tool outputs; measure whether the server degrades cleanly —
6
+ and whether your agent *notices* or silently acts on the garbage.
7
+
8
+ ```bash
9
+ uvx mcp-drill wrap --faults timeout,corrupt -- npx -y @modelcontextprotocol/server-filesystem /tmp
10
+ ```
11
+
12
+ MCP is JSON-RPC over stdio/SSE with bidirectional notifications, so ordinary HTTP fault-injectors
13
+ and chaos tools don't fit. `mcp-drill` speaks MCP: it sits transparently between an MCP client and
14
+ a backend server and perturbs the traffic, so you can test failure paths in CI without a live LLM.
15
+
16
+ ## Why
17
+
18
+ Real MCP deployments fail in ways integration tests never cover: a tool times out, a server
19
+ returns a well-formed-but-wrong payload, a response is truncated mid-stream. Most agents were
20
+ never exercised against these paths. `mcp-drill` makes them reproducible:
21
+
22
+ - 🧪 **Fault injection** — deterministically inject timeouts, malformed/oversized/truncated
23
+ responses, corrupted-but-schema-valid payloads, dropped tools, and latency.
24
+ - 🎬 **CI-first** — a CLI and a GitHub Action; no live model or API keys required in the loop.
25
+ - 📊 **Reliability scorecard** — a model-free scan that grades how a server responds to bad
26
+ input and how machine-checkable its tool output contracts are.
27
+
28
+ ## Install
29
+
30
+ Until the first PyPI release, install from source:
31
+
32
+ ```bash
33
+ pip install "mcp-drill[scan] @ git+https://github.com/TimurRakhmatullin86/mcp-drill"
34
+ ```
35
+
36
+ ## Quickstart
37
+
38
+ ```bash
39
+ # wrap a server and inject faults into its responses
40
+ mcp-drill wrap --faults timeout,truncate -- npx -y @modelcontextprotocol/server-everything
41
+
42
+ # score a server's fault handling and output-schema hygiene (no LLM involved)
43
+ mcp-drill scan -- npx -y @modelcontextprotocol/server-filesystem /tmp
44
+ ```
45
+
46
+ ## What it measures (model-free)
47
+
48
+ The `scan` command is deterministic and involves no language model, so its numbers are properties
49
+ of the server and the protocol — not of whichever agent happens to call it:
50
+
51
+ 1. **Error conformance** — on invalid requests (unknown method, unknown tool, missing required
52
+ arguments), does the server return a spec-compliant JSON-RPC error, a proper tool error, or
53
+ does it hang / crash / answer as if nothing was wrong?
54
+ 2. **Output-contract coverage** — what fraction of a server's tools declare a machine-checkable
55
+ `outputSchema` at all? Tools without one give downstream validators nothing to check.
56
+ 3. **Output-contract enforceability** — of the tools that declare an `outputSchema`, how many would
57
+ actually *reject* a corrupted (well-typed but wrong) response? Many declared schemas validate
58
+ shape only, so a corrupted payload still passes the server's own contract.
59
+
60
+ ## Status
61
+
62
+ Early development. The proxy/injector core is pure-stdlib; schema scoring uses `jsonschema`
63
+ (the `scan` extra). Install from source until the first PyPI release. Telemetry is **off** —
64
+ the tool never phones home.
65
+
66
+ ## License
67
+
68
+ Apache-2.0 (see `LICENSE`).
@@ -0,0 +1,49 @@
1
+ [build-system]
2
+ requires = ["setuptools>=68"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "mcp-drill"
7
+ version = "0.0.1"
8
+ description = "Fault injection and reliability scoring for Model Context Protocol (MCP) servers."
9
+ readme = "README.md"
10
+ requires-python = ">=3.10"
11
+ license = { text = "Apache-2.0" }
12
+ authors = [{ name = "Timur Rakhmatullin" }]
13
+ keywords = [
14
+ "mcp",
15
+ "model-context-protocol",
16
+ "fault-injection",
17
+ "chaos-engineering",
18
+ "reliability",
19
+ "testing",
20
+ "llm",
21
+ "agents",
22
+ ]
23
+ classifiers = [
24
+ "Development Status :: 3 - Alpha",
25
+ "Intended Audience :: Developers",
26
+ "License :: OSI Approved :: Apache Software License",
27
+ "Programming Language :: Python :: 3",
28
+ "Topic :: Software Development :: Testing",
29
+ ]
30
+ dependencies = [] # the proxy/injector core is pure-stdlib
31
+
32
+ [project.optional-dependencies]
33
+ # Schema-conformance scoring needs a JSON Schema validator.
34
+ scan = ["jsonschema>=4.20"]
35
+ dev = ["pytest>=8", "jsonschema>=4.20"]
36
+
37
+ [project.urls]
38
+ Repository = "https://github.com/TimurRakhmatullin86/mcp-drill"
39
+ Issues = "https://github.com/TimurRakhmatullin86/mcp-drill/issues"
40
+
41
+ [project.scripts]
42
+ mcp-drill = "mcp_drill.cli:main"
43
+
44
+ [tool.setuptools.packages.find]
45
+ where = ["src"]
46
+
47
+ [tool.pytest.ini_options]
48
+ pythonpath = ["src"]
49
+ testpaths = ["tests"]
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
@@ -0,0 +1,4 @@
1
+ """mcp-drill: fault injection and reliability scoring for MCP servers."""
2
+ from __future__ import annotations
3
+
4
+ __version__ = "0.0.1"
@@ -0,0 +1,130 @@
1
+ """Command-line entry point: `mcp-drill wrap|scan|faults|version`."""
2
+ from __future__ import annotations
3
+
4
+ import argparse
5
+ import json
6
+ import sys
7
+
8
+ from . import __version__, faults
9
+ from .proxy import FaultProxy, build_specs
10
+ from .scorecard import ServerScore, scan_server
11
+
12
+
13
+ def _split_server_command(argv: list[str]) -> tuple[list[str], list[str]]:
14
+ """Everything after a standalone ``--`` is the server command to launch."""
15
+ if "--" in argv:
16
+ i = argv.index("--")
17
+ return argv[:i], argv[i + 1:]
18
+ return argv, []
19
+
20
+
21
+ def _parse_fault_list(spec: str) -> list[str]:
22
+ spec = spec.strip()
23
+ if not spec:
24
+ return []
25
+ parts = spec.split(";") if ":" in spec else spec.split(",")
26
+ return [p.strip() for p in parts if p.strip()]
27
+
28
+
29
+ def _build_parser() -> argparse.ArgumentParser:
30
+ parser = argparse.ArgumentParser(
31
+ prog="mcp-drill",
32
+ description="Fault injection and reliability scoring for MCP servers.",
33
+ epilog="Put the server command after `--`, e.g. mcp-drill scan -- npx -y some-mcp-server",
34
+ )
35
+ sub = parser.add_subparsers(dest="cmd", required=True)
36
+
37
+ wrap = sub.add_parser("wrap", help="proxy a server and inject faults into its responses")
38
+ wrap.add_argument("--faults", default="", metavar="LIST",
39
+ help="faults to inject, e.g. 'timeout,corrupt' or 'latency:seconds=2;truncate'")
40
+ wrap.add_argument("--only", default="tools/call", metavar="METHODS",
41
+ help="comma-separated methods whose responses may be faulted")
42
+ wrap.add_argument("-p", "--probability", type=float, default=1.0,
43
+ help="probability [0..1] that a targeted response is faulted")
44
+ wrap.add_argument("--seed", type=int, default=None, help="RNG seed for reproducible runs")
45
+
46
+ scan = sub.add_parser("scan", help="score a server's fault handling and schema hygiene (no LLM)")
47
+ scan.add_argument("--json", action="store_true", help="emit the full score as JSON")
48
+ scan.add_argument("--timeout", type=float, default=20.0, help="per-request timeout in seconds")
49
+ scan.add_argument("--name", default=None, help="label for the server in the report")
50
+
51
+ sub.add_parser("faults", help="list the available fault types")
52
+ sub.add_parser("version", help="print the version")
53
+ return parser
54
+
55
+
56
+ def _print_report(score: ServerScore) -> None:
57
+ info = score.server_info or {}
58
+ label = info.get("name") or score.name
59
+ print(f"mcp-drill scan — {label} {info.get('version', '')}".rstrip())
60
+ print(f" handshake : {'ok' if score.handshake_ok else 'FAILED'}"
61
+ + (f" (protocol {score.protocol_version})" if score.protocol_version else ""))
62
+ if not score.handshake_ok:
63
+ for note in score.notes:
64
+ print(f" note : {note}")
65
+ return
66
+ cov = score.output_schema_coverage
67
+ enf = score.enforceable_rate
68
+ ca = score.corruption_acceptance_rate
69
+ ehs = score.error_handling_score
70
+ print(f" tools : {score.n_tools}")
71
+ print(f" output-schema : {_pct(cov)} of tools declare one"
72
+ f" ({score.tools_with_output_schema}/{score.n_tools})")
73
+ print(f" enforceable : {_pct(enf)} of tools declare a schema that rejects a corrupted"
74
+ f" response ({score.enforceable_output_schemas}/{score.n_tools})")
75
+ if score.tools_with_output_schema:
76
+ print(f" vacuous schemas : {_pct(ca)} of declared schemas still validate a corrupted"
77
+ f" payload ({score.vacuous_output_schemas}/{score.tools_with_output_schema})")
78
+ if score.fastmcp_wrapped_tools:
79
+ print(f" fastmcp-wrapped : {score.fastmcp_wrapped_tools} tool(s) carry x-fastmcp-wrap-result")
80
+ print(f" error handling : {_pct(ehs)} of bad-input probes handled cleanly")
81
+ for probe, verdict in score.probes.items():
82
+ print(f" - {probe:<22}: {verdict}")
83
+ for note in score.notes:
84
+ print(f" note : {note}")
85
+
86
+
87
+ def _pct(value: float | None) -> str:
88
+ return "n/a" if value is None else f"{value * 100:.0f}%"
89
+
90
+
91
+ def main(argv: list[str] | None = None) -> int:
92
+ argv = list(sys.argv[1:] if argv is None else argv)
93
+ argv, server_cmd = _split_server_command(argv)
94
+ args = _build_parser().parse_args(argv)
95
+
96
+ if args.cmd == "version":
97
+ print(__version__)
98
+ return 0
99
+ if args.cmd == "faults":
100
+ print("\n".join(faults.names()))
101
+ return 0
102
+
103
+ if not server_cmd:
104
+ print("error: provide the server command after `--`", file=sys.stderr)
105
+ return 2
106
+
107
+ if args.cmd == "wrap":
108
+ specs = build_specs(_parse_fault_list(args.faults))
109
+ proxy = FaultProxy(
110
+ server_cmd,
111
+ specs,
112
+ target_methods=tuple(m.strip() for m in args.only.split(",") if m.strip()),
113
+ probability=args.probability,
114
+ seed=args.seed,
115
+ )
116
+ return proxy.run()
117
+
118
+ if args.cmd == "scan":
119
+ score = scan_server(args.name or server_cmd[-1], server_cmd, timeout=args.timeout)
120
+ if args.json:
121
+ print(json.dumps(score.to_dict(), indent=2, ensure_ascii=False))
122
+ else:
123
+ _print_report(score)
124
+ return 0
125
+
126
+ return 2
127
+
128
+
129
+ if __name__ == "__main__":
130
+ raise SystemExit(main())