examples: MCP contact endpoint (verify-then-forward INK receiver)#24
Open
jasonodoom wants to merge 1 commit into
Open
examples: MCP contact endpoint (verify-then-forward INK receiver)#24jasonodoom wants to merge 1 commit into
jasonodoom wants to merge 1 commit into
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
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.
A publicly addressable INK receiver that forwards verified signed envelopes to a human inbox, so an agent can reach a person alongside an MCP server. It reuses the reference-receiver verification pipeline (bounded read, validateMessage, sender-key resolution, then verifyInkAuth for both the transport and body signatures plus nonce and timestamp checks) and differs only in the terminal action.
The four design decisions (recipient binding to a real published DID, no encryption in v1, dual per-IP and per-DID rate limiting, verified-vs-claimed labeling in the forwarded email) are written up in the README. The shared plumbing is imported from the reference receiver rather than re-implemented, so the example cannot drift from its security floor.
Supersedes #23, whose branch was removed.