Rams
REMOTE · WORKER.RAMS.AI · SCANNED AUG 3
Design review for UI code: 291 rules, scored 0-100 with fixes and git-applyable patches.
Available components
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. How we score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 322 tokens (~107/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · worker.rams.ai
claude mcp add --transport http ai-rams-rams https://worker.rams.ai/mcp
[mcp_servers.ai-rams-rams] url = "https://worker.rams.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-rams-rams": {
"type": "remote",
"url": "https://worker.rams.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-rams-rams --url https://worker.rams.ai/mcp --transport streamable-http
mcp_servers:
ai-rams-rams:
url: "https://worker.rams.ai/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 2 Aug 26 +1
- Schema quality: good → excellent functional
- 1 Aug 26 +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.
- 31 Jul 26 +4
- 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 See what changed → functional
- New tool “verify_fixes” functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://worker.rams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=worker.rams.ai | CN=YR1,O=Let's Encrypt,C=US | 22 Jul 2026 | 20 Oct 2026 | RSA 2048 | SHA256-RSA | 5886e35e4c8ce9bbef73b8e698bb1cee81a |
| SANs: worker.rams.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of worker.rams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| rams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://worker.rams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://worker.rams.ai/mcp | HTTPS enforced | 301 | https://worker.rams.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
review_files Rams design review ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Short label for this review, e.g. the feature or branch name |
| files | array | yes | UI files to review (up to 20) |
| Name | Type | Req | Description |
|---|---|---|---|
| detectedCounts | object | yes | — |
| direction | string | — | What the change is trying to be — judgment before findings |
| issues | array | yes | — |
| reviewsLimit | number|null | yes | null = unlimited (Team overage applies instead) |
| reviewsUsed | number | yes | — |
| score | number | yes | 0-100; confirmed criticals cap it — one at 59, two at 49, three or more at 39 |
| summary | string | yes | — |
No examples provided.
usage Rams review quota ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_fixes Verify Rams fixes landed ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | The updated UI files (same paths as the original review) |
| issues | array | yes | The findings to verify, as returned by review_files |
| Name | Type | Req | Description |
|---|---|---|---|
| allClear | boolean | yes | true when nothing remains, including no remaining criticals |
| fixed | array | yes | — |
| present | array | yes | — |
No examples provided.