design.regards/mcp · v1.0.0 · design
regards.design is healthy: it completed an MCP handshake in 2831 ms and exposes 10 tools.
Search real website sections from hand-picked sites by look, for design references and inspiration.
Endpoint: https://mcp.regards.design/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 10 |
| Latency | 2831 ms |
| Last checked (UTC) | 2026-11-09T22:25:32.580Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-09T22:25:32.580Z | Healthy | 2831 |
search_sections | Find sections of real websites to design from, by how they look, what they show and say, and how unusual they are. Then view_section the most promising hits (a summary is one line), widen from the ones that work with similar_sections, and in every later search, similar_sections too, pass every key y |
upload_image | Get a link to send a picture to (a screenshot, a mockup, a photo of a sketch), to search sections with it: for agents that can run a shell command. Send the file with the curl command in the answer; it answers with the picture's id, which goes in search_sections' image, with q saying what you want f |
search_interactions | Search a library of interactions recorded on live websites (hovers, clicks, focus states, scroll reveals, scroll-linked motion, loops, menu glides), each measured in the browser. Use it when the work is motion: a hover state, a menu, a reveal, an easing curve or a duration to choose, "make this feel |
similar_sections | Sections from any site that look and read like the given ones, by their screenshots and what they show. Use it to widen from hits you liked, or to find alternatives to a section you have. What is like the ones you liked includes ones you've seen: pass every key you've been shown as exclude_keys. q s |
get_section | One section in full: its kind, summary, novelty and whether it moves (how certain, what kind of motion), its annotation (hit.annotation: how it is laid out and presented, its style tags, the details a designer would point out, each with its kind, a short name for its technique and where it is, and w |
page_sections | A captured page's sections in order, top to bottom, each with its kind, summary, novelty and geometry: the page's structure and rhythm. Use it to see the whole page around a section you found, or to compare how sites build a page. page is a page id (hit.page.id); a section key works too. include add |
view_section | See a section: one image of its screenshot tiles stitched top to bottom (every part of a long section), its long edge at most max_px. Use it to judge a section by its pixels before you choose, describe or build from it: the summary is one line. context_px adds that many page px of the sections above |
list_boards | The user's boards on regards.design, where they keep sections they liked: each board's id, name, how many sections it holds, whether it is shared by link, and its page (url). last is the board save_to_board uses when none is named; most and sectionsEach are how many boards the plan keeps (null: as m |
read_board | One of the user's boards on regards.design: its sections in the order the user keeps them, each as search_sections gives a hit (key, kind of section, summary, novelty, whether it moves, links) without match. Use it to start from what the user saved, e.g. "use my Pricing board": view_section shows an |
save_to_board | Save sections to one of the user's boards on regards.design, so they keep what they liked and find it there later. keys are section keys ("page/section", hit.key), up to 24. board is a board's id or name; a name that matches none of their boards makes a new board with it. Left out, the board saved t |