Skip to content

Add deed.page MCP Server - #272

Open
Avatar 8 (f-o-x11) wants to merge 1 commit into
Azure:mainfrom
f-o-x11:add-deed-page
Open

Avatar 8 (f-o-x11) wants to merge 1 commit into
Azure:mainfrom
f-o-x11:add-deed-page

Conversation

@f-o-x11

Copy link
Copy Markdown

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 type streamable-http, an optional deedpageBearer security 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/*.json passes, and the server name and the security scheme key are unique across the folder, as the validation workflow requires.
  • Against the live server: initialize, tools/list, an anonymous publish_site, get_site, then delete_site with 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.

@f-o-x11

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree company="Avatar 8 LLC"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant