mcp_obsidian_streamable_http · job 79%mcp_obsidian_2 · job 78%solomd · job 75%mcp_obsidian_advanced · job 77%turbovault · job 90%mcp_obsidian_4 · job 83%Brain Graph · job 76%MCP RAGdown · job 74%seeklink · job 72%SoDam-WikiMate for Codex · job 71%sodam_wikimate · job 72%Obsidian Semantic MCP · job 75%Obsidian Vault MCP · job 75%gosidian · job 74%Obsidian Guarded MCP · job 82%Duckuments MCP · job 79%Obsidian AGI Workspace MCP · job 76%Obsidian Knowledge MCP · job 75%okc-mcp · job 72%Ragnarok · job 76%Obsidian RAG MCP · job 80%EchoBrain Local · job 75%OMGBase · job 70%ragmark · job 82%Obsidian CRUD MCP · job 76%Obsidian Brain · job 79%Context Layer · job 78%Knowledge Base · job 71%Pebble Index MCP · job 75%Obsidian Turbocharged · job 73%Obsidian Remote REST API · job 73%Vaults Hub · job 79%Knowledgebase MCP · job 76%MCP Server for Obsidian · job 75%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series