Server definition

Hash: sha256:9e075bce5e05f1f6faca1d7b1f41e2720186fb3b724a6df168782ed17152a3b1
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": "Return the full record for a single component: title, description, narrative body, the primary HTML pattern, list of slots (placeholders the model should fill), VML/responsive flags, and all code examples. Use after list_components to fetch the actual HTML pattern to paste into an email.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "name": {
            "description": "Component name. Get the list from list_components first.",
            "enum": [
              "background-images",
              "buttons",
              "images",
              "inline-icon",
              "spacing",
              "text"
            ],
            "type": "string"
          }
        },
        "required": [
          "name"
        ],
        "type": "object"
      },
      "name": "get_component",
      "outputSchema": null
    },
    {
      "description": "Return the full rule pages for a given category. Each rule includes the title, description, markdown body explaining the rule, and any HTML/CSS code examples from the playbook. Use this to teach a model the exact patterns for a specific concern (e.g., responsive layout).",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "category": {
            "description": "Which rule category to fetch.",
            "enum": [
              "ai-generation",
              "compatibility",
              "production",
              "structure"
            ],
            "type": "string"
          }
        },
        "required": [
          "category"
        ],
        "type": "object"
      },
      "name": "get_playbook_rules",
      "outputSchema": null
    },
    {
      "description": "List all rule categories in the Email Playbook with a one-line description and page count. Categories are: structure (head/body container/header/body/footer), compatibility (Outlook MSO, RTL, responsive), production (Gmail clipping, dark mode, preheader, bulletproof buttons), ai-generation (constraints for AI emitters). For reusable components, use list_components instead — they live in a separate dimension and are not returned by get_playbook_rules.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "list_categories",
      "outputSchema": null
    },
    {
      "description": "List all reusable email components in the playbook with their metadata: name, subcategory (layout/media/interactive/text), description, whether they require Outlook VML, and whether they are responsive. Use this first to discover what components exist before calling get_component.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "list_components",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:9e075bce5e05f1f6faca1d7b1f41e2720186fb3b724a6df168782ed17152a3b1 | sha256sum