B+

bringyour.ai

Item: bringyour.ai
Rating: 87
Author: wmcp.sh

https://bringyour.ai/mcp

87/100 · MCP Trust Grade · checked 4h 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 — 7 tools · Developer Tools

preview_move

Free no-data preview for moving a harness between Claude Code and Codex. Returns feasibility copy only. Does not accept or return mappings, file paths

preview_build_setup

Free no-data preview for building a user's first Claude Code or Codex setup. Does not accept GitHub handles, generated memories, mappings, or file con

list_targets

List Bring Your AI target tools. No harness data is accepted or returned.

install_local_cli

Return no-data local install and MCP wiring commands. The remote server does not install anything and does not receive harness data.

list_products

List agent-readable Bring Your AI products and supported payment modes. No harness data is accepted.

quote_lifetime_license

Quote a Bring Your AI lifetime license in USD. Human checkout uses Stripe Payment Links; agent checkout can settle a Link-issued Stripe shared payment

start_checkout

Start checkout. With payment_mode=stripe_spt plus shared_payment_granted_token and buyer_email, settles a Stripe PaymentIntent and returns the signed

Spec conformance20%100

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

Security (OWASP MCP)30%100

7 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%84

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

Tool hygiene15%63

71% of tools have typed inputSchema
0/7 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 bringyour.ai 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 — bringyour.ai grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/bringyour.ai

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

HTML

<a href="https://wmcp.sh/mcp/grade/bringyour.ai"><img src="https://wmcp.sh/mcp/grade/bringyour.ai/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.