bryan-protocol-mcp
Related Servers
Alternatives to bryan-protocol-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables retrieval of biomedical evidence from PubMed, Europe PMC, ClinicalTrials.gov and openFDA, returning passages with server-issued citation handles so that citations and verbatim quotes in an answer can be deterministically audited for authenticity.717 PyPIApache 2.0
- AlicenseCqualityBmaintenanceEnables users to search scientific literature metadata across OpenAlex, Europe PMC, and Crossref, verify citations, retractions, source quotes, and claims, and build or export hash-chained evidence ledgers with explicit provenance and limitations.355Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search and ask questions across a local hybrid-retrieval index of scattered notes, documents, PDFs, and chat logs, returning section-level citations and agent-usable tools, resources, and prompts.-
- AlicenseNot gradedqualityCmaintenanceEnables local read-only search and retrieval of approved, current evidence via hybrid lexical and dense methods, with tools to get exact source spans, answer from cited passages, and create and verify recheckable evidence packets.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to query locally indexed notes, docs, chat logs, and other files via hybrid vector/BM25 retrieval with section-level citations. Exposes tools, resources, and prompts for searching and asking over the indexed content.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search a locally indexed second brain built from scattered notes, docs, PDFs, and chat exports, returning hybrid vector-plus-keyword results with section-level citations rather than whole files.-
TDQS
Scored across 7 tools
Several tools target overlapping questions about Bryan's positions: what_would_bryan_do, check_stance_and_changes, get_official_protocol, and search_archive can all plausibly answer 'what does Bryan think about X'. The descriptions differentiate them somewhat (scenario dossier vs. chronological stance tracking vs. Tier 1 only vs. broad search), but an agent could still misselect among the four.
Most names follow a clean verb_noun snake_case pattern (get_protocol_overview, get_official_protocol, check_stance_and_changes, search_archive, get_document, list_sources). The outlier is the question-style 'what_would_bryan_do', which breaks convention but is memorable and domain-appropriate.
Seven tools is well within the ideal 3-15 range for a knowledge-retrieval server. Each tool has a plausible distinct role (overview, targeted lookup, scenario dossier, stance tracking, search, fetch, list), so nothing feels padded.
The surface covers the core lifecycle of a RAG-style knowledge server: discover (overview/list_sources), search (search_archive), and fetch (get_document), plus specialized protocol/stance lookups. Minor gaps exist (e.g., no explicit topic/section enumeration tool beyond the overview, no related-documents or cross-source comparison), but agents can work around these via search_archive and get_document.