# io.github.petalframework/petal-components-mcp (remote · mcp.petal.build)

Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.

- Trust score: 68/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.petal.build`: 68/100 (this document), [markdown](https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp.md), [page](https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp)
- npm · `petal-components-mcp`: 68/100, [markdown](https://verifymcp.io/servers/petalframework-petal-components-mcp/petal-components-mcp.md), [page](https://verifymcp.io/servers/petalframework-petal-components-mcp/petal-components-mcp)

## Channel facts

- Endpoint: `https://mcp.petal.build/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 298 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http petalframework-petal-components-mcp https://mcp.petal.build/mcp
```

### Codex

```toml
[mcp_servers.petalframework-petal-components-mcp]
url = "https://mcp.petal.build/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "petalframework-petal-components-mcp": {
      "type": "remote",
      "url": "https://mcp.petal.build/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add petalframework-petal-components-mcp --url https://mcp.petal.build/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  petalframework-petal-components-mcp:
    url: "https://mcp.petal.build/mcp"
```

### Other

```json
{
  "mcpServers": {
    "petalframework-petal-components-mcp": {
      "type": "http",
      "url": "https://mcp.petal.build/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (3)

### `get_install_instructions` (~101 tokens)

Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks to install petal_components, when you are setting up a new Phoenix project that needs UI components, or when verifying an existing installation. Returns step-by-step instructions covering mix.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to follow on a project that is partially configured.

### `list_components` (~61 tokens)

List every component shipped by petal_components, the shadcn-style component library for Phoenix LiveView. This is the canonical Phoenix UI vocabulary - call it before composing any HEEx so you reach for an existing component instead of hand-rolling Tailwind divs.

### `get_component` (~136 tokens)

Get the full schema for one petal_components component: attrs, slots, defaults, allowed values, and a working HEEx usage example. Call this every time you are about to write a tag like <.button>, <.modal>, <.table>, or <.field> so the attrs and slots match the real library instead of training-data guesses.

Input parameters:

- `name` (string, required): Component function name without the leading dot (e.g. 'button', 'modal', 'field', 'text_input'). The HEEx tag is the same name prefixed with a dot: <.button>. Call list_components for the full invent…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 68
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 66
- 2026-07-26: 65

## Links

- Remote endpoint: https://mcp.petal.build/mcp
- Repository: https://github.com/petalframework/petal-components-mcp
- Website: https://petal.build/components/mcp
- Changelog RSS feed: https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/petalframework-petal-components-mcp/mcp