2aea5dc6beCarve the schema-bearing parts of SEP-1913 into three independent experimental extensions, per @localden's "narrower first cut" ask and the Tool Annotations IG's 2026-05-28 extension-first decision: - io.modelcontextprotocol/trust-annotations (headline): narrow data-classification taxonomy (sensitive, untrusted) + open-ended evidenceRef pointer. - io.modelcontextprotocol/action-metadata: carries forward SEP-2061 (inputMetadata/returnMetadata/outcomes + requiresReview). - io.modelcontextprotocol/ifc-fides: FIDES information-flow control as a profile of evidenceRef, not a wire root. Adds repo meta (README, MAINTAINERS, CONTRIBUTING, LICENSE) and docs (sep-disposition, intent-comment, decisions, open-questions, trust-model, related-work). FIDES demoted to a profile; DataClass and requiresReview rehomed; maliciousActivityHint and propagation parked on the SEP-1913 umbrella. Citations index on public sources only. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
42 lines
1.9 KiB
Markdown
42 lines
1.9 KiB
Markdown
# Contributing
|
|
|
|
This repository is an incubation space for the
|
|
[Tool Annotations Interest Group](https://modelcontextprotocol.io/community/tool-annotations/charter).
|
|
We welcome proposals, schema changes, and reference implementations that
|
|
inform a future Extensions Track SEP.
|
|
|
|
## What lives here
|
|
|
|
- **Specification drafts** — `specification/draft/<extension-name>.mdx`,
|
|
one file per extension, written in the same RFC-2119 style as the core MCP
|
|
specification (per [SEP-2133](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/2133-extensions.md)).
|
|
- **Decision records** — `docs/decisions.md`. Append, do not rewrite.
|
|
- **Open questions** — `docs/open-questions.md`.
|
|
|
|
## What does *not* live here
|
|
|
|
- Implementation code. Reference implementations live in their own
|
|
repositories and are linked from the relevant `specification/draft/*.mdx`.
|
|
- Binding specification changes. Those are made through the
|
|
[SEP process](https://modelcontextprotocol.io/community/sep-guidelines).
|
|
|
|
## Proposing a change to an existing extension
|
|
|
|
1. Open a PR against `specification/draft/<name>.mdx`.
|
|
2. Update the **Status** and **Changelog** sections in the frontmatter.
|
|
3. If the change is breaking (per the SEP-2133 definition), use a new
|
|
extension identifier and a new file.
|
|
4. Append an entry to `docs/decisions.md` if the change reflects a design
|
|
decision worth preserving.
|
|
|
|
## Proposing a new extension
|
|
|
|
1. Read [SEP-2133, "Experimental Extensions"](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/2133-extensions.md#experimental-extensions).
|
|
2. Open a discussion or PR proposing the identifier and scope.
|
|
3. On acceptance, add `specification/draft/<new-name>.mdx` using the
|
|
frontmatter from an existing draft as a template.
|
|
|
|
## Code of conduct
|
|
|
|
This repository follows the
|
|
[MCP Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md).
|