fix(mcp): advertise version and tool costs - #138
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares DocPull 6.5.5.\n\nThe MCP server now reports the package version during initialization and attaches the documented cost prefix plus structured docpull/cost metadata to all 37 tools. The default remains local and zero-cost; only render_url explicitly advertises its opt-in paid-capable runtimes. Release metadata, the plugin prerequisite, both lockfiles, and the JavaScript SDK version are synchronized.\n\nValidation:\n- focused MCP and plugin policy tests: 27 passed\n- JavaScript SDK tests: 14 passed\n- Python full suite: 1,211 passed, 18 skipped; one network-dependent spaCy model download timed out, then passed on focused retry\n- lint, formatting, type checks, metadata, and schema checks passed\n- reproducible wheel and sdist build passed