{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-tldv","slug":"tldv","name":"Tldv","type":"mcp","url":"https://gitlab.com/tldv/tldv-mcp-server","page_url":"https://unfragile.ai/tldv","categories":["mcp-servers"],"tags":[],"pricing":{"model":"unknown","free":false,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-tldv__cap_0","uri":"capability://tool.use.integration.meeting.recording.access.via.mcp","name":"meeting-recording-access-via-mcp","description":"Exposes Google Meet, Zoom, and Microsoft Teams meeting recordings and metadata through the Model Context Protocol (MCP), allowing AI agents to query and retrieve meeting data without direct API integration. The server acts as a unified abstraction layer that translates MCP tool calls into authenticated requests to the tl;dv backend service, which handles OAuth token management and platform-specific API translation for each video conferencing provider.","intents":["I want my AI agent to access meeting recordings from multiple platforms through a single standardized interface","I need to retrieve meeting metadata and recordings programmatically without managing separate OAuth flows for each platform","I want to integrate meeting data into my agent's context without building custom API connectors for Google Meet, Zoom, and Teams"],"best_for":["AI agent developers building multi-platform meeting analysis workflows","Teams building internal tools that need to access meeting recordings across Google Workspace, Microsoft 365, and Zoom","Developers integrating meeting intelligence into LLM-powered applications"],"limitations":["Requires active tl;dv account with authenticated connections to each platform (Google Meet, Zoom, Teams) — cannot access recordings without prior setup","No built-in caching or local storage of recordings — all queries route through tl;dv service, introducing network latency","Read-only access to recordings; no capability to delete, modify, or re-upload meeting data","Rate limits and quota restrictions unknown — dependent on tl;dv service tier and platform API limits"],"requires":["tl;dv account with active subscription","OAuth credentials configured for at least one of: Google Workspace, Microsoft 365, or Zoom","MCP-compatible client (Claude Desktop, custom agent framework, etc.)","Network connectivity to tl;dv backend service"],"input_types":["meeting identifiers (platform-specific IDs or URLs)","query parameters (date range, participant filters, etc.)","structured MCP tool call schemas"],"output_types":["meeting metadata (title, participants, duration, timestamps)","transcript text or structured transcript objects","recording URLs or streaming endpoints","summary or key points (if tl;dv service provides)"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-tldv__cap_1","uri":"capability://search.retrieval.transcript.retrieval.and.search","name":"transcript-retrieval-and-search","description":"Retrieves full or partial meeting transcripts from tl;dv's indexed recording library and enables semantic or keyword-based search across meeting content. The MCP server translates search queries into tl;dv backend calls, which leverage pre-processed transcripts stored in tl;dv's database, returning matching segments with timestamps and speaker attribution for context-aware agent reasoning.","intents":["I want to search across all my meeting transcripts to find discussions about a specific topic","I need to retrieve exact quotes or segments from meetings with precise timestamps for my agent to reference","I want my agent to access meeting transcripts without downloading or storing full recording files locally"],"best_for":["Knowledge workers building agents that need to reference past meeting discussions","Teams using AI to analyze meeting patterns, decisions, or action items across multiple recordings","Developers building meeting-aware chatbots or search interfaces"],"limitations":["Search quality depends on tl;dv's transcription accuracy — OCR or speaker diarization errors will propagate to search results","No full-text indexing control from the MCP client — search capabilities limited to what tl;dv backend exposes","Transcript availability depends on recording completion and processing time — newly recorded meetings may not be immediately searchable","Unknown support for multi-language transcripts or language-specific search"],"requires":["tl;dv account with at least one completed and processed recording","MCP client with transcript search tool support","Authenticated connection to tl;dv backend"],"input_types":["search query strings (keywords or phrases)","optional filters (date range, participants, meeting title)","structured search parameters (if MCP schema supports)"],"output_types":["transcript segments with timestamps","speaker attribution and turn-taking data","relevance scores or match confidence (if provided)","meeting metadata linked to transcript matches"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-tldv__cap_2","uri":"capability://data.processing.analysis.meeting.summary.and.insights.retrieval","name":"meeting-summary-and-insights-retrieval","description":"Retrieves AI-generated summaries, key points, action items, and meeting insights from tl;dv's analysis engine through MCP tool calls. The server queries tl;dv's backend for pre-computed summaries and structured insights derived from meeting transcripts and recordings, returning formatted data that agents can use for decision-making or context enrichment without re-analyzing the full recording.","intents":["I want my agent to quickly understand the outcome and key decisions from a meeting without reading the full transcript","I need to extract action items and owners from meetings programmatically for task management integration","I want my agent to access meeting insights (decisions, risks, next steps) for downstream reasoning or reporting"],"best_for":["Agents building automated meeting follow-up workflows or action item tracking","Teams using AI to synthesize insights from large numbers of meetings","Developers building meeting-aware project management or CRM integrations"],"limitations":["Summary quality depends on tl;dv's AI model and analysis pipeline — hallucinations or missed context possible","Insights are pre-computed and static — cannot customize summary length, focus, or analysis approach per query","Unknown whether summaries are available for all recordings or only recent/premium-tier meetings","No control over summary language or format — locked to tl;dv's output schema"],"requires":["tl;dv account with summary/insights feature enabled (may require premium tier)","Completed and processed recordings with analysis results available","MCP client supporting summary retrieval tools"],"input_types":["meeting identifiers or recording IDs","optional parameters (summary type, detail level, if configurable)"],"output_types":["structured summary text","action items with owner/assignee information","key decisions or discussion points","risk flags or follow-up items","meeting metadata and timestamp references"],"categories":["data-processing-analysis","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-tldv__cap_3","uri":"capability://data.processing.analysis.multi.platform.meeting.metadata.aggregation","name":"multi-platform-meeting-metadata-aggregation","description":"Aggregates meeting metadata (participants, duration, date, platform source) across Google Meet, Zoom, and Microsoft Teams recordings through a unified MCP interface. The server queries tl;dv's backend to fetch and normalize metadata from each platform's API, presenting a consistent schema regardless of source platform, enabling agents to reason about meetings without platform-specific logic.","intents":["I want to query all meetings across my organization's platforms (Google Meet, Zoom, Teams) with a single API call","I need to filter or analyze meetings by participant, date, or duration without writing separate queries for each platform","I want my agent to understand which platform a meeting came from without exposing platform-specific details"],"best_for":["Enterprise teams using multiple video conferencing platforms","Agents building cross-platform meeting analytics or reporting","Developers building unified meeting management interfaces"],"limitations":["Metadata normalization may lose platform-specific fields or capabilities (e.g., Zoom breakout rooms, Teams recording settings)","Metadata freshness depends on tl;dv's sync frequency — real-time updates not guaranteed","Requires OAuth setup for each platform independently — cannot access meetings from platforms without configured credentials","Unknown support for archived or deleted meetings — may only expose active/recent recordings"],"requires":["tl;dv account with OAuth connections configured for desired platforms","MCP client supporting metadata query tools","Authenticated access to tl;dv backend"],"input_types":["filter parameters (date range, participant name, platform type, meeting title)","pagination parameters (limit, offset)","structured query schemas (if MCP supports)"],"output_types":["normalized meeting metadata objects","participant lists with roles/permissions","recording availability status","platform source attribution","timestamps and duration information"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-tldv__cap_4","uri":"capability://tool.use.integration.mcp.protocol.transport.abstraction","name":"mcp-protocol-transport-abstraction","description":"Implements the Model Context Protocol (MCP) server specification, translating MCP tool calls and resource requests into tl;dv backend API calls and returning results in MCP-compliant formats. The server handles MCP transport (stdio, SSE, or HTTP), request/response serialization, and error handling, allowing any MCP-compatible client (Claude Desktop, custom agents, etc.) to interact with tl;dv meeting data without direct API knowledge.","intents":["I want to use Claude or another MCP client to access my tl;dv meetings without writing custom API code","I need to integrate tl;dv into my existing MCP-based agent framework","I want to expose tl;dv capabilities to multiple clients through a standardized protocol"],"best_for":["Developers building MCP-compatible agents or tools","Teams using Claude Desktop or other MCP clients who want tl;dv integration","Organizations standardizing on MCP for AI tool integration"],"limitations":["MCP transport type (stdio, SSE, HTTP) unknown — may limit deployment scenarios","Error handling and timeout behavior not documented — unknown how server handles tl;dv backend failures","No built-in request queuing or retry logic documented — transient failures may propagate to clients","MCP schema definitions not provided — unknown exact tool/resource specifications"],"requires":["MCP-compatible client (Claude Desktop, custom MCP framework, etc.)","Node.js or runtime environment supporting the MCP server implementation","Network connectivity to tl;dv backend service","tl;dv account and credentials for authentication"],"input_types":["MCP tool call requests with parameters","MCP resource read/list requests","MCP protocol messages (initialization, capability negotiation)"],"output_types":["MCP tool call results with structured data","MCP resource content (text, JSON, etc.)","MCP protocol responses and error messages"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-tldv__cap_5","uri":"capability://tool.use.integration.oauth.credential.management.for.video.platforms","name":"oauth-credential-management-for-video-platforms","description":"Manages OAuth authentication flows and credential storage for Google Meet, Zoom, and Microsoft Teams through tl;dv's backend, allowing agents to access recordings without storing or managing platform-specific API keys. The MCP server delegates authentication to tl;dv's OAuth handlers, which refresh tokens and maintain secure credential storage, exposing only authenticated meeting data to the agent.","intents":["I want my agent to access meetings from multiple platforms without managing separate OAuth tokens","I need secure credential storage for video platform integrations without exposing keys to my agent code","I want to set up platform access once in tl;dv and reuse it across multiple agents or tools"],"best_for":["Teams managing multi-platform meeting access across multiple agents","Developers building agents that need secure, centralized credential management","Organizations with compliance requirements for API key storage and rotation"],"limitations":["Credential management is opaque — no visibility into token refresh cycles or expiration handling","OAuth setup must be completed in tl;dv UI before MCP server can access meetings — no programmatic OAuth flow from MCP client","Token revocation or permission changes in source platforms may not propagate immediately to MCP server","Unknown support for service accounts or non-interactive OAuth flows — may require manual re-authentication"],"requires":["tl;dv account with OAuth app credentials configured for each platform","User authorization completed in tl;dv UI for Google Meet, Zoom, and/or Teams","Active OAuth tokens maintained by tl;dv backend"],"input_types":["platform selection (Google Meet, Zoom, Teams)","optional scope/permission parameters (if configurable)"],"output_types":["authenticated access to platform-specific meeting data","implicit token management (no tokens exposed to MCP client)"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"high","permissions":["tl;dv account with active subscription","OAuth credentials configured for at least one of: Google Workspace, Microsoft 365, or Zoom","MCP-compatible client (Claude Desktop, custom agent framework, etc.)","Network connectivity to tl;dv backend service","tl;dv account with at least one completed and processed recording","MCP client with transcript search tool support","Authenticated connection to tl;dv backend","tl;dv account with summary/insights feature enabled (may require premium tier)","Completed and processed recordings with analysis results available","MCP client supporting summary retrieval tools"],"failure_modes":["Requires active tl;dv account with authenticated connections to each platform (Google Meet, Zoom, Teams) — cannot access recordings without prior setup","No built-in caching or local storage of recordings — all queries route through tl;dv service, introducing network latency","Read-only access to recordings; no capability to delete, modify, or re-upload meeting data","Rate limits and quota restrictions unknown — dependent on tl;dv service tier and platform API limits","Search quality depends on tl;dv's transcription accuracy — OCR or speaker diarization errors will propagate to search results","No full-text indexing control from the MCP client — search capabilities limited to what tl;dv backend exposes","Transcript availability depends on recording completion and processing time — newly recorded meetings may not be immediately searchable","Unknown support for multi-language transcripts or language-specific search","Summary quality depends on tl;dv's AI model and analysis pipeline — hallucinations or missed context possible","Insights are pre-computed and static — cannot customize summary length, focus, or analysis approach per query","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.25,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.050Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=tldv","compare_url":"https://unfragile.ai/compare?artifact=tldv"}},"signature":"NgCjm1wHwvi8arTM2CC3cstR16FWVVmF6qxig+2mZtlwoIlW2HFWWYl5mpmDU/l4GLj+DvCeYsv4VVK/7xOjBg==","signedAt":"2026-06-22T13:06:19.617Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/tldv","artifact":"https://unfragile.ai/tldv","verify":"https://unfragile.ai/api/v1/verify?slug=tldv","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}