Hololive MCP
Related Servers
Alternatives to Hololive MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and read entries, official social media accounts and identifiers, and history, with optional API-key or OAuth access to perform account-permitted actions safely through dry runs.18MIT
- AlicenseNot gradedqualityDmaintenanceExposes a public, read-only professional profile with tools to search resume evidence, fetch curated links, and generate career briefs for LLM agents.MIT
- AlicenseNot gradedqualityBmaintenanceEnables assistants to retrieve a public profile, search content, and fetch full documents with canonical links across biography, CV, articles, videos, courses, and tools.MIT

Upriver MCPofficial
AlicenseNot gradedqualityDmaintenanceProvides AI applications with real-time, evidence-backed context on creators, audiences, brands, trends, and sponsorships, including breakout topic search and browsing tools.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to answer questions about a personal site straight from its published JSON bundle — profile, posts, case studies, pages, projects, stats and small datasets — through seven read-only tools for listing, full-text search, fetching Markdown, and querying dataset rows, with no sign-in, database or write path.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to read RSS/Atom feeds, extract web page content as text or Markdown, search the web, and batch-fetch multiple URLs without building custom crawlers.5MIT
TDQS
Scored across 3 tools
Each tool targets a distinct resource and action: enumerating all talents, fetching a single talent's profile by slug, and fetching news headlines. There is no plausible way to confuse these three operations, and the descriptions reinforce the boundaries (list returns names/slugs, profile requires a slug from that list).
All three tools follow a clean verb_noun snake_case pattern: list_talents, get_talent_profile, get_recent_news. The verb choice also meaningfully distinguishes collection-level (list) from item-level (get) retrieval.
Three tools is on the lean side but each earns its place and covers a genuinely different need (roster, profile detail, news). It is a tightly scoped read-only scraping server, so the small surface is defensible rather than anemic.
The talent lifecycle is well covered: list_talents returns every slug, and get_talent_profile resolves any of them, so there are no dead ends. Minor gaps exist around filtering/searching by generation or branch and around fetching older news beyond the latest 10 items, but agents can work around both.