A-

mcp.fryd.app

Item: mcp.fryd.app
Rating: 90
Author: wmcp.sh

https://mcp.fryd.app/mcp

90/100 · MCP Trust Grade · checked 6h 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 · Database

search_planting_plans

Search Fryd garden planting plan templates. Extracts crop names, light conditions and ground type from the user prompt to find matching plans. Use sea

get_plant_profile

Look up detailed information about a plant or variety. Returns a comprehensive plant profile including sowing/planting/harvest seasons, spacing, light

check_companion_planting

Check whether two plants are compatible companions in the garden (Mischkultur). Returns compatibility (good/neutral/bad), and lists good and bad neigh

get_seasonal_calendar

Find out which plants can be sown, pre-cultivated, or harvested in a given month. Optionally adjusted for a specific USDA hardiness zone or region. Re

search_crops

Search the Fryd plant database (3,000+ varieties) by name. Returns a list of matching crops with IDs, descriptions, and whether each is a species or v

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ 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%70

single-probe latency 3309ms (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 mcp.fryd.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 — mcp.fryd.app grade A-

Share on X Open card image

https://wmcp.sh/mcp/grade/mcp.fryd.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 A-](https://wmcp.sh/mcp/grade/mcp.fryd.app/badge.svg)](https://wmcp.sh/mcp/grade/mcp.fryd.app)

HTML

<a href="https://wmcp.sh/mcp/grade/mcp.fryd.app"><img src="https://wmcp.sh/mcp/grade/mcp.fryd.app/badge.svg" alt="MCP Trust Grade A- · 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.