CoreWise
io.github.ryanportfolio/corewise · 1.0.0
Extract structured insights from videos, podcasts, articles, and PDFs with multi-model AI
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://corewise.video/mcpstreamable-httpAuthorizationoptional, secret: CoreWise API key as a Bearer token, e.g. 'Bearer cw_live_...'. Create one at https://corewise.video/profile under 'API & MCP Keys'. Optional: public library search works without a key; extract_url req
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- CoreWise 1.0.0
- Handshake time
- 233 ms
- HTTP status
- 200
The tools it lists (4, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
extract_urlStart 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 qu
get_extractionGet 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.
get_transcriptGet 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.
search_public_extractionsSearch 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.ryanportfolio/corewise, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 95 days ago. The registry entry · corewise.video