@gizmodata/hardcharger-mcp 0.0.0-stage → 2.0.0
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.
- package/CHANGELOG.md +119 -0
- package/LICENSE +201 -0
- package/NOTICE +8 -0
- package/README.md +487 -2
- package/dist/cli.d.ts +2 -0
- package/dist/cli.js +75 -0
- package/dist/cli.js.map +1 -0
- package/dist/connection.d.ts +260 -0
- package/dist/connection.js +797 -0
- package/dist/connection.js.map +1 -0
- package/dist/format.d.ts +56 -0
- package/dist/format.js +240 -0
- package/dist/format.js.map +1 -0
- package/dist/oauth-facade.d.ts +50 -0
- package/dist/oauth-facade.js +223 -0
- package/dist/oauth-facade.js.map +1 -0
- package/dist/oauth.d.ts +94 -0
- package/dist/oauth.js +228 -0
- package/dist/oauth.js.map +1 -0
- package/dist/params.d.ts +61 -0
- package/dist/params.js +200 -0
- package/dist/params.js.map +1 -0
- package/dist/registry.d.ts +45 -0
- package/dist/registry.js +91 -0
- package/dist/registry.js.map +1 -0
- package/dist/server.d.ts +38 -0
- package/dist/server.js +753 -0
- package/dist/server.js.map +1 -0
- package/dist/sessions.d.ts +52 -0
- package/dist/sessions.js +113 -0
- package/dist/sessions.js.map +1 -0
- package/dist/sql-guard.d.ts +62 -0
- package/dist/sql-guard.js +460 -0
- package/dist/sql-guard.js.map +1 -0
- package/dist/sso.d.ts +29 -0
- package/dist/sso.js +145 -0
- package/dist/sso.js.map +1 -0
- package/dist/transports.d.ts +29 -0
- package/dist/transports.js +308 -0
- package/dist/transports.js.map +1 -0
- package/dist/version.d.ts +2 -0
- package/dist/version.js +8 -0
- package/dist/version.js.map +1 -0
- package/package.json +72 -4
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,119 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable changes to this project will be documented in this file.
|
|
4
|
+
|
|
5
|
+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
|
|
6
|
+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
|
+
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
## [2.0.0] - 2026-10-20
|
|
11
|
+
|
|
12
|
+
The first published release, with Hardcharger 2.0.0 (0.1.0 was never published). The Changed and
|
|
13
|
+
Fixed entries describe what moved since 0.1.0, for anyone who installed it from git.
|
|
14
|
+
<!-- Set the date above at tag time. -->
|
|
15
|
+
|
|
16
|
+
### Changed
|
|
17
|
+
- Built on `@gizmodata/hardcharger` 2.0.0 (hardcharger-js `a6e93a2`, on `@gizmodata/warp-sql` 1.0.0,
|
|
18
|
+
warp-sql-js `903feb4`), the clients for Warp SQL protocol 1.0.0 with browser sign-in (were
|
|
19
|
+
`a4ac97c` and `6dea14c`). The chart, the extension manifest and the npm package are 2.0.0: the
|
|
20
|
+
Hardcharger clients and integrations launch with the server's version.
|
|
21
|
+
- **Breaking:** `login_sso` runs Warp SQL browser sign-in (§4.3) on the connection's own URI and
|
|
22
|
+
port, through `@gizmodata/hardcharger`, as Hardcharger now offers it (its separate OAuth port and
|
|
23
|
+
`/oauth/initiate` routes are gone). It signs in with the access token the server hands out, used
|
|
24
|
+
as is (call `login_sso` again when it expires), instead of exchanging an ID token. A failed
|
|
25
|
+
sign-in reports the flow's code (`access_denied`, `identity_provider_error`,
|
|
26
|
+
`invalid_credentials`); an expired or collected flow (`flow_not_found`) starts over on the next
|
|
27
|
+
call; a server without browser sign-in (`not_implemented`) is reported as unavailable.
|
|
28
|
+
`HARDCHARGER_OAUTH_PORT`, `HARDCHARGER_OAUTH_BASE_URL` and the extension's "SSO port" setting
|
|
29
|
+
are removed.
|
|
30
|
+
- The client's own error codes begin with `client_`: a lost connection is reopened on
|
|
31
|
+
`client_transport_error` and `client_connection_closed` (was `transport_error`,
|
|
32
|
+
`connection_closed`), the plain-HTTP hint keys on `client_transport_error`, and error messages
|
|
33
|
+
name the new codes (e.g. `(client_transport_error)`, `(client_invalid_argument)`).
|
|
34
|
+
- `server_info` on a Warp SQL server other than Hardcharger reads the DuckDB version from the
|
|
35
|
+
server-info key `duckdb_version` (was `engine_version`, which protocol 1.0.0 dropped).
|
|
36
|
+
- A session ended with reason `token_revoked`, `credentials_changed` or `principal_dropped` is no
|
|
37
|
+
longer reopened with the configured credentials (Warp SQL §4.2, §5.6): the error, with its
|
|
38
|
+
reason, is returned. `killed`, `token_expired`, no reason or an unknown reason still reopen once.
|
|
39
|
+
|
|
40
|
+
### Added
|
|
41
|
+
- Production dependency license texts travel with the desktop extension as
|
|
42
|
+
`THIRD_PARTY_NOTICES.txt` and with the image under `/usr/share/doc/hardcharger-mcp/`.
|
|
43
|
+
- Tests: reopening after `client_transport_error`; no reopen after a session ended for a revoked
|
|
44
|
+
token; `isConnectionLost` for every `session_ended` reason and for the old unprefixed codes.
|
|
45
|
+
- Tests for `login_sso` on browser sign-in: unit tests for each poll answer (pending at the
|
|
46
|
+
server's interval, complete, a failed flow's code, `flow_not_found`, an expired flow, a server
|
|
47
|
+
without browser sign-in, an unreachable one); the live tests run it against
|
|
48
|
+
`hardcharger-server --oauth-client-id` on its main port.
|
|
49
|
+
|
|
50
|
+
### Fixed
|
|
51
|
+
- CI's live tests on main failed: the browser sign-in suite started `hardcharger-server` with
|
|
52
|
+
`--oauth-port`, which Hardcharger 2.0.0-rc.1 removed (browser sign-in runs on the server's own
|
|
53
|
+
port, Warp SQL §4.3), so the server exited with "unknown option". The suite now passes
|
|
54
|
+
`--oauth-base-url` with the server's port (from the merged Warp SQL 1.0 work).
|
|
55
|
+
|
|
56
|
+
### Documentation
|
|
57
|
+
|
|
58
|
+
- The README banner is the new Hardcharger™ logo, the bull mascot lockup in a light and a dark
|
|
59
|
+
version that follows the reader's color scheme, in place of the GizmoData banner card, and the
|
|
60
|
+
Claude Desktop extension's icon (`icon.png`, 512 px) is the Hardcharger bull head in place of the
|
|
61
|
+
GizmoData logo.
|
|
62
|
+
|
|
63
|
+
## [0.1.0] - 2026-10-19
|
|
64
|
+
|
|
65
|
+
The Hardcharger™ port of [gizmosql-mcp](https://github.com/gizmodata/gizmosql-mcp) 0.4.11: the same
|
|
66
|
+
tools, resource, transports, OAuth resource-server mode, per-user HTTP sessions, Claude Desktop
|
|
67
|
+
extension, container image and Helm chart, on Hardcharger's Warp SQL protocol through
|
|
68
|
+
`@gizmodata/hardcharger` (hardcharger-js `a4ac97c` on warp-sql-js `6dea14c`).
|
|
69
|
+
|
|
70
|
+
### Added
|
|
71
|
+
- Tools `list_connections`, `use_connection`, `list_catalogs`, `list_schemas`, `list_tables`,
|
|
72
|
+
`describe_table`, `use_schema`, `run_query`, `explain_query`, `server_info`, `execute_statement`
|
|
73
|
+
(only with `HARDCHARGER_ALLOW_WRITES=true`) and `login_sso` (only with
|
|
74
|
+
`HARDCHARGER_ENABLE_SSO=true`, stdio only), and the table DDL resource
|
|
75
|
+
`hardcharger://{connection}/schema/{catalog}/{schema}/{table}`.
|
|
76
|
+
- Connections are `hardcharger://host[:port][/prefix][?tls=false]` URIs (`HARDCHARGER_URI`, TLS to
|
|
77
|
+
port 31337 unless the URI says otherwise), checked the way the client reads them before anything
|
|
78
|
+
is sent. Only `HARDCHARGER_*` settings are read.
|
|
79
|
+
- Sign-in with a password, a signed sign-in token (`HARDCHARGER_TOKEN`, the `token_exchange`
|
|
80
|
+
grant; the token also works as the password of user `token`), a client certificate
|
|
81
|
+
(`HARDCHARGER_MTLS_CERT` + `HARDCHARGER_MTLS_KEY`: alone, the certificate is the credential), or
|
|
82
|
+
the server's browser sign-in (`login_sso`, the same OAuth routes as `hardcharger --auth-type
|
|
83
|
+
external`; `HARDCHARGER_BROWSER` names the browser). `HARDCHARGER_TLS_ROOTS` trusts a private CA.
|
|
84
|
+
- Query timeouts are the server's own (`statementTimeoutMs`, Warp SQL §6.9): a runaway statement is
|
|
85
|
+
cancelled on the server and reported as `statement_timeout`, with a client-side cancel a few
|
|
86
|
+
seconds later as backstop. This covers `execute_statement` too.
|
|
87
|
+
- Lost sessions: the client replaces a session the server evicted and replays its catalog and
|
|
88
|
+
schema, including ones set by `use_schema` or a `USE` run through `run_query`; a session an
|
|
89
|
+
administrator killed, a closed connection or a transport failure reopens the connection once.
|
|
90
|
+
`server_info` reports `session_replacements` and `reconnects`.
|
|
91
|
+
- Errors keep the server's message with its Warp SQL code, SQLSTATE, HTTP status and request id
|
|
92
|
+
(`... (sql_error, SQLSTATE 42P01, HTTP 400, request r_...)`); errors raised before an answer get
|
|
93
|
+
their code added (`(transport_error)`), and a TLS handshake against a plain-HTTP server says to
|
|
94
|
+
add `?tls=false`.
|
|
95
|
+
- `server_info` reports `HARDCHARGER_VERSION()`, `HARDCHARGER_USER()`, `HARDCHARGER_ROLE()`, the
|
|
96
|
+
protocol and capabilities from discovery, the server's idle timeout from the session document,
|
|
97
|
+
and settings from `hardcharger_settings()`.
|
|
98
|
+
- Bind parameters travel as Warp SQL JSON parameters; a date, timestamp or binary parameter binds
|
|
99
|
+
the row as Arrow data through a prepared statement.
|
|
100
|
+
- Claude Desktop extension (`.mcpb`): one all-JavaScript bundle for every platform (no native
|
|
101
|
+
driver), with URI, token, client certificate and CA settings.
|
|
102
|
+
- Live tests against `hardcharger-server` (every tool, the HTTP transport, every sign-in, lost
|
|
103
|
+
sessions); they fail, never skip, without a server. CI runs them against
|
|
104
|
+
`ghcr.io/gizmodata/hardcharger:main`; the release workflow runs the full CI on the tagged commit
|
|
105
|
+
first.
|
|
106
|
+
|
|
107
|
+
### Changed (from gizmosql-mcp)
|
|
108
|
+
- Plain ISO-8601 strings in `params` are no longer turned into timestamps: the server types each
|
|
109
|
+
JSON parameter from where it is used (a date string compared with a DATE column is a date). Use
|
|
110
|
+
`{"type": "date"|"timestamp", ...}` where nothing gives the type.
|
|
111
|
+
|
|
112
|
+
### Removed (from gizmosql-mcp)
|
|
113
|
+
- The native ADBC driver and everything around it (bundled drivers per platform,
|
|
114
|
+
`GIZMOSQL_DRIVER_LIB`, the install-script approval): the client is pure JavaScript.
|
|
115
|
+
- The timed session refresh (`GIZMOSQL_SESSION_REFRESH_SECONDS`): GizmoSQL silently recreated an
|
|
116
|
+
evicted session, so the search path had to be re-applied on a timer; Warp SQL reports the loss
|
|
117
|
+
and the client replays the session's options.
|
|
118
|
+
- Host/port/plaintext settings (`GIZMOSQL_HOST`, `_PORT`, `_PLAINTEXT`): the URI says all three.
|
|
119
|
+
- Flight SQL error unwrapping and the SqlInfo fallback, which have no Warp SQL counterpart.
|
package/LICENSE
ADDED
|
@@ -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
|
|
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 GizmoData LLC
|
|
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.
|
package/NOTICE
ADDED
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
Hardcharger MCP server
|
|
2
|
+
Copyright 2026 GizmoData LLC
|
|
3
|
+
|
|
4
|
+
This product includes software developed at GizmoData LLC (https://gizmodata.com).
|
|
5
|
+
|
|
6
|
+
Portions derived from gizmodata/gizmosql-mcp (Apache License 2.0, Copyright GizmoData LLC).
|
|
7
|
+
|
|
8
|
+
Hardcharger and GizmoData are trademarks of GizmoData LLC.
|