CoreWise
REMOTE · COREWISE.VIDEO · SCANNED SEP 24
Extract structured insights from videos, podcasts, articles, and PDFs with multi-model AI
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 659 tokens (~164/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the CoreWise MCP server?
CoreWise is a hosted endpoint at https://corewise.video/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · corewise.video
claude mcp add --transport http ryanportfolio-corewise 'https://corewise.video/mcp'
{
"mcpServers": {
"ryanportfolio-corewise": {
"url": "https://corewise.video/mcp"
}
}
} {
"servers": {
"ryanportfolio-corewise": {
"type": "http",
"url": "https://corewise.video/mcp"
}
}
} [mcp_servers.ryanportfolio-corewise] url = "https://corewise.video/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ryanportfolio-corewise": {
"type": "remote",
"url": "https://corewise.video/mcp",
"enabled": true
}
}
} openclaw mcp add ryanportfolio-corewise --url 'https://corewise.video/mcp' --transport streamable-http
mcp_servers:
ryanportfolio-corewise:
url: "https://corewise.video/mcp" {
"McpServers": {
"ryanportfolio-corewise": {
"Transport": "http",
"Url": "https://corewise.video/mcp"
}
}
} assistant mcp add ryanportfolio-corewise -t streamable-http -u 'https://corewise.video/mcp'
{
"mcpServers": {
"ryanportfolio-corewise": {
"type": "http",
"url": "https://corewise.video/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://corewise.video/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=corewise.video | CN=YE1,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5c267a6e061ea7c28f57f93e28c5c286770 |
| SANs: corewise.video | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of corewise.video. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| video. | present | 42529 | 8 | Verified |
| corewise.video. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-eval' 'sha256-qOhFsq0QMV2REqNwk5hGH5bZE9SkX6gt6yeyKdYPv+U=' https://challenges.cloudflare.com https://www.youtube.com https://s.ytimg.com; style-src 'self' 'unsafe-inline'; font-src 'self' data: https:; img-src 'self' data: blob: https: http:; media-src 'self' blob: https://storage.googleapis.com https://media.corewisevideo.com; connect-src 'self' https: wss:; frame-src 'self' https://challenges.cloudflare.com https://www.youtube.com https://www.youtube-nocookie.com; worker-src 'self' blob:; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer-when-downgrade |
| permissions-policy | geolocation=(), microphone=(self), camera=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://corewise.video/mcp | Verified | 200 | |
| http (plaintext) | http://corewise.video/mcp | HTTPS enforced | 301 | https://corewise.video:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
extract_url ~186
Start an AI extraction of a YouTube video, podcast, article, or PDF URL on CoreWise. Returns an extraction_id immediately after initialization. Initialization normally takes a few seconds but can take up to 2 minutes for videos without captions or for PDFs. The extraction itself then runs for 1-7 minutes: poll with get_extraction every 20-30 seconds until status is 'completed'. Results include a cross-validated synthesis plus per-model summaries. Requires an API key (create one at corewise.video, Profile page, 'API & MCP Keys'). Each call consumes one extraction from the key owner's monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | – | Which AI models to run (1-6). Default: ['openai', 'gemini']. More models cost more time. |
| url | string | yes | The video, podcast, article, or PDF URL to extract insights from. |
No output schema declared.
No examples provided.
get_extraction ~101
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 response contains the structured synthesis (JSON object: summary, takeaways, highlights, notable quotes) and per-model markdown summaries. Works on your own extractions (API key required) and on public community extractions.
| Name | Type | Req | Description |
|---|---|---|---|
| extraction_id | string | yes | The extraction id returned by extract_url. |
No output schema declared.
No examples provided.
get_transcript ~163
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 to wait for 'completed'. Transcripts can be very long, so results are paged: pass 'offset' and 'max_chars' to fetch further chunks when 'truncated' is true. Works on your own extractions (API key required) and on public community extractions.
| Name | Type | Req | Description |
|---|---|---|---|
| extraction_id | string | yes | The extraction id returned by extract_url or found via search. |
| max_chars | number | – | Max characters to return (default 100000, max 200000). |
| offset | number | – | Character offset to start from (default 0). Use with max_chars to page. |
No output schema declared.
No examples provided.
search_public_extractions ~96
Search CoreWise's public community library of extractions (videos, podcasts, articles, and PDFs already analyzed by other users). Returns titles, snippets, and share URLs. Useful to check whether a video has already been extracted before starting a new extraction. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 25). |
| query | string | yes | Search terms matched against titles and content. |
No output schema declared.
No examples provided.
What is the CoreWise MCP server?
CoreWise is an MCP server listed in the public MCP registry as io.github.ryanportfolio/corewise. Extract structured insights from videos, podcasts, articles, and PDFs with multi-model AI. This page covers its hosted endpoint (https://corewise.video/mcp).
Is the CoreWise MCP server safe to use?
CoreWise scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CoreWise MCP server expose?
CoreWise exposes 4 tools: extract_url, get_extraction, get_transcript, search_public_extractions. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.
Does the CoreWise MCP server require authentication?
No. We connected to CoreWise without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CoreWise MCP server still maintained?
CoreWise is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.