CoreWise
REMOTE · COREWISE.VIDEO · SCANNED AUG 3
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 →
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 Usability73
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · corewise.video
claude mcp add --transport http ryanportfolio-corewise 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 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 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- 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 64
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 3 Aug 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=E8,O=Let's Encrypt,C=US | 23 May 2026 | 21 Aug 2026 | ECDSA 256 | ECDSA-SHA384 | 5c2acc45292d0bfd952ed93f2b9da13a20a |
| SANs: corewise.video | ||||||
| CN=E8,O=Let's Encrypt,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 Mar 2024 | 12 Mar 2027 | ECDSA 384 | SHA256-RSA | 63959363c24e7082715918bfc3d7ed56 |
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=() |
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.
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.