# Rams (remote · worker.rams.ai)

Design review for UI code: 291 rules, scored 0-100 with fixes and git-applyable patches.

- Trust score: 80/100 (high trust)
- Change this week: +9
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `worker.rams.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ai-rams-rams/worker.md), [page](https://verifymcp.io/servers/ai-rams-rams/worker)

## Channel facts

- Endpoint: `https://worker.rams.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 322 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-rams-rams https://worker.rams.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-rams-rams]
url = "https://worker.rams.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-rams-rams": {
      "type": "remote",
      "url": "https://worker.rams.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-rams-rams --url https://worker.rams.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-rams-rams:
    url: "https://worker.rams.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-rams-rams": {
      "type": "http",
      "url": "https://worker.rams.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 79, +1)

- [functional] Schema quality: good → excellent

### 2026-08-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 77, +4)

- [functional regression] Schema quality: 224 → 308
- [functional] First check of Tool coverage: 67
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server
- [functional] New tool “verify_fixes”

### 2026-07-30 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 70)

First indexed and scored.

## MCP tools (3)

### `usage` (~44 tokens)

Rams review quota

Check how many Rams reviews this workspace has used and has left (rolling 30 days, shared between the GitHub App and MCP). Free to call — does not consume a review.

### `review_files` (~194 tokens)

Rams design review

Run a Rams design review over UI files (React, Vue, Svelte, CSS). 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. Use before committing UI changes to catch accessibility and design problems. TOKEN COST WARNING: reading and sending files consumes the CALLING agent's context and token budget, roughly proportional to the code sent. Reviewing a handful of changed screens is cheap; a whole-codebase audit in many batches can consume a large share of the user's model allowance — warn the user and get their OK before starting one, and prefer reviewing the highest-traffic screens.

Input parameters:

- `context` (string): Short label for this review, e.g. the feature or branch name
- `files` (array, required): UI files to review (up to 20)

Output parameters:

- `detectedCounts` (object)
- `direction` (string): What the change is trying to be — judgment before findings
- `issues` (array)
- `reviewsLimit` (number|null): null = unlimited (Team overage applies instead)
- `reviewsUsed` (number)
- `score` (number): 0-100; confirmed criticals cap it — one at 59, two at 49, three or more at 39
- `summary` (string)

### `verify_fixes` (~84 tokens)

Verify Rams fixes landed

Re-check previous review_files findings against updated file contents. Returns fixed vs still-present per finding. Much cheaper and faster than a full re-review; does NOT consume review quota. Use after applying fixes.

Input parameters:

- `files` (array, required): The updated UI files (same paths as the original review)
- `issues` (array, required): The findings to verify, as returned by review_files

Output parameters:

- `allClear` (boolean): true when nothing remains, including no remaining criticals
- `fixed` (array)
- `present` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-rams-rams/worker#diagnostics

## Score history

- 2026-08-03: 80
- 2026-08-02: 79
- 2026-08-01: 78
- 2026-07-31: 77
- 2026-07-30: 73
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 71
- 2026-07-26: 70

## Links

- Remote endpoint: https://worker.rams.ai/mcp
- Authorisation metadata: https://worker.rams.ai/.well-known/oauth-protected-resource/mcp
- Website: https://www.rams.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-rams-rams/worker/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-rams-rams/worker/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-rams-rams/worker