accueil / serveurs / Dev & Code / ai.rams/rams
ai.rams/rams
serveur MCP (Model Context Protocol) · rams 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que ai.rams/rams est sûr ?
Au dernier audit MCP Hub, le serveur MCP « ai.rams/rams » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- quick_review≈ 671 tokens
Fast 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.
Paramètres, retour & exemple (3)
Paramètresvia· string · optionnel
Set to "rules" when this call is made because of a standing instruction in a rules file (e.g. CLAUDE.md). Omit when a person asked for the review.files· array · requis
The UI code, one entry per file (up to 20): the real path, or for pasted code a path that fits it (pasted/Card.tsx), and the full codecontext· string · optionnel
Short label, e.g. the component or feature name
Exemple d'appel{"name": "quick_review", "arguments": {"files": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"ran": true, "issues": [], "message": "texte", "issueCount": 1}} - review_files≈ 911 tokens
Full 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.
Paramètres, retour & exemple (3)
Paramètresvia· string · optionnel
Set to "rules" when this call is made because of a standing instruction in a rules file (e.g. CLAUDE.md). Omit when a person asked for the review.files· array · requis
The UI code, one entry per file (up to 20): the real path, or for pasted code a path that fits it (pasted/Card.tsx), and the full codecontext· string · optionnel
Short label for this review, e.g. the feature or branch name
Exemple d'appel{"name": "review_files", "arguments": {"files": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"score": 1, "issues": [], "summary": "texte", "direction": "texte", "visualPair": {}, "reviewsUsed": 1, "reviewsLimit": 1, "detectedCounts": {}, "visualFindings": []}} - review_url≈ 767 tokens
Review 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.
Paramètres, retour & exemple (2)
Paramètresurl· string · requis
The page to review, e.g. https://rams.ai or rams.ai/pricingfocus· string · optionnel
Optional: what to put first, e.g. "mobile", "typography", "color"
Exemple d'appel{"name": "review_url", "arguments": {"url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"host": "texte", "score": 1, "scores": {}, "summary": "texte", "findings": [], "reviewsUsed": 1, "reviewsLimit": 1, "detectedCounts": {}}} - usage≈ 490 tokens
Check how many Rams reviews this account has used and how many are left. Free to call. It does not use a review.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "usage", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"plan": "texte", "used": 1, "limit": 1, "window": "texte", "pausedNow": true, "remaining": 1, "resumesAt": "texte", "fullReviews": {}, "overageBilling": true, "purchasedCredits": 1}} - verify_fixes≈ 617 tokens
Re-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.
Paramètres, retour & exemple (2)
Paramètresfiles· array · requis
The updated UI files (same paths as the original review)issues· array · requis
The findings to verify, as returned by review_files
Exemple d'appel{"name": "verify_fixes", "arguments": {"files": [], "issues": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"fixed": [], "present": [], "allClear": true}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».