Bind progressive MCP discovery to versioned catalog checkpoints
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
No files or test paths are named. Start by reading the progressive discovery and server/discover implementations, then trace how governed calls verify discovered schemas and approved catalog checkpoints. Done means tests cover cache refresh, stale catalogs, tool removal, schema substitution, and unapproved late discovery without weakening catalog approval.
Written by the indexing model from the issue text.
Description
Support progressive discovery and server/discover without weakening catalog approval. Each governed call must bind to the exact discovered schema and approved catalog checkpoint. Acceptance evidence: cache refresh, stale catalog, tool removal, schema substitution, and unapproved late-discovery tests.
- Dominant language
- Python
- Stars
- 33
- Forks
- 24
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 75
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from agentrust-io/cmcp
-
Follow-ups from #779: seal after bundle verification, owner-auth wording, config-digest changelogPossibly taken @rajnisht7 claimed this 1 day ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
agentrust-io/cmcp#782 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
3 of 6 InspectionResult values are declared but unreachablePossibly taken @dinakarjs claimed this 3 days ago. Open
Difficulty 3/5 Half a day Newbie friendliness 35/100
agentrust-io/cmcp#764 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
agentrust-io/cmcp#736 · 6 comments ·
Maintainers usually reply within 1 day
-
Session identity is minted fresh on every open, so a restarted or peer instance cannot resume a sessionPossibly taken @dinakarjs claimed this 1 day ago. Openhelp wanted
Difficulty 4/5 3-5 days Newbie friendliness 55/100
agentrust-io/cmcp#675 · 3 comments ·
Maintainers usually reply within 1 day
-
Define explicit authorization for releasing confidential data and derived outputsPossibly taken @rajnisht7 claimed this 1 day ago. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
agentrust-io/cmcp#660 · 7 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in agentrust-io/cmcp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zach-blumenfeld/aip#13 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
nathanmarlor/foxess_modbus#1287 ·
Maintainers usually reply within 4 days
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
OpenLakeForge/openlakeforge#498 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest help wanted python
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
pollen-robotics/reachy_mini#1493 ·
Maintainers usually reply within 1 day