Is the Valetdotdev Valet MCP server down?

mcp-registry/io.github.valetdotdev/valet · v2.0.0

healthy
Last checked 2026-10-27 01:56 UTC · handshake 224ms

As of 2026-10-27 01:56 UTC, the Valetdotdev Valet MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
99.8%
checks observed
4,755
outages (90d)
11
tools
62

Get share links, publish and manage websites, artifacts and agents. No account needed.

Point your MCP client at this streamable-http endpoint: https://api.valet.dev/mcp

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 4 warning(s) across 62 tool(s); ~20,390 tokens of tool definitions.
Scores higher than 18% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~20,390 tokens per session — more than 95% of servers.
80 → 80 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost35
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (5)

62 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

Loading this server's tool list costs an agent ~20,390 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

Handshake + tools/list takes ~1,563 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 25 tool(s) removed and 42 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.valetdotdev/valet"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.valetdotdev/valet"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.valetdotdev%2Fvalet.svg)](https://glimind.com/server/mcp-registry%2Fio.github.valetdotdev%2Fvalet?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.valetdotdev%2Fvalet?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.valetdotdev%2Fvalet.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.valetdotdev%2Fvalet.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.valetdotdev%2Fvalet?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1110b6f4d6f0051c…, first seen 2026-10-21, included at leaf 40638 of 76,719. Version history · verify what your client received.

Tools (62)

Compare: most reliable communication servers · most reliable security servers · most reliable devops servers · most reliable knowledge servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Valetdotdev Valet MCP server down right now?

As of 2026-10-27 01:56 UTC, the Valetdotdev Valet MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Valetdotdev Valet MCP server provide?

Valetdotdev Valet MCP server advertises 62 tools, including attach_channel, attach_connector, attach_resource, attach_skill, call_connector.

How do I install Valetdotdev Valet MCP server?

Point your MCP client at this streamable-http endpoint: https://api.valet.dev/mcp

Is the Valetdotdev Valet MCP server safe to connect to an AI agent?

Glimind scanned all 62 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Valetdotdev Valet MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve