Server definition

Hash: sha256:00355621994e347cb6e4dce0b613a011b3c0d04deb420f89572cd2812bd72218
What it is: What a remote MCP server returned when asked what it offers: 4 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "Delete a page you published, by id.",
      "inputSchema": {
        "properties": {
          "id": {
            "type": "string"
          }
        },
        "required": [
          "id"
        ],
        "type": "object"
      },
      "name": "delete_page",
      "outputSchema": null
    },
    {
      "description": "List the pages you have published, newest first, with their URLs and view counts.",
      "inputSchema": {
        "properties": {
          "limit": {
            "type": "number"
          }
        },
        "type": "object"
      },
      "name": "list_pages",
      "outputSchema": null
    },
    {
      "description": "Publish text or markdown as a clean, shareable public web page and get back a URL you can hand to a human. Use this whenever you produce a report, summary, plan, table, or any result a person should read in a browser instead of the chat window. To keep ONE page updated across runs/sessions, pass a stable `slug`: publishing again with the same slug overwrites the same page at the same URL — no need to remember a generated id.",
      "inputSchema": {
        "properties": {
          "content": {
            "description": "The page body. Markdown is supported (headings, lists, links, code, bold/italic, blockquotes).",
            "type": "string"
          },
          "format": {
            "description": "How to render content. Default markdown.",
            "enum": [
              "markdown",
              "text"
            ],
            "type": "string"
          },
          "slug": {
            "description": "Optional stable name for a page you intend to keep updating (e.g. \"deploy-status\", \"nightly-report\"). Re-publishing with the same slug updates that same page in place at the same URL. Perfect for a fresh-context agent that can't remember a generated id — just reuse the slug. Omit for a one-off page with a random id.",
            "type": "string"
          },
          "title": {
            "description": "Page title (shown at top and in the browser tab).",
            "type": "string"
          }
        },
        "required": [
          "content"
        ],
        "type": "object"
      },
      "name": "publish_page",
      "outputSchema": null
    },
    {
      "description": "Update the title and/or content of a page you previously published; the URL never changes. Use this to keep one stable link current across sessions or runs — a live status page, a running changelog, an append-as-you-go log, or a dashboard the recipient can bookmark once and always see fresh.",
      "inputSchema": {
        "properties": {
          "content": {
            "type": "string"
          },
          "id": {
            "type": "string"
          },
          "title": {
            "type": "string"
          }
        },
        "required": [
          "id"
        ],
        "type": "object"
      },
      "name": "update_page",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:00355621994e347cb6e4dce0b613a011b3c0d04deb420f89572cd2812bd72218 | sha256sum