io.github.petalframework/petal-components-mcp
REMOTE · MCP.PETAL.BUILD · 2 COMPONENTS · SCANNED SEP 21
Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 298 tokens (~99/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.petalframework/petal-components-mcp server?
io.github.petalframework/petal-components-mcp is a hosted endpoint at https://mcp.petal.build/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.petal.build
claude mcp add --transport http petalframework-petal-components-mcp 'https://mcp.petal.build/mcp'
{
"mcpServers": {
"petalframework-petal-components-mcp": {
"url": "https://mcp.petal.build/mcp"
}
}
} {
"servers": {
"petalframework-petal-components-mcp": {
"type": "http",
"url": "https://mcp.petal.build/mcp"
}
}
} [mcp_servers.petalframework-petal-components-mcp] url = "https://mcp.petal.build/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"petalframework-petal-components-mcp": {
"type": "remote",
"url": "https://mcp.petal.build/mcp",
"enabled": true
}
}
} openclaw mcp add petalframework-petal-components-mcp --url 'https://mcp.petal.build/mcp' --transport streamable-http
mcp_servers:
petalframework-petal-components-mcp:
url: "https://mcp.petal.build/mcp" {
"McpServers": {
"petalframework-petal-components-mcp": {
"Transport": "http",
"Url": "https://mcp.petal.build/mcp"
}
}
} assistant mcp add petalframework-petal-components-mcp -t streamable-http -u 'https://mcp.petal.build/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp.petal.build/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.petal.build | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5d5a2f3a5bf5e29e2395a5b2c65f96b37ea |
| SANs: mcp.petal.build | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.petal.build. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| build. | present | 30770, 38839 | 8, 8 | Verified |
| petal.build. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.petal.build/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.petal.build/mcp | HTTPS enforced | 301 | https://mcp.petal.build/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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… |
No output schema declared.
No examples provided.
get_install_instructions ~101
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_components ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.petalframework/petal-components-mcp server?
io.github.petalframework/petal-components-mcp is listed in the public MCP registry as io.github.petalframework/petal-components-mcp. Phoenix LiveView component schemas from petal_components, exposed to AI coding assistants. This page covers its hosted endpoint (https://mcp.petal.build/mcp).
Is the io.github.petalframework/petal-components-mcp server safe to use?
io.github.petalframework/petal-components-mcp scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.petalframework/petal-components-mcp server expose?
io.github.petalframework/petal-components-mcp exposes 3 tools: get_install_instructions, list_components, get_component. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.
Does the io.github.petalframework/petal-components-mcp server require authentication?
No. We connected to io.github.petalframework/petal-components-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.petalframework/petal-components-mcp server still maintained?
io.github.petalframework/petal-components-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.