Add mpp.land registry entry to discovery.mdx#535
Open
etal37 wants to merge 1 commit intotempoxyz:mainfrom
Open
Add mpp.land registry entry to discovery.mdx#535etal37 wants to merge 1 commit intotempoxyz:mainfrom
etal37 wants to merge 1 commit intotempoxyz:mainfrom
Conversation
|
@etal37 is attempting to deploy a commit to the Tempo Team on Vercel. A member of the Team first needs to authorize it. |
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.
What
Adds mpp.land to the registries table in the discovery documentation.
Why
mpp.land is an open registry that continuously verifies MPP services against
the spec. It scans every indexed service every 5 minutes and publishes
compliance scores, uptime history, and spec validation results.
Discovery documents are advisory (as the docs note). A service can publish a
valid-looking spec and behave differently at runtime. mpp.land catches these
discrepancies by probing the 402 challenge flow, validating response schemas
against declared specs, and tracking changes over time.
What it provides:
(TLS, challenge binding, digest params, 402 declarations, schema completeness)
5 minutes with response time tracking
logged in a public changelog
so agents can query the registry programmatically
enforcement, response previews, and reliability routing as a free proxy