Home / MCP registry index / io.github.Nutlope/inspo

io.github.Nutlope/inspo

io.github.Nutlope/inspo in the official MCP registry. Endpoint https://inspomcp.dev/api/mcp. Source: github.com/Nutlope/inspo.

The registry describes it as: Real production websites for coding agents: palettes, fonts, fold autopsies and reference JSX.

We read its 15 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

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

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_screens get_screen get_design_system find_similar compare find_by_color find_examples_for_macrostructure list_collections get_filters get_site_pages find_components get_collection find_reference_components recommend get_reference_jsx

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

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

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. What we found across the registry.

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