Source-first AI knowledge control tower MCP server for YouTube, Bilibili, RSSHub, and RSS.
{
"mcpServers": {
"io-github-xiaojiou176-open-sourceharbor-mcp": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Source-first AI knowledge control tower MCP server for YouTube, Bilibili, RSSHub, and RSS.
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for io.github.xiaojiou176-open/sourceharbor-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Proof-first AI knowledge control tower for source intake, grounded search, and agent workflows, with one shared Web/API/MCP truth and strong YouTube/Bilibili lanes.
See It In 30 Seconds · Run Locally · No-Boot Tour · Docs Home · MCP Quickstart · Builders · Distribution Status · Starter Packs · Media Kit · Sample Corpus · Proof · Project Status · Why It Stands Out · Discussions
SourceHarbor helps you turn long-form sources into grounded search results, knowledge cards, traceable job runs, and MCP-ready operations. It stays source-first and proof-first: you can inspect it, run it locally, and verify each surface instead of trusting product copy on vibes alone.
Three quick reasons developers keep reading:
The honest intake boundary today is:
That intake split now lives behind one shared template catalog instead of
separate Web-only presets: the /subscriptions front door, HTTP API, and MCP
surface all point at the same strong-supported vs generalized intake contract.
It is strongest when you read it as a control tower for source intake:
SourceHarbor is a multi-surface product repo, not a single skill package.
Public starter packs and plugin-grade skill surfaces are adoption layers inside
that repo. They are not the whole product, and they are not raw exports of the
internal .agents/skills tree.