B+

xfms.vercel.app

Item: xfms.vercel.app
Rating: 88
Author: wmcp.sh

https://xfms.vercel.app/mcp/

88/100 · MCP Trust Grade · checked 3h ago · MCP 2025-06-18

✓ Watched since 2026-06-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 5 tools · Developer Tools

rank

Rank LLMs for a stated purpose. Returns a shortlist with weights, scores, and plain-English rationale per pick. Use when the user wants to see and com

pick

Return the single best LLM for a stated purpose. Concise output, no list. Use when the user has settled on the criteria and just wants one answer.

discover

Show which quality dimensions matter for a stated purpose, WITHOUT ranking any models. Returns the inferred weights and the discovery-walk trace. Usef

benchmark

Run a live A/B test against the engine's TOP 3 PICKS for a stated purpose — the engine chooses the candidates from the full catalog. Generates 5 repre

compare

Run a live A/B test between 2–5 user-specified models for a stated purpose. NO ranking step — the supplied model_ids ARE the candidate set. Generates

Spec conformance20%80

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✗ unknown method → -32602
✓ tools/list → 5 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

5 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%84

single-probe latency 1404ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%100

100% of tools have typed inputSchema
5/5 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade xfms.vercel.app on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — xfms.vercel.app grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/xfms.vercel.app

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/xfms.vercel.app/badge.svg)](https://wmcp.sh/mcp/grade/xfms.vercel.app)

HTML

<a href="https://wmcp.sh/mcp/grade/xfms.vercel.app"><img src="https://wmcp.sh/mcp/grade/xfms.vercel.app/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.