mcp-drift-watch 0.1.0__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.
- mcp_drift_watch-0.1.0/LICENSE +202 -0
- mcp_drift_watch-0.1.0/PKG-INFO +128 -0
- mcp_drift_watch-0.1.0/docs/pypi.md +86 -0
- mcp_drift_watch-0.1.0/pyproject.toml +91 -0
- mcp_drift_watch-0.1.0/pyproject.toml.orig +86 -0
- mcp_drift_watch-0.1.0/src/driftwatch/__init__.py +8 -0
- mcp_drift_watch-0.1.0/src/driftwatch/__main__.py +5 -0
- mcp_drift_watch-0.1.0/src/driftwatch/alerts.py +541 -0
- mcp_drift_watch-0.1.0/src/driftwatch/approve.py +151 -0
- mcp_drift_watch-0.1.0/src/driftwatch/canonical.py +167 -0
- mcp_drift_watch-0.1.0/src/driftwatch/cli.py +1060 -0
- mcp_drift_watch-0.1.0/src/driftwatch/collect.py +173 -0
- mcp_drift_watch-0.1.0/src/driftwatch/config.py +123 -0
- mcp_drift_watch-0.1.0/src/driftwatch/conform.py +592 -0
- mcp_drift_watch-0.1.0/src/driftwatch/db.py +414 -0
- mcp_drift_watch-0.1.0/src/driftwatch/diff.py +669 -0
- mcp_drift_watch-0.1.0/src/driftwatch/evaluate.py +428 -0
- mcp_drift_watch-0.1.0/src/driftwatch/explain.py +523 -0
- mcp_drift_watch-0.1.0/src/driftwatch/export.py +156 -0
- mcp_drift_watch-0.1.0/src/driftwatch/gateway.py +927 -0
- mcp_drift_watch-0.1.0/src/driftwatch/guard.py +435 -0
- mcp_drift_watch-0.1.0/src/driftwatch/pin.py +251 -0
- mcp_drift_watch-0.1.0/src/driftwatch/render.py +415 -0
- mcp_drift_watch-0.1.0/src/driftwatch/review.py +707 -0
- mcp_drift_watch-0.1.0/src/driftwatch/rules/conformance-2026-07-28.yaml +196 -0
- mcp_drift_watch-0.1.0/src/driftwatch/rules/owasp-mcp-top10.yaml +79 -0
- mcp_drift_watch-0.1.0/src/driftwatch/schedule.py +123 -0
- mcp_drift_watch-0.1.0/src/driftwatch/textscan.py +135 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/__init__.py +5 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/app.py +301 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/present.py +214 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/static/htmx-2.0.11.min.js +1 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/static/htmx-LICENSE.txt +13 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/static/style.css +185 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/_alerts_table.html +30 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/_flags.html +14 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/_freshness.html +3 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/_servers_table.html +26 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/_side_by_side.html +13 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/alerts.html +10 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/base.html +28 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/conformance.html +32 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/error.html +7 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/server.html +159 -0
- mcp_drift_watch-0.1.0/src/driftwatch/web/templates/servers.html +13 -0
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,128 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: mcp-drift-watch
|
|
3
|
+
Version: 0.1.0
|
|
4
|
+
Summary: Pin approved MCP servers by fingerprint, alert when their tool descriptions change, and keep changed servers frozen until a person re-approves them.
|
|
5
|
+
Keywords: mcp,model-context-protocol,ai-security,tool-poisoning,rug-pull,ai-agents
|
|
6
|
+
Author: hsarikan
|
|
7
|
+
License-Expression: Apache-2.0
|
|
8
|
+
License-File: LICENSE
|
|
9
|
+
Classifier: Development Status :: 3 - Alpha
|
|
10
|
+
Classifier: Environment :: Console
|
|
11
|
+
Classifier: Intended Audience :: Developers
|
|
12
|
+
Classifier: Intended Audience :: System Administrators
|
|
13
|
+
Classifier: Operating System :: OS Independent
|
|
14
|
+
Classifier: Programming Language :: Python :: 3
|
|
15
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
17
|
+
Classifier: Topic :: Security
|
|
18
|
+
Requires-Dist: anthropic>=1
|
|
19
|
+
Requires-Dist: anyio>=4.16
|
|
20
|
+
Requires-Dist: httpx2>=2.16
|
|
21
|
+
Requires-Dist: jsonschema>=4.18
|
|
22
|
+
Requires-Dist: mcp>=2.3.0
|
|
23
|
+
Requires-Dist: mcp-types>=2.3.0
|
|
24
|
+
Requires-Dist: pydantic>=2
|
|
25
|
+
Requires-Dist: python-dotenv>=1
|
|
26
|
+
Requires-Dist: pyyaml>=6
|
|
27
|
+
Requires-Dist: referencing>=0.37
|
|
28
|
+
Requires-Dist: rich>=13
|
|
29
|
+
Requires-Dist: sqlalchemy>=2.0
|
|
30
|
+
Requires-Dist: typer>=0.12
|
|
31
|
+
Requires-Dist: psycopg[binary]>=3.2 ; extra == 'postgres'
|
|
32
|
+
Requires-Dist: fastapi>=0.115 ; extra == 'web'
|
|
33
|
+
Requires-Dist: jinja2>=3.1 ; extra == 'web'
|
|
34
|
+
Requires-Dist: markupsafe>=3.0 ; extra == 'web'
|
|
35
|
+
Requires-Dist: python-multipart>=0.0.18 ; extra == 'web'
|
|
36
|
+
Requires-Dist: starlette>=1.10 ; extra == 'web'
|
|
37
|
+
Requires-Dist: uvicorn>=0.30 ; extra == 'web'
|
|
38
|
+
Requires-Python: >=3.12
|
|
39
|
+
Provides-Extra: postgres
|
|
40
|
+
Provides-Extra: web
|
|
41
|
+
Description-Content-Type: text/markdown
|
|
42
|
+
|
|
43
|
+
# MCP Drift Watch
|
|
44
|
+
|
|
45
|
+
**Your AI agents trust what MCP servers say about their tools. Drift Watch makes sure it's still what you approved.**
|
|
46
|
+
|
|
47
|
+
An MCP server can change its tool descriptions at any time after you approve it: a "rug pull". The AI model reads those descriptions as instructions, so a changed description can tell it to read files or send data somewhere. Nothing in MCP tells you when this happens.
|
|
48
|
+
|
|
49
|
+
Drift Watch pins every approved server by a SHA-256 fingerprint of everything the model reads:
|
|
50
|
+
- the tool names and descriptions
|
|
51
|
+
- the parameters
|
|
52
|
+
- the server's instructions
|
|
53
|
+
- how the server is started or reached
|
|
54
|
+
|
|
55
|
+
When any of it changes, the server is **frozen** and you get an alert. It stays frozen until a person looks at the change and approves or rejects it.
|
|
56
|
+
|
|
57
|
+
## Install
|
|
58
|
+
|
|
59
|
+
```sh
|
|
60
|
+
uv tool install mcp-drift-watch # or: pipx install mcp-drift-watch
|
|
61
|
+
driftwatch --version
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
The package is called `mcp-drift-watch`, and the command is `driftwatch`. A different, unrelated package on PyPI is called `driftwatch`, so `pip install driftwatch` and `uvx driftwatch` install that one, not this.
|
|
65
|
+
|
|
66
|
+
Optional parts:
|
|
67
|
+
- `mcp-drift-watch[web]` adds the review site and the HTTP gateway
|
|
68
|
+
- `mcp-drift-watch[postgres]` adds a hosted Postgres database, instead of a local SQLite file
|
|
69
|
+
|
|
70
|
+
## Quick start
|
|
71
|
+
|
|
72
|
+
List the servers you approved in `servers.yaml`. Write secrets as `${VAR}`: they're read from the environment and never stored.
|
|
73
|
+
|
|
74
|
+
```yaml
|
|
75
|
+
servers:
|
|
76
|
+
- name: notes
|
|
77
|
+
transport: stdio
|
|
78
|
+
command: npx
|
|
79
|
+
args: ["-y", "@example/notes-mcp@1.4.2"] # pin the version
|
|
80
|
+
- name: tickets
|
|
81
|
+
transport: http
|
|
82
|
+
url: https://tickets.example.com/mcp
|
|
83
|
+
headers: {Authorization: "Bearer ${TICKETS_TOKEN}"}
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
```sh
|
|
87
|
+
driftwatch pin servers.yaml # approve what's there now, pinned by fingerprint
|
|
88
|
+
driftwatch check servers.yaml # later: compare with the approved version (exit 1 if anything changed)
|
|
89
|
+
driftwatch diff notes # what changed, with red flags and OWASP MCP Top 10 IDs
|
|
90
|
+
driftwatch approve notes --fingerprint <id> # the id diff shows; or: driftwatch reject notes
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
`check` approves nothing, so it fits a CI job or a cron.
|
|
94
|
+
|
|
95
|
+
## Before you start: what Drift Watch trusts
|
|
96
|
+
|
|
97
|
+
- **`servers.yaml` is like code.** `pin` and `check` start the programs it names, and each `${VAR}` hands that environment variable to them. Only use a `servers.yaml` you trust: never one from someone else's pull request.
|
|
98
|
+
- **A `.env` file in the current folder is read too** (keys and settings). Trust it like `servers.yaml`.
|
|
99
|
+
- **The first `pin` trusts what the server serves at that moment.** It warns about high red flags in that first version, and `driftwatch diff <server>` shows them.
|
|
100
|
+
- **The review site and the HTTP gateway have no sign-in.** They answer only on 127.0.0.1 and refuse web pages, but any program on your computer can use them.
|
|
101
|
+
|
|
102
|
+
## What else is included
|
|
103
|
+
|
|
104
|
+
- **AI second opinion:** `driftwatch review notes` labels a change, quotes the risky text and gives a reason. It uses Claude Haiku with your own `ANTHROPIC_API_KEY` (or `OPENROUTER_API_KEY`), for about $0.0005 per change, within a monthly budget you set. Without a key, it uses a local model through Ollama if one is running. It never approves anything: only a person does.
|
|
105
|
+
- **Alerts:** `driftwatch check servers.yaml --review --alert` sends each change once to Slack (an incoming webhook) and by email.
|
|
106
|
+
- **Scheduled watcher:** `driftwatch watch servers.yaml` checks only the servers that are due, by risk, from every 6 hours to every 7 days.
|
|
107
|
+
- **Review site:** `driftwatch serve` shows the approved list, the alerts, and for each change a side-by-side diff with hidden text highlighted, plus Approve and Reject buttons. It listens on 127.0.0.1 only.
|
|
108
|
+
- **Guard, for agents you write:** `driftwatch.guard` wraps the MCP Python SDK client, so the model only ever sees approved tools, even from the SDK's cache. Calls with unapproved arguments are refused before they leave.
|
|
109
|
+
- **Gateway, for apps you can't change** (like desktop AI apps and IDEs): `driftwatch gateway stdio <server>` or `driftwatch gateway http` stands between the app and its servers. It passes on only approved tools and calls. It starts a local server only if its launch command was approved.
|
|
110
|
+
- **Login setup check:** `driftwatch conform servers.yaml` checks remote servers' published OAuth metadata against the MCP authorization spec. It sends only GET requests for public documents.
|
|
111
|
+
|
|
112
|
+
`driftwatch export --lock approved.lock.json` writes the approved list that the guard and the gateway enforce.
|
|
113
|
+
|
|
114
|
+
## What it never does
|
|
115
|
+
|
|
116
|
+
- **Passive only.** It reads what a server publishes to every client. No login attempts, and no attack traffic.
|
|
117
|
+
- **No telemetry.** The CLI sends nothing to us. It contacts only your servers (and, with `conform`, the login servers they name), plus your AI provider, a local model, Slack and email when you turn those on.
|
|
118
|
+
- **The AI never approves.** It only gives a second opinion.
|
|
119
|
+
|
|
120
|
+
## Limits
|
|
121
|
+
|
|
122
|
+
- Drift Watch compares what a server *says* about its tools, never its source code. A change to what a tool *does*, with the same description, isn't seen. Neither are instructions inside a tool's results.
|
|
123
|
+
- It pins tools and server instructions, not prompts or resources.
|
|
124
|
+
- The gateway checks tool lists and tool calls. Through `gateway stdio`, requests that start from the server, such as asking the app's model to write something or asking the user for input, pass through unchecked.
|
|
125
|
+
|
|
126
|
+
## License
|
|
127
|
+
|
|
128
|
+
Apache-2.0
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# MCP Drift Watch
|
|
2
|
+
|
|
3
|
+
**Your AI agents trust what MCP servers say about their tools. Drift Watch makes sure it's still what you approved.**
|
|
4
|
+
|
|
5
|
+
An MCP server can change its tool descriptions at any time after you approve it: a "rug pull". The AI model reads those descriptions as instructions, so a changed description can tell it to read files or send data somewhere. Nothing in MCP tells you when this happens.
|
|
6
|
+
|
|
7
|
+
Drift Watch pins every approved server by a SHA-256 fingerprint of everything the model reads:
|
|
8
|
+
- the tool names and descriptions
|
|
9
|
+
- the parameters
|
|
10
|
+
- the server's instructions
|
|
11
|
+
- how the server is started or reached
|
|
12
|
+
|
|
13
|
+
When any of it changes, the server is **frozen** and you get an alert. It stays frozen until a person looks at the change and approves or rejects it.
|
|
14
|
+
|
|
15
|
+
## Install
|
|
16
|
+
|
|
17
|
+
```sh
|
|
18
|
+
uv tool install mcp-drift-watch # or: pipx install mcp-drift-watch
|
|
19
|
+
driftwatch --version
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
The package is called `mcp-drift-watch`, and the command is `driftwatch`. A different, unrelated package on PyPI is called `driftwatch`, so `pip install driftwatch` and `uvx driftwatch` install that one, not this.
|
|
23
|
+
|
|
24
|
+
Optional parts:
|
|
25
|
+
- `mcp-drift-watch[web]` adds the review site and the HTTP gateway
|
|
26
|
+
- `mcp-drift-watch[postgres]` adds a hosted Postgres database, instead of a local SQLite file
|
|
27
|
+
|
|
28
|
+
## Quick start
|
|
29
|
+
|
|
30
|
+
List the servers you approved in `servers.yaml`. Write secrets as `${VAR}`: they're read from the environment and never stored.
|
|
31
|
+
|
|
32
|
+
```yaml
|
|
33
|
+
servers:
|
|
34
|
+
- name: notes
|
|
35
|
+
transport: stdio
|
|
36
|
+
command: npx
|
|
37
|
+
args: ["-y", "@example/notes-mcp@1.4.2"] # pin the version
|
|
38
|
+
- name: tickets
|
|
39
|
+
transport: http
|
|
40
|
+
url: https://tickets.example.com/mcp
|
|
41
|
+
headers: {Authorization: "Bearer ${TICKETS_TOKEN}"}
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
```sh
|
|
45
|
+
driftwatch pin servers.yaml # approve what's there now, pinned by fingerprint
|
|
46
|
+
driftwatch check servers.yaml # later: compare with the approved version (exit 1 if anything changed)
|
|
47
|
+
driftwatch diff notes # what changed, with red flags and OWASP MCP Top 10 IDs
|
|
48
|
+
driftwatch approve notes --fingerprint <id> # the id diff shows; or: driftwatch reject notes
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
`check` approves nothing, so it fits a CI job or a cron.
|
|
52
|
+
|
|
53
|
+
## Before you start: what Drift Watch trusts
|
|
54
|
+
|
|
55
|
+
- **`servers.yaml` is like code.** `pin` and `check` start the programs it names, and each `${VAR}` hands that environment variable to them. Only use a `servers.yaml` you trust: never one from someone else's pull request.
|
|
56
|
+
- **A `.env` file in the current folder is read too** (keys and settings). Trust it like `servers.yaml`.
|
|
57
|
+
- **The first `pin` trusts what the server serves at that moment.** It warns about high red flags in that first version, and `driftwatch diff <server>` shows them.
|
|
58
|
+
- **The review site and the HTTP gateway have no sign-in.** They answer only on 127.0.0.1 and refuse web pages, but any program on your computer can use them.
|
|
59
|
+
|
|
60
|
+
## What else is included
|
|
61
|
+
|
|
62
|
+
- **AI second opinion:** `driftwatch review notes` labels a change, quotes the risky text and gives a reason. It uses Claude Haiku with your own `ANTHROPIC_API_KEY` (or `OPENROUTER_API_KEY`), for about $0.0005 per change, within a monthly budget you set. Without a key, it uses a local model through Ollama if one is running. It never approves anything: only a person does.
|
|
63
|
+
- **Alerts:** `driftwatch check servers.yaml --review --alert` sends each change once to Slack (an incoming webhook) and by email.
|
|
64
|
+
- **Scheduled watcher:** `driftwatch watch servers.yaml` checks only the servers that are due, by risk, from every 6 hours to every 7 days.
|
|
65
|
+
- **Review site:** `driftwatch serve` shows the approved list, the alerts, and for each change a side-by-side diff with hidden text highlighted, plus Approve and Reject buttons. It listens on 127.0.0.1 only.
|
|
66
|
+
- **Guard, for agents you write:** `driftwatch.guard` wraps the MCP Python SDK client, so the model only ever sees approved tools, even from the SDK's cache. Calls with unapproved arguments are refused before they leave.
|
|
67
|
+
- **Gateway, for apps you can't change** (like desktop AI apps and IDEs): `driftwatch gateway stdio <server>` or `driftwatch gateway http` stands between the app and its servers. It passes on only approved tools and calls. It starts a local server only if its launch command was approved.
|
|
68
|
+
- **Login setup check:** `driftwatch conform servers.yaml` checks remote servers' published OAuth metadata against the MCP authorization spec. It sends only GET requests for public documents.
|
|
69
|
+
|
|
70
|
+
`driftwatch export --lock approved.lock.json` writes the approved list that the guard and the gateway enforce.
|
|
71
|
+
|
|
72
|
+
## What it never does
|
|
73
|
+
|
|
74
|
+
- **Passive only.** It reads what a server publishes to every client. No login attempts, and no attack traffic.
|
|
75
|
+
- **No telemetry.** The CLI sends nothing to us. It contacts only your servers (and, with `conform`, the login servers they name), plus your AI provider, a local model, Slack and email when you turn those on.
|
|
76
|
+
- **The AI never approves.** It only gives a second opinion.
|
|
77
|
+
|
|
78
|
+
## Limits
|
|
79
|
+
|
|
80
|
+
- Drift Watch compares what a server *says* about its tools, never its source code. A change to what a tool *does*, with the same description, isn't seen. Neither are instructions inside a tool's results.
|
|
81
|
+
- It pins tools and server instructions, not prompts or resources.
|
|
82
|
+
- The gateway checks tool lists and tool calls. Through `gateway stdio`, requests that start from the server, such as asking the app's model to write something or asking the user for input, pass through unchecked.
|
|
83
|
+
|
|
84
|
+
## License
|
|
85
|
+
|
|
86
|
+
Apache-2.0
|
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "mcp-drift-watch"
|
|
3
|
+
version = "0.1.0"
|
|
4
|
+
description = "Pin approved MCP servers by fingerprint, alert when their tool descriptions change, and keep changed servers frozen until a person re-approves them."
|
|
5
|
+
readme = "docs/pypi.md"
|
|
6
|
+
license = "Apache-2.0"
|
|
7
|
+
license-files = ["LICENSE"]
|
|
8
|
+
keywords = [
|
|
9
|
+
"mcp",
|
|
10
|
+
"model-context-protocol",
|
|
11
|
+
"ai-security",
|
|
12
|
+
"tool-poisoning",
|
|
13
|
+
"rug-pull",
|
|
14
|
+
"ai-agents",
|
|
15
|
+
]
|
|
16
|
+
classifiers = [
|
|
17
|
+
"Development Status :: 3 - Alpha",
|
|
18
|
+
"Environment :: Console",
|
|
19
|
+
"Intended Audience :: Developers",
|
|
20
|
+
"Intended Audience :: System Administrators",
|
|
21
|
+
"Operating System :: OS Independent",
|
|
22
|
+
"Programming Language :: Python :: 3",
|
|
23
|
+
"Programming Language :: Python :: 3.12",
|
|
24
|
+
"Programming Language :: Python :: 3.13",
|
|
25
|
+
"Topic :: Security",
|
|
26
|
+
]
|
|
27
|
+
requires-python = ">=3.12"
|
|
28
|
+
dependencies = [
|
|
29
|
+
"anthropic>=1",
|
|
30
|
+
"anyio>=4.16",
|
|
31
|
+
"httpx2>=2.16",
|
|
32
|
+
"jsonschema>=4.18",
|
|
33
|
+
"mcp>=2.3.0",
|
|
34
|
+
"mcp-types>=2.3.0",
|
|
35
|
+
"pydantic>=2",
|
|
36
|
+
"python-dotenv>=1",
|
|
37
|
+
"pyyaml>=6",
|
|
38
|
+
"referencing>=0.37",
|
|
39
|
+
"rich>=13",
|
|
40
|
+
"sqlalchemy>=2.0",
|
|
41
|
+
"typer>=0.12",
|
|
42
|
+
]
|
|
43
|
+
|
|
44
|
+
[[project.authors]]
|
|
45
|
+
name = "hsarikan"
|
|
46
|
+
|
|
47
|
+
[project.scripts]
|
|
48
|
+
driftwatch = "driftwatch.cli:app"
|
|
49
|
+
|
|
50
|
+
[project.optional-dependencies]
|
|
51
|
+
postgres = ["psycopg[binary]>=3.2"]
|
|
52
|
+
web = [
|
|
53
|
+
"fastapi>=0.115",
|
|
54
|
+
"jinja2>=3.1",
|
|
55
|
+
"markupsafe>=3.0",
|
|
56
|
+
"python-multipart>=0.0.18",
|
|
57
|
+
"starlette>=1.10",
|
|
58
|
+
"uvicorn>=0.30",
|
|
59
|
+
]
|
|
60
|
+
|
|
61
|
+
[build-system]
|
|
62
|
+
requires = ["uv_build>=0.12.1,<0.13.0"]
|
|
63
|
+
build-backend = "uv_build"
|
|
64
|
+
|
|
65
|
+
[tool.uv.build-backend]
|
|
66
|
+
module-name = "driftwatch"
|
|
67
|
+
|
|
68
|
+
[tool.pytest.ini_options]
|
|
69
|
+
testpaths = ["tests"]
|
|
70
|
+
pythonpath = ["."]
|
|
71
|
+
addopts = "-q"
|
|
72
|
+
|
|
73
|
+
[tool.ruff]
|
|
74
|
+
line-length = 100
|
|
75
|
+
target-version = "py312"
|
|
76
|
+
|
|
77
|
+
[tool.ruff.lint]
|
|
78
|
+
select = [
|
|
79
|
+
"E",
|
|
80
|
+
"F",
|
|
81
|
+
"I",
|
|
82
|
+
"B",
|
|
83
|
+
"UP",
|
|
84
|
+
"SIM",
|
|
85
|
+
]
|
|
86
|
+
|
|
87
|
+
[dependency-groups]
|
|
88
|
+
dev = [
|
|
89
|
+
"pytest>=8",
|
|
90
|
+
"ruff>=0.6",
|
|
91
|
+
]
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
# "driftwatch" on PyPI is someone else's project (ML drift monitoring), so the package is
|
|
3
|
+
# mcp-drift-watch. The command and the import stay `driftwatch` (finding F28).
|
|
4
|
+
name = "mcp-drift-watch"
|
|
5
|
+
version = "0.1.0"
|
|
6
|
+
description = "Pin approved MCP servers by fingerprint, alert when their tool descriptions change, and keep changed servers frozen until a person re-approves them."
|
|
7
|
+
# PyPI shows this file. The repo's README.md links to files that aren't public.
|
|
8
|
+
readme = "docs/pypi.md"
|
|
9
|
+
license = "Apache-2.0"
|
|
10
|
+
license-files = ["LICENSE"]
|
|
11
|
+
# Name only: PyPI shows the author's email to everyone.
|
|
12
|
+
authors = [
|
|
13
|
+
{ name = "hsarikan" }
|
|
14
|
+
]
|
|
15
|
+
keywords = ["mcp", "model-context-protocol", "ai-security", "tool-poisoning", "rug-pull", "ai-agents"]
|
|
16
|
+
classifiers = [
|
|
17
|
+
"Development Status :: 3 - Alpha",
|
|
18
|
+
"Environment :: Console",
|
|
19
|
+
"Intended Audience :: Developers",
|
|
20
|
+
"Intended Audience :: System Administrators",
|
|
21
|
+
"Operating System :: OS Independent",
|
|
22
|
+
"Programming Language :: Python :: 3",
|
|
23
|
+
"Programming Language :: Python :: 3.12",
|
|
24
|
+
"Programming Language :: Python :: 3.13",
|
|
25
|
+
"Topic :: Security",
|
|
26
|
+
]
|
|
27
|
+
requires-python = ">=3.12"
|
|
28
|
+
# Everything the code imports is listed, even what other packages bring along anyway:
|
|
29
|
+
# if one of them stopped bringing it, the CLI would break for everyone who installs it.
|
|
30
|
+
# Lower bounds are the versions it's tested with (uv.lock).
|
|
31
|
+
dependencies = [
|
|
32
|
+
"anthropic>=1",
|
|
33
|
+
"anyio>=4.16",
|
|
34
|
+
"httpx2>=2.16",
|
|
35
|
+
"jsonschema>=4.18",
|
|
36
|
+
"mcp>=2.3.0",
|
|
37
|
+
"mcp-types>=2.3.0",
|
|
38
|
+
"pydantic>=2",
|
|
39
|
+
"python-dotenv>=1",
|
|
40
|
+
"pyyaml>=6",
|
|
41
|
+
"referencing>=0.37",
|
|
42
|
+
"rich>=13",
|
|
43
|
+
"sqlalchemy>=2.0",
|
|
44
|
+
"typer>=0.12",
|
|
45
|
+
]
|
|
46
|
+
|
|
47
|
+
[project.scripts]
|
|
48
|
+
driftwatch = "driftwatch.cli:app"
|
|
49
|
+
|
|
50
|
+
[project.optional-dependencies]
|
|
51
|
+
postgres = [
|
|
52
|
+
"psycopg[binary]>=3.2",
|
|
53
|
+
]
|
|
54
|
+
web = [
|
|
55
|
+
"fastapi>=0.115",
|
|
56
|
+
"jinja2>=3.1",
|
|
57
|
+
"markupsafe>=3.0",
|
|
58
|
+
"python-multipart>=0.0.18",
|
|
59
|
+
"starlette>=1.10",
|
|
60
|
+
"uvicorn>=0.30",
|
|
61
|
+
]
|
|
62
|
+
|
|
63
|
+
[build-system]
|
|
64
|
+
requires = ["uv_build>=0.12.1,<0.13.0"]
|
|
65
|
+
build-backend = "uv_build"
|
|
66
|
+
|
|
67
|
+
[tool.uv.build-backend]
|
|
68
|
+
module-name = "driftwatch" # the package's name differs from the import's
|
|
69
|
+
|
|
70
|
+
[dependency-groups]
|
|
71
|
+
dev = [
|
|
72
|
+
"pytest>=8",
|
|
73
|
+
"ruff>=0.6",
|
|
74
|
+
]
|
|
75
|
+
|
|
76
|
+
[tool.pytest.ini_options]
|
|
77
|
+
testpaths = ["tests"]
|
|
78
|
+
pythonpath = ["."]
|
|
79
|
+
addopts = "-q"
|
|
80
|
+
|
|
81
|
+
[tool.ruff]
|
|
82
|
+
line-length = 100
|
|
83
|
+
target-version = "py312"
|
|
84
|
+
|
|
85
|
+
[tool.ruff.lint]
|
|
86
|
+
select = ["E", "F", "I", "B", "UP", "SIM"]
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
"""MCP Drift Watch: pin approved MCP servers and catch changes after approval."""
|
|
2
|
+
|
|
3
|
+
from importlib.metadata import PackageNotFoundError, version
|
|
4
|
+
|
|
5
|
+
try:
|
|
6
|
+
__version__ = version("mcp-drift-watch") # the package's name on PyPI
|
|
7
|
+
except PackageNotFoundError: # running from a source tree without an install
|
|
8
|
+
__version__ = "0.0.0"
|