What are the risks of connecting to corewise.video?

No blocking issues were found in the static + spec checks. Overall trust grade A (94/100).

When was corewise.video last audited?

Last checked 2026-09-11; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

corewise.video

Item: corewise.video
Rating: 94
Author: wmcp.sh

https://corewise.video/mcp

94/100 · MCP Trust Grade · checked 2d ago · MCP 2025-06-18

Is the corewise.video MCP server safe to use?

Independent trust grade A (94/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches corewise.video for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-09-07 — behavioral baseline locked, no drift for 4 days. 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 — 4 tools · Search

extract_url

Start an AI extraction of a YouTube video, podcast, article, or PDF URL on CoreWise. Returns an extraction_id immediately after initialization. Initia

get_extraction

Get the status and results of a CoreWise extraction by id. While status is 'processing', poll every 20-30 seconds. When status is 'completed' the resp

get_transcript

Get the raw source transcript (or article/PDF text) of a CoreWise extraction by id. Available as soon as the extraction has been initialized — no need

search_public_extractions

Search CoreWise's public community library of extractions (videos, podcasts, articles, and PDFs already analyzed by other users). Returns titles, snip

Spec conformance20%100

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

Security (OWASP MCP)30%100

4 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%92

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

Tool hygiene15%80

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

Transparency / provenance15%90

HTTPS ✓
RFC 9728 oauth-protected-resource metadata ✓
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 corewise.video on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run corewise.video? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

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 — corewise.video grade A

Share on X Open card image

https://wmcp.sh/mcp/grade/corewise.video

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

HTML

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