feat(mcp): read-only dependency inventory tools - #112
Merged
Merged
Conversation
balcsida
added this pull request to stack #114
September 22, 2026 21:06
balcsida
changed the title
balcsida
force-pushed
the
feat/supply-chain/m6-mcp
branch
2 times, most recently
from
September 22, 2026 22:19
50a3ea3 to
8c6b999
Compare
balcsida
marked this pull request as ready for review
September 22, 2026 22:20
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Add search_dependency_inventory, find_component_repositories, and inspect_component_license over the same inventory services REST uses, so authorization scope, not-found behavior, cursors, and truncation agree. Outputs carry snapshot IDs, provenance, scope, and a note that package and license content is untrusted data. No write tools are exposed. An integration test proves REST/MCP agreement and that another installation's occurrences never leak through results or errors. Co-Authored-By: Claude <noreply@anthropic.com>
balcsida
force-pushed
the
feat/supply-chain/m6-mcp
branch
from
September 22, 2026 22:30
8c6b999 to
2af8325
Compare
balcsida
force-pushed
the
feat/supply-chain/m6-mcp
branch
from
September 22, 2026 22:59
2af8325 to
aa278e7
Compare
balcsida
force-pushed
the
feat/supply-chain/m6-mcp
branch
from
September 22, 2026 23:51
aa278e7 to
2af8325
Compare
Merged
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
1 participant
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.
Summary
Milestone 6. Depends on #111.
Adds three read-only MCP tools over the same authorized services REST uses, so scope, not-found behavior, cursors, and truncation agree:
search_dependency_inventory– unique coordinates across readable repositories with filters and cursor pagination.find_component_repositories– authorized repositories/snapshots containing a component.inspect_component_license– declarations, registry evidence history with resolver/list versions, assessment, relationships for one occurrence.Responses include snapshot IDs, provenance, scope, and truncation, and state that package/license/evidence content is untrusted data, never instructions. No approval, import, or refresh tools are exposed. Exact code-usage joins are deliberately not offered (a dependency path is not a call graph; GHES snapshots are unbound observations).
Verification
Integration test: tool list has no write tools; REST and MCP return the same components for the same principal; another installation's occurrences never leak through results or error text; bogus keys and foreign snapshot IDs fail safely; truncation honored.
Implications
None beyond the module gate; tools register only when
GRAPHNEST_SUPPLY_CHAIN=true.Part of the Dependencies & Licenses stack (native GitHub stack #114, ten layers,
main ← #104 ← #105 ← #106 ← #107 ← #108 ← #109 ← #110 ← #111 ← #112 ← #113). Design: ADR-0017; living plan with the full validation table:docs/execplans/supply-chain.md. All commits are SSH-signed. Nothing here calls a live GitHub Enterprise Server or a live package registry; GitHub and registry behavior is exercised against fixtures and fake servers only.Stack created with GitHub Stacks CLI