Home / MCP registry index / io.github.migueljdias/cuely

Cuely

io.github.migueljdias/cuely in the official MCP registry. Endpoint https://cuely.dev/api/mcp. Source: github.com/migueljdias/cuely.

The registry describes it as: Picks the stack, security and compliance setup for what you're building, with today's prices.

Connect it

The endpoint is live and asks for credentials before it lists its tools. Add it to your client:

claude mcp add --transport http cuely https://cuely.dev/api/mcp

{
  "mcpServers": {
    "cuely": {
      "url": "https://cuely.dev/api/mcp"
    }
  }
}

code --add-mcp '{"name":"cuely","type":"http","url":"https://cuely.dev/api/mcp"}'

Most clients open the server's sign-in page the first time they connect. If it wants an API key instead, the server's own docs say where to put it.

Check its tools after you sign in

We could not read this server's tools without an account, so nothing above says they are clean. Once you are signed in, your agent can pass the tool list it received to the check_mcp_tools tool on our MCP server, which runs the same tool-poisoning rules. A free developer key covers 10 checks a day, and your agent can get one in the same session with get_free_key. No account or card.

claude mcp add --transport http --scope user lazaretto "https://lazaretto.dev/mcp?ref=site"

Then ask your agent: Use Lazaretto to check the npm packages chalk@5.6.1 and chalk@5.3.0.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-migueljdias-cuely/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-migueljdias-cuely)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Security MCP servers