sniffmcp-cli 0.4.1__py3-none-any.whl

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,265 @@
1
+ Metadata-Version: 2.4
2
+ Name: sniffmcp-cli
3
+ Version: 0.4.1
4
+ Summary: Audit the MCP servers installed in your agent: injection, credentials, pinning, and post-install drift.
5
+ License-Expression: Apache-2.0
6
+ Project-URL: Homepage, https://github.com/SomehowLiving/sniffmcp
7
+ Project-URL: Issues, https://github.com/SomehowLiving/sniffmcp/issues
8
+ Project-URL: Changelog, https://github.com/SomehowLiving/sniffmcp/blob/main/CHANGELOG.md
9
+ Keywords: mcp,model-context-protocol,security,scanner,ai-agents,supply-chain,prompt-injection
10
+ Classifier: Development Status :: 3 - Alpha
11
+ Classifier: Environment :: Console
12
+ Classifier: Intended Audience :: Developers
13
+ Classifier: Topic :: Security
14
+ Classifier: Programming Language :: Python :: 3
15
+ Classifier: Programming Language :: Python :: 3.11
16
+ Classifier: Programming Language :: Python :: 3.12
17
+ Classifier: Programming Language :: Python :: 3.13
18
+ Requires-Python: >=3.11
19
+ Description-Content-Type: text/markdown
20
+ License-File: LICENSE
21
+ Requires-Dist: mcp<3,>=2.3
22
+ Provides-Extra: dev
23
+ Requires-Dist: pytest>=8; extra == "dev"
24
+ Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
25
+ Provides-Extra: bench
26
+ Requires-Dist: yara-python>=4.5; extra == "bench"
27
+ Dynamic: license-file
28
+
29
+ <p align="center">
30
+ <img src="assets/logo.png" alt="SniffMCP: a raccoon detective with a magnifying glass inspecting an MCP cube" width="360">
31
+ </p>
32
+
33
+ <h1 align="center">SniffMCP</h1>
34
+
35
+ <p align="center"><b>Sniff out what your AI tools are hiding.</b><br>
36
+ Local security checks for the MCP servers plugged into your AI agent.</p>
37
+
38
+ SniffMCP connects to every MCP server in your Claude Code, Claude Desktop, Cursor or
39
+ Windsurf config the way your client does, reads everything the model will read, and tells
40
+ you what's risky:
41
+
42
+ - 🕵️ **Hidden instructions** in tool descriptions, parameter descriptions, prompts and server instructions
43
+ - ☠️ **Known malware and vulnerabilities** in the package that would launch, checked against [OSV.dev](https://osv.dev) **before it runs**
44
+ - 🔑 **Plaintext credentials** in your client config (always redacted in output)
45
+ - 📌 **Unpinned launches** (`npx pkg`, `uvx pkg`, `image:latest`)
46
+ - ⚙️ **Powerful capabilities** worth keeping approval on, and annotations that misstate a tool as read-only
47
+ - 🧬 **Post-install changes** (rug pulls), classified as *risky*, *breaking* or *benign*, so a wording tweak doesn't page you and a new hidden instruction does
48
+
49
+ No account. Nothing uploaded. One runtime dependency (the official MCP SDK).
50
+
51
+ ## Quickstart
52
+
53
+ ```bash
54
+ uvx sniffmcp-cli fleet # run once, no install (Python 3.11+, uv)
55
+ pipx install sniffmcp-cli # or install: gives you the `sniffmcp` command
56
+ sniffmcp fleet # scan every server in your client configs
57
+ ```
58
+
59
+ The PyPI package is `sniffmcp-cli` (PyPI reserves names too similar to an unrelated
60
+ existing project); the command, module and repo are `sniffmcp`.
61
+
62
+ ```text
63
+ $ sniffmcp scan '{"command":"npx","args":["-y","@modelcontextprotocol/server-memory"]}'
64
+
65
+ npx -y @modelcontextprotocol/server-memory
66
+ score 89/100 grade B (9 tools)
67
+ critical:0 high:0 medium:1 low:1 info:2
68
+ [medium ] SM-07 npm package launched without an exact version
69
+ @modelcontextprotocol/server-memory
70
+ [low ] SM-04 Has destructive tools
71
+ delete_entities, delete_observations, delete_relations
72
+ ```
73
+
74
+ Known malware is reported **without ever being launched**:
75
+
76
+ ```text
77
+ $ sniffmcp scan '{"command":"npx","args":["-y","@callcenter-frontend/api@99.0.2025091-3.10"]}'
78
+
79
+ score 34/100 grade F (0 tools)
80
+ [critical] SM-11 Known malicious package: @callcenter-frontend/api@99.0.2025091-3.10
81
+ MAL-2025-41825 — Malicious code in @callcenter-frontend/api (npm)
82
+ ```
83
+
84
+ ## Commands
85
+
86
+ ```bash
87
+ sniffmcp fleet # every installed server (Claude Code incl. per-project, Claude Desktop, Cursor, Windsurf, .mcp.json)
88
+ sniffmcp scan https://mcp.example.com/mcp # one remote server
89
+ sniffmcp scan cfg.json --format sarif --output results.sarif # GitHub code scanning
90
+ sniffmcp fleet .mcp.json --no-launch --format sarif --output r.sarif # CI: never start servers from an untrusted config
91
+ sniffmcp scan cfg.json --baseline last.json --fail-on high # CI gate; known findings don't fail
92
+ sniffmcp watch cfg.json --name memory --webhook https://hooks.slack.com/... # baseline + watch
93
+ sniffmcp watch --name memory --accept # accept the current version after review
94
+ sniffmcp watch --run # check every watch on its interval
95
+ sniffmcp crawl run --output reports/crawl.md # ecosystem crawler (see below)
96
+ ```
97
+
98
+ Exit codes: `0` clean · `1` finding at/above `--fail-on` · `2` bad config · `3` some servers not analysed.
99
+ `--offline` skips OSV lookups.
100
+
101
+ > **Scanning a stdio server runs its command**, exactly as your client does at startup.
102
+ > sniffmcp checks the package against OSV first and refuses to launch known malware,
103
+ > but only scan configs you would run anyway.
104
+
105
+ ### In GitHub Actions
106
+
107
+ Teams commit `.mcp.json` (Claude Code's project servers) and `.cursor/mcp.json` to their repos.
108
+ Audit them on every pull request, with findings shown on the exact line of the config:
109
+
110
+ ```yaml
111
+ name: sniffmcp
112
+ on: [pull_request, push]
113
+ permissions:
114
+ contents: read
115
+ security-events: write # for code scanning upload
116
+ jobs:
117
+ audit:
118
+ runs-on: ubuntu-latest
119
+ steps:
120
+ - uses: actions/checkout@v4
121
+ - uses: SomehowLiving/sniffmcp@v0.4.0
122
+ with:
123
+ config: .mcp.json .cursor/mcp.json
124
+ fail-on: high
125
+ ```
126
+
127
+ By default the action **does not start any server** (`launch: false`): a pull request could
128
+ add a server whose command is the attack. It runs the config checks (secrets, pinning,
129
+ `curl | sh`, plain HTTP) and OSV malware/vulnerability lookups, and connects to remote URLs.
130
+ It writes a job summary table and SARIF for code scanning. Inputs: `config`, `fail-on`,
131
+ `launch`, `offline`, `fail-on-unreachable`, `sarif-file`, `upload-sarif`.
132
+
133
+ ### Inside your agent
134
+
135
+ ```bash
136
+ claude mcp add sniffmcp -- /path/to/sniffmcp/.venv/bin/python -m sniffmcp.server
137
+ ```
138
+
139
+ Tools: `list_installed_servers`, `scan_server`, `score_server`, `scan_all_installed`,
140
+ `analyze_tool_descriptions`, `watch_server`, `list_watches`.
141
+
142
+ A model-callable "scan this command" tool would be a remote-code-execution hole, so in
143
+ server mode targets must be servers already in your configs, or https URLs. Arbitrary
144
+ commands need `SNIFFMCP_ALLOW_COMMANDS=1`. HTTP mode binds to localhost only.
145
+
146
+ ## Checks
147
+
148
+ | ID | What it catches | OWASP MCP Top 10 |
149
+ |---|---|---|
150
+ | INJ-HEUR | Instruction overrides, self-referential concealment ("don't tell the user about this step"), paired fake `<IMPORTANT>` tags, credential-path targeting, exfiltration ("send the contents of X to https://…"), base64 payloads, hidden Unicode, instructions to write into the agent's own config (skills, CLAUDE.md, AGENTS.md). Covers descriptions, titles and every nested parameter description | MCP03, MCP06 |
151
+ | SM-01 | The same, in server-level instructions | MCP03, MCP06 |
152
+ | SM-02 | Credentials in args or URLs (high), or in config env/headers (medium). `${VAR}` references are fine | MCP01 |
153
+ | SM-03 | Post-install drift: risky / breaking / benign | MCP03, MCP04 |
154
+ | SM-04 | Command-execution and destructive tools; read-only claims contradicted by the tool name | MCP02, MCP05 |
155
+ | SM-05 | Tools that read secrets or the environment; resources at real secret paths | MCP10, MCP01 |
156
+ | SM-06 | Remote servers over plain HTTP | MCP07 |
157
+ | SM-07 | Package runners without an exact version; images without a digest | MCP04 |
158
+ | SM-08 | Very large tool sets, duplicate tool names | MCP03 |
159
+ | SM-09 | Injection in prompts | MCP03 |
160
+ | SM-10 | `curl \| sh` launch commands, TLS verification disabled | MCP04, MCP07 |
161
+ | SM-11 | **Known malware** (OSV / OpenSSF `MAL-`) for the package that would launch. Blocks the launch | MCP04 |
162
+ | SM-12 | Known vulnerabilities (GHSA / PYSEC / CVE) at the pinned version, or today's latest if unpinned | MCP04 |
163
+ | FLEET-01 | Same tool name exposed by two installed servers (shadowing) | MCP03 |
164
+
165
+ IDs are sniffmcp's own; every finding also carries its OWASP categories (`owasp_mcp` in JSON, tags in SARIF).
166
+ Scoring: 100 minus severity-weighted deductions (25/15/8/3, at most two per check). **Any critical caps the grade at F; any high at C.**
167
+
168
+ ### Precision over noise
169
+
170
+ A scanner that flags everything gets uninstalled. Two rules govern detection here:
171
+
172
+ 1. **Popular legitimate servers must grade A/B.** Being able to write files or run commands is reported, not punished.
173
+ 2. **Every rule must stay silent on the real-world false-positive corpus** in `tests/test_checks.py`: 35 descriptions from live registry servers that once fooled a rule, such as accuracy instructions like "never tell the user the payment cleared", Persian text with zero-width joiners, contact links, public SSH keys, and security tools that *quote* attack phrases.
174
+
175
+ On the 10,409 reachable servers in the official registry (2026-10-09), sniffmcp raises
176
+ high/critical findings on 2. Both were checked by hand and both are real.
177
+
178
+ ## Ecosystem crawler
179
+
180
+ The crawler builds a history of how the public MCP ecosystem changes.
181
+
182
+ ```bash
183
+ sniffmcp crawl run # sync + probe + packages + advisories + report
184
+ sniffmcp crawl sync | probe | packages | advisories | report | rescore
185
+ ```
186
+
187
+ | Stage | What it does |
188
+ |---|---|
189
+ | `sync` | Every latest entry in the official registry (`registry.modelcontextprotocol.io`) |
190
+ | `probe` | Lists tools/resources/prompts on each public remote endpoint; stores a snapshot only when it changes; classifies each change |
191
+ | `packages` | npm/PyPI release history from metadata: install scripts appearing, provenance or trusted publishing dropped, first release by a new publisher without provenance, source-only releases |
192
+ | `advisories` | Every tracked package against OSV: malware in any version, vulnerabilities in the current latest |
193
+ | `report` / `rescore` | Markdown summary; re-grade stored snapshots after a rule change |
194
+
195
+ **Why it runs daily.** npm deletes malicious versions after takedown. On 2026-10-09, OSV listed
196
+ past malware in four registry packages: three from the Shai-Hulud worm campaigns and one fake
197
+ "local-only" scanner. Those versions are already gone from npm metadata. Only a crawler running
198
+ *during* an attack records what happened.
199
+
200
+ **Crawler rules:**
201
+ - Probes public addresses only. Registry entries are untrusted, so nothing that resolves to loopback, LAN or cloud metadata is contacted.
202
+ - List calls only; it never calls a tool.
203
+ - At most 1 probe per endpoint per 20h, 2 at a time per host, 100 per host per run.
204
+ - Endpoints that declare required auth are recorded but not probed.
205
+ - Packages are never downloaded or executed.
206
+ - Data stays local (`~/.sniffmcp/crawl.db`).
207
+
208
+ Daily via cron:
209
+
210
+ ```cron
211
+ 17 6 * * * cd /path/to/sniffmcp && .venv/bin/sniffmcp crawl run --output reports/crawl-$(date +\%F).md >> ~/.sniffmcp/crawl.log 2>&1
212
+ ```
213
+
214
+ ## How it compares
215
+
216
+ We learned a lot from the tools already here, and recommend them for what they do best:
217
+
218
+ | | sniffmcp | [Snyk Agent Scan](https://github.com/snyk/agent-scan) (ex-Invariant mcp-scan) | [Cisco mcp-scanner](https://github.com/cisco-ai-defense/mcp-scanner) | [MCP-Sentinel](https://github.com/BashaarJavaid/MCP-Sentinel) |
219
+ |---|---|---|---|---|
220
+ | Scans | Installed servers, live | Installed servers, live | Servers/tools, live | Server **source** in CI |
221
+ | Detection | Precision-tuned rules + OSV | Hosted analysis + rules | YARA + LLM judge + Cisco AI Defense | AST, Semgrep, LLM, Docker probes |
222
+ | Account / upload | **None, fully local** | Snyk token; tool data sent to Snyk | Local YARA; APIs optional | LLM key for full value |
223
+ | Drift | **Classified**, alert once | Hash pinning | Rug-pull checks | CI baselines |
224
+ | Malware feed | OSV, **checked before launch** | Snyk platform | — | — |
225
+ | Ecosystem dataset | **Daily registry crawl with history** | — | — | — |
226
+ | Sees handler code | ❌ | ❌ | Partly | ✅ |
227
+ | Maturity | New | Most mature (3k+ ★) | ~1k ★ | Early |
228
+
229
+ Head-to-head on the same 10,409 registry servers (`scripts/benchmark_yara.py`): Cisco's YARA
230
+ rules flag 17% of servers, and the hand-checked samples are mostly noise ("assert" triggers
231
+ code execution, "benchmark" triggers SQL injection). But they surfaced one pattern we had missed,
232
+ which is now a rule. Use more than one tool.
233
+
234
+ ## Known limits
235
+
236
+ - **OAuth-protected servers can't be scanned yet.** That's about 36% of registry endpoints.
237
+ - **Manifest only.** We see what a server *says*, not what its handlers *do*. Pair with source scanning for servers you build.
238
+ - **Session-gated payloads evade polling.** A server that turns malicious after N tool calls inside a session shows its clean face to every fresh connection.
239
+ - Heuristics are tuned for precision; a careful attacker can phrase around them.
240
+
241
+ ## Roadmap
242
+
243
+ - OAuth support so auth-gated servers can be scanned
244
+ - A public benchmark corpus (known attacks + real-world false positives) any scanner can be measured against
245
+ - Optional LLM second opinion for ambiguous text (the hook exists: `analyze_descriptions(llm_hook=…)`)
246
+ - A session proxy to catch payloads that only appear mid-session
247
+
248
+ ## Docs
249
+
250
+ - [ARCHITECTURE.md](ARCHITECTURE.md): how it works, with diagrams, the OWASP mapping, and design decisions
251
+ - [CONTRIBUTING.md](CONTRIBUTING.md): dev setup and the rules every detection change must pass
252
+ - [SECURITY.md](SECURITY.md): reporting a vulnerability, and how crawl findings are disclosed
253
+ - [CHANGELOG.md](CHANGELOG.md)
254
+
255
+ ## Acknowledgements
256
+
257
+ - [Invariant Labs](https://invariantlabs.ai) for the tool-poisoning research our regression suite starts from
258
+ - [OSV.dev](https://osv.dev) and the [OpenSSF malicious-packages](https://github.com/ossf/malicious-packages) project for malware and vulnerability data
259
+ - [OWASP MCP Top 10](https://owasp.org/www-project-mcp-top-10/) for the shared risk taxonomy
260
+ - [Cisco AI Defense](https://github.com/cisco-ai-defense/mcp-scanner) for the Apache-2.0 YARA rules we benchmark against (fetched at a pinned commit, not vendored)
261
+ - Pillar Security and the Cloud Security Alliance for the Deadbugz analysis behind the drift checks
262
+
263
+ ## License
264
+
265
+ [Apache-2.0](LICENSE). Mascot and brand artwork in `assets/` are part of the SniffMCP brand.
@@ -0,0 +1,23 @@
1
+ sniffmcp/__init__.py,sha256=HkE2rOZyvR5ljNb4FEcFW8PIttUaVoKXDx82KNMXq4s,85
2
+ sniffmcp/__main__.py,sha256=3dYKHfmWsrdExFlTFlcR5a_icR9fAkn06Yh14TQkEd8,33
3
+ sniffmcp/checks.py,sha256=KnljOXPHARU4KpoW4uqk8pjCCcp8YnjzON2btehvoNk,22839
4
+ sniffmcp/cli.py,sha256=kzcCJK0uk0X4TgX6-coTQSlhvD4eAOfNFt4zKSsvbD8,11155
5
+ sniffmcp/client.py,sha256=7T5PvCri-nC9KYi2pTAYGOtqzaQjgtA5HvuGLGoZSH4,6861
6
+ sniffmcp/crawldb.py,sha256=iJp67WCfWw1-sVoDXiZS7gTvSqdKa7jaIr6qZM9Lcq8,6903
7
+ sniffmcp/crawler.py,sha256=MDH4zRXg-Btwvx9SGkqVwcrwMyia3_uz7lZdvZeXhjo,26303
8
+ sniffmcp/engine.py,sha256=MMACb4GjEI1ZtROyW1BohN44gqS7zH-1LbZu_36u5O0,3246
9
+ sniffmcp/fleet.py,sha256=0O5w3AxC7I3PKZgjMkpy6lQp476voh21gw0ZBChnVMs,8641
10
+ sniffmcp/injection.py,sha256=4p7cizZzt5UzEK4dFUKBUDQymwpxxhxdSpkA-rnowR0,10914
11
+ sniffmcp/models.py,sha256=4Np1OHN_8l7XjDeZsn5uaSWy0OatnvFxHjzCpcvMisA,1971
12
+ sniffmcp/osv.py,sha256=D1iPjGfHoSQP6QCvBpTdHVtlpw1JP4y6jd9WBbDKQyQ,6164
13
+ sniffmcp/report.py,sha256=0kPP1eQ7br0CRoHKmz-fpoM9xxd8Ehn0qganu3bz5gw,10797
14
+ sniffmcp/scoring.py,sha256=fVaToTt7gGlHFjwozxvFPebHR1y0XUMTY3BRt-cMtsw,1443
15
+ sniffmcp/server.py,sha256=ONeSHS8NvRuZ3p2Y4AOoXgwhZLYGU3FLiVl_NIDRHI0,6293
16
+ sniffmcp/state.py,sha256=ngIGOWalMUZt3qIzzeugtVecRfz10GAhdtvlSQPsIZs,4796
17
+ sniffmcp/watcher.py,sha256=X0FskZOx1Qy2mFGcNBez_hJZK6076YDUW7ekAV-dU_8,3981
18
+ sniffmcp_cli-0.4.1.dist-info/licenses/LICENSE,sha256=M_ELi-4dW5lYx2vUZLy0V6jyzxrUVhRuiVSJQ19Nis4,11352
19
+ sniffmcp_cli-0.4.1.dist-info/METADATA,sha256=ZgNGWiRndenk1nvg9NGLCddQGwBm-UmkMfYtHMaRSfs,14314
20
+ sniffmcp_cli-0.4.1.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
21
+ sniffmcp_cli-0.4.1.dist-info/entry_points.txt,sha256=9wT3oJpILjZ6TARYPPFjkAaMb0V1PiaCgi04TwOYnD0,80
22
+ sniffmcp_cli-0.4.1.dist-info/top_level.txt,sha256=ANwFZOrPonOFj8qGOSLOl2h-W1wuV-sa_bnbOcB8jUQ,9
23
+ sniffmcp_cli-0.4.1.dist-info/RECORD,,
@@ -0,0 +1,5 @@
1
+ Wheel-Version: 1.0
2
+ Generator: setuptools (84.0.0)
3
+ Root-Is-Purelib: true
4
+ Tag: py3-none-any
5
+
@@ -0,0 +1,3 @@
1
+ [console_scripts]
2
+ sniffmcp = sniffmcp.cli:main
3
+ sniffmcp-cli = sniffmcp.cli:main
@@ -0,0 +1,202 @@
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
95
+ Derivative 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 SniffMCP contributors
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.
202
+
@@ -0,0 +1 @@
1
+ sniffmcp