qyl-mcp-server 6.1.0 → 6.1.2
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/README.md +21 -0
- package/dist/mcp-app.html +1 -1
- package/dist/mcp-dashboard.html +1 -1
- package/dist/mcp-home.html +27 -8
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -96,6 +96,27 @@ so serving it requires Bun.
|
|
|
96
96
|
|
|
97
97
|
## Release notes
|
|
98
98
|
|
|
99
|
+
### 6.1.2
|
|
100
|
+
|
|
101
|
+
- The landing page at `mcp.qyl.at` states what 6.1.0 added: a request-scope
|
|
102
|
+
section for cancellation, progress and the per-call log line, the full
|
|
103
|
+
eleven-tool surface, and a hero fact for it. Surfaces take the ink of the
|
|
104
|
+
original qyl site (`#050706`) and its family; the cyan accent is unchanged.
|
|
105
|
+
- The page no longer embeds the whole `package.json`: a default JSON import
|
|
106
|
+
inlined the dependency and export tables into every visitor's download; a
|
|
107
|
+
named import of `version` ships the one field the footer shows.
|
|
108
|
+
|
|
109
|
+
### 6.1.1
|
|
110
|
+
|
|
111
|
+
- The bundled viewers no longer ask for progress they never read: the MCP
|
|
112
|
+
Apps client passed a no-op `onprogress` on every `tools/call`, which put a
|
|
113
|
+
`progressToken` on each request and, since 6.1.0, had the server answer
|
|
114
|
+
with notifications nobody consumed. A viewer that wants progress passes its
|
|
115
|
+
own callback.
|
|
116
|
+
- `verify:frame` runs as a step of `bun run test`: every tool in the manifest
|
|
117
|
+
must be registered inside `runTool` under its own name, so a tool cannot
|
|
118
|
+
ship without cancellation, progress and its log line.
|
|
119
|
+
|
|
99
120
|
### 6.1.0
|
|
100
121
|
|
|
101
122
|
- Every tool handler runs inside `runTool`, which resolves the SDK request
|