Repository navigation
Add deed.page MCP Server - #272
Open
Avatar 8 (f-o-x11) wants to merge 1 commit into
Open
Avatar 8 (f-o-x11) wants to merge 1 commit into
Avatar 8 (f-o-x11) wants to merge 1 commit into
Conversation
Author
|
@microsoft-github-policy-service agree company="Avatar 8 LLC" |
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.
This adds deed.page to the partner server list. It comes from the deed.page team (Avatar 8 LLC).
deed.page is static web hosting for AI agents. Its remote MCP server (
https://deed.page/mcp, Streamable HTTP) lets an agent publish a page or a small static site it wrote to a permanent HTTPS URL, update it in place, roll back to an earlier version, attach a custom domain, or delete it. The first publish needs no account: the server returns an owner token, which the client then sends as a Bearer token. That is why the entry declares a bearer scheme and describes it as optional for the first call.What is in the file:
partners/servers/deed-page-mcp-server.json, following the shape of the existing partner entries: category Web, remote typestreamable-http, an optionaldeedpageBearersecurity scheme, our terms as the license link, and four use cases taken from what the server's tools actually do.How it was checked:
check-jsonschema --schemafile partners/server-schema.json partners/servers/*.jsonpasses, and the server name and the security scheme key are unique across the folder, as the validation workflow requires.initialize,tools/list, an anonymouspublish_site,get_site, thendelete_sitewith the returned token. The test page answered 404 afterwards.Links:
We're happy to adjust the description, category or icon, and to go through the verification process.