Rams
ai.rams/ramsVersion 1.2.0Design review for UI code and live pages: quick checks, 0-100 scored reviews, fixes as patches
Status
Responds164 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:32 UTC
- Latency
- 164 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://worker.rams.ai/mcpResponds164 msNo sign-in
Claude Code
claude mcp add --transport http rams https://worker.rams.ai/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: rams
Remote MCP server URL: https://worker.rams.ai/mcpCursor
{
"mcpServers": {
"rams": {
"url": "https://worker.rams.ai/mcp"
}
}
}VS Code
code --add-mcp '{"name":"rams","type":"http","url":"https://worker.rams.ai/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
quick_reviewFast design and accessibility check of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns the top issues with severity, category and file:line in about 10 seconds. Call it when the user pastes or uploads UI code, asks whether a design is good or accessible, or when you just wrote or changed a component, page or view. You do not need to ask first. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx, pasted/index.html) and the full code. Five quick checks cost one review credit (two on the free plan). It reads code only, not screenshots or URLs. It returns no score and no patch: fix the issues yourself. For a score or patches, use review_files. | No | No | No | No |
review_filesFull Rams design review of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns a 0-100 score (criticals cap it: one caps at 59, two at 49, three or more at 39), issues with severity, category, file:line, and concrete fixes as patches. Call it once at the end: before a commit, or when the user wants a score or a final check. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx). Each call uses one review credit. Reviewing a few files needs no permission. Ask the user before a whole-codebase audit (dozens of files), since it spends their allowance. For quick feedback while you work, use quick_review. | No | No | No | No |
review_urlReview a live public web page by its URL, no code needed. Rams opens the page at desktop (1440px) and phone (390px) widths, measures the rendered page and looks at both screenshots, then returns the top design issues (severity, category, where on the page, and a fix in plain words) with a 0-100 score. Use it when the user names a site or a page: "review rams.ai with Rams", "how does my landing page look?". It takes up to a minute and uses one review credit. Public pages only: no sign-in pages, localhost or private addresses. It returns no code patches. If the user has the code for the page, use quick_review or review_files on those files instead. | No | No | No | Yes |
usageCheck how many Rams reviews this account has used and how many are left. Free to call. It does not use a review. | No | Yes | Yes | No |
verify_fixesRe-check findings from an earlier Rams review against the updated code. Pass the new version of each file under the same path as before, plus the findings. Returns fixed or still present for each one. Free: it never counts against the user's quota. Use it after you fix the issues. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Repository
- Not given
- Categories (suggested)
- Design and mediaSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared