Valet
REMOTE · API.VALET.DEV · SCANNED OCT 4
Get share links, publish and manage websites, artifacts and agents. No account needed.
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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (call_site_connector). See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7697 tokens (~265/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management69
- Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 18 additions. See how to fix → Fail
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
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Valet MCP server?
Valet is a hosted endpoint at https://api.valet.dev/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 · api.valet.dev
claude mcp add --transport http valetdotdev-valet 'https://api.valet.dev/mcp'
{
"mcpServers": {
"valetdotdev-valet": {
"url": "https://api.valet.dev/mcp"
}
}
} {
"servers": {
"valetdotdev-valet": {
"type": "http",
"url": "https://api.valet.dev/mcp"
}
}
} [mcp_servers.valetdotdev-valet] url = "https://api.valet.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"valetdotdev-valet": {
"type": "remote",
"url": "https://api.valet.dev/mcp",
"enabled": true
}
}
} openclaw mcp add valetdotdev-valet --url 'https://api.valet.dev/mcp' --transport streamable-http
mcp_servers:
valetdotdev-valet:
url: "https://api.valet.dev/mcp" {
"McpServers": {
"valetdotdev-valet": {
"Transport": "http",
"Url": "https://api.valet.dev/mcp"
}
}
} assistant mcp add valetdotdev-valet -t streamable-http -u 'https://api.valet.dev/mcp'
{
"mcpServers": {
"valetdotdev-valet": {
"type": "http",
"url": "https://api.valet.dev/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.
- 4 Oct 26 −4
- Stability: pass → fail ▼ security
- Tool “rename_site” was removed ▼ security
- Tool “delete_site” was removed ▼ security
- Tool “get_design_system” was removed ▼ security
- Tool “get_site” was removed ▼ security
- Tool “list_sites” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “delete_resource”, which the server declares destructive security
- New tool “delete_service”, which the server declares destructive security
- New tool “detach_connector”, which the server declares destructive security
- New tool “detach_resource”, which the server declares destructive security
- New tool “publish_app”, which the server declares destructive security
- New tool “publish_skill”, which the server declares destructive security
- New tool “rename_service”, which the server declares destructive security
- New tool “set_env_vars”, which the server declares destructive security
- Tool “get_connector_client” rewrote its description, which is the text the model reads security
- Tool “publish_site” rewrote its description, which is the text the model reads security
- Schema quality: 313 → 265 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- New tool “attach_connector” functional
- New tool “attach_resource” functional
- New tool “get_build” functional
- New tool “get_service” functional
- New tool “get_skill” functional
- New tool “get_skill_file” functional
- New tool “get_source” functional
- New tool “list_resource_catalog” functional
- New tool “list_services” functional
- New tool “list_skills” functional
- 28 Sept 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 Sept 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
- 14 Sept 26 +2
- Stability: fail → pass ▲ security
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 86.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 76 to 80.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73.
- 5 Sept 26 72
- Tool “publish_site” rewrote its description, which is the text the model reads security
- Tool “rename_site” rewrote its description, which is the text the model reads security
- “publish_site” reworded the description of “name” cosmetic
- “rename_site” reworded the description of “new_name” cosmetic
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 8 Oct 2026 · Probed https://api.valet.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.valet.dev | CN=YE2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 597d3cbe8de81bc95955470c861a475384b |
| SANs: api.valet.dev | ||||||
| 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 api.valet.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| valet.dev. | 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://api.valet.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.valet.dev/mcp | HTTPS enforced | 301 | https://api.valet.dev/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 →
set_service_access Set website or app access ~310
Set who can reach a website or app: public serves it to anyone who has the link, private serves it only to members of the organization that owns it after they sign in to Valet, and password serves it to anyone who enters a shared visitor password. Pass kind to say which you mean; a name holding another kind is then refused rather than changed. Apps can be changed only on a server with app access turned on. Requires connecting a Valet account. Password mode takes the password as the password argument. It is a shared visitor password the owner hands to whoever should see the service, not a Valet credential, and it is at most 72 bytes.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | The kind you mean. Omit to change whatever the name holds; give it to have a name holding another kind refused. |
| mode | string | yes | Required. The access mode. public serves it to anyone who has the link. private serves it only to members of the organization that owns it. password serves it to anyone who enters the shared visitor… |
| name | string | yes | Required. The website's or app's name. |
| org_name | string | – | The Valet organization it belongs to. Omit to use the organization the account joined first. |
| password | string | – | The shared visitor password. Required for password mode and rejected for the others. Anyone who enters it can open the service, so its owner passes it to whoever should see it. At most 72 bytes. |
No output schema declared.
No examples provided.
share_service Share a website by email ~407
Share a website with specific people by email, whether it is private or password-protected — sharing does not change who else can reach it. Each address is mailed a link from Valet that opens the site; the recipient needs no Valet account of their own, only the link, so anyone holding the email can open the site and forwarding it forwards access. Only websites can be shared by email so far; an app is refused. Sharing again with an address that already has access re-sends the same link rather than creating a second one. Requires connecting a Valet account.
| Name | Type | Req | Description |
|---|---|---|---|
| access_ttl | string | – | How long the first open starts access for, after which the link stops working, such as 30m or 7d (units: s, m, h, d). Omit for access that never expires this way. Composes with expires_in: the unopen… |
| emails | array | yes | Required. The email addresses to share the site with, at most 10 at a time. Sharing again with an address that already has access re-sends the same link rather than creating a second one. |
| expires_in | string | – | How long from now the link works if nobody has opened it yet, such as 24h or 7d (units: s, m, h, d). Omit for a link that never expires this way. |
| kind | string | – | The kind you mean. Omit to share whatever the name holds; give it to have a name holding another kind refused. Only a website can be shared by email so far. |
| message | string | – | An optional note included in the email, shown to the recipient as a quote beside the link. At most 500 characters. |
| name | string | yes | Required. The website's name. |
| org_name | string | – | The Valet organization the site belongs to. Omit to use the organization the account joined first. |
No output schema declared.
No examples provided.
unset_env_vars Unset environment variables ~174
Remove environment variables set on an app or agent, and restart it once if it is running. This removes the service's own variables only; an organization variable it inherits is not touched. A variable a connector or channel references, or one a resource set, is refused: the answer names the holder and what frees it. A channel the agent owns is destroyed with destroy_channel; a resource's variables leave only when the resource is detached. A name that is not set is reported and does not fail the call. Requires connecting a Valet account.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Required. The app's or agent's name. |
| names | array | yes | Required. The variable names to remove. |
| org_name | string | – | The Valet organization it belongs to. Omit to use the organization the account joined first. |
No output schema declared.
No examples provided.
unshare_service Revoke website shares ~201
Revoke people's shares of a website, by email. Each address's link stops working at once, and revoking is permanent: sharing again with the same address mails a new link. This cannot be undone, so confirm the addresses with the user first. An address with no share is reported, not refused. Sharing does not change who else can reach the site. Only a website can be shared by email so far; an app is refused. Requires connecting a Valet account.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Required. The email addresses whose shares to revoke, at most 10 at a time. |
| kind | string | – | The kind you mean. Omit to act on whatever the name holds; give it to have a name holding another kind refused. |
| name | string | yes | Required. The website's name. |
| org_name | string | – | The Valet organization the website belongs to. Omit to use the organization the account joined first. |
No output schema declared.
No examples provided.
What is the Valet MCP server?
Valet is an MCP server listed in the public MCP registry as io.github.valetdotdev/valet. Get share links, publish and manage websites, artifacts and agents. No account needed. This page covers its hosted endpoint (https://api.valet.dev/mcp).
Is the Valet MCP server safe to use?
Valet scores 73 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 Valet MCP server expose?
Valet exposes 54 tools: attach_channel, attach_connector, attach_resource, attach_skill, call_connector, and 49 more. Their descriptions and schemas cost roughly 13,337 tokens of context every time the server is loaded.
Does the Valet MCP server require authentication?
No. We connected to Valet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Valet MCP server still maintained?
Valet is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.