{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-currents","slug":"currents","name":"Currents","type":"mcp","url":"https://github.com/currents-dev/currents-mcp","page_url":"https://unfragile.ai/currents","categories":["mcp-servers","testing-quality"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-currents__cap_0","uri":"capability://tool.use.integration.playwright.test.failure.detection.and.ingestion.from.currents","name":"playwright test failure detection and ingestion from currents","description":"Integrates with Currents CI/CD platform to receive real-time notifications of Playwright test failures via MCP protocol, parsing failure metadata including test name, error messages, stack traces, and execution context. The MCP server acts as a bridge between Currents' test reporting infrastructure and AI agents, enabling agents to subscribe to failure events and access structured test execution data without polling.","intents":["I want my AI agent to automatically receive notifications when Playwright tests fail in CI","I need to pass detailed test failure context (error messages, stack traces, test code) to an LLM for analysis","I want to trigger automated test debugging workflows when specific test failures occur"],"best_for":["Teams running Playwright tests through Currents CI platform","AI agent developers building autonomous test repair systems","QA automation engineers integrating LLM-powered debugging into test pipelines"],"limitations":["Requires Currents account and active test runs — cannot ingest failures from local Playwright runs or other CI platforms","MCP protocol overhead adds ~100-200ms latency per failure event delivery","Failure context is limited to what Currents captures — custom test metadata not automatically included"],"requires":["Currents account with API credentials","Playwright test suite configured to report to Currents","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network connectivity to Currents API endpoints"],"input_types":["Currents API webhook/event stream","Test execution metadata (JSON)"],"output_types":["Structured test failure objects with error details","Test execution context (duration, environment, browser)"],"categories":["tool-use-integration","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-currents__cap_1","uri":"capability://memory.knowledge.test.failure.root.cause.analysis.and.code.context.retrieval","name":"test failure root cause analysis and code context retrieval","description":"Provides AI agents with access to the failing test code, related source code, and error stack traces through MCP tools that query Currents' test metadata store. Agents can retrieve the full test implementation, assertion failures, and execution logs to understand failure context before attempting repairs, using structured queries rather than free-text search.","intents":["I need to see the exact test code and assertion that failed to understand what to fix","I want to retrieve the full error stack trace and execution logs for a failed test","I need to find related source code files that might be causing the test failure"],"best_for":["Autonomous test repair agents that need full failure context before code generation","Developers using Claude or other LLMs to debug test failures interactively","Test failure triage systems that need to categorize failures by root cause"],"limitations":["Only retrieves test metadata stored in Currents — does not have direct access to git history or source control","Stack trace parsing depends on Playwright's error formatting — custom test frameworks may have incomplete context","Large test files (>50KB) may exceed MCP message size limits, requiring pagination"],"requires":["Currents API access with test execution history","Test run ID or failure ID from Currents","MCP client with tool-calling capability"],"input_types":["Test run ID (string)","Failure ID (string)","Query parameters (test name, error type)"],"output_types":["Test source code (string)","Error messages and stack traces (string)","Execution logs (string)","Structured failure metadata (JSON)"],"categories":["memory-knowledge","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-currents__cap_2","uri":"capability://code.generation.editing.automated.playwright.test.repair.code.generation","name":"automated playwright test repair code generation","description":"Enables AI agents to generate fixes for failing Playwright tests by analyzing failure context and producing corrected test code. The MCP server provides tools for agents to submit proposed fixes back to Currents, which can be validated against the test suite. Agents use chain-of-thought reasoning to understand failure root causes (selector changes, timing issues, API changes) and generate targeted repairs.","intents":["I want an AI agent to automatically fix Playwright tests that fail due to selector changes","I need to generate corrected test code for timing-related flakiness and submit it for validation","I want the agent to propose multiple fix strategies and let me choose the best one"],"best_for":["Teams with high test failure rates looking to automate test maintenance","Developers using AI agents to reduce manual test debugging overhead","CI/CD pipelines that need autonomous test repair before human review"],"limitations":["Generated fixes require human review before merging — no automatic commit capability","Cannot fix failures requiring changes to application code, only test code","Agents may generate overly broad fixes (e.g., adding excessive waits) rather than addressing root causes","No built-in validation that generated fixes actually pass — requires re-running test suite"],"requires":["Currents account with write permissions to test runs","LLM with code generation capability (Claude, GPT-4, etc.)","MCP client with tool-calling and code generation support","Git repository access for submitting fixes (optional, for automation)"],"input_types":["Test failure context (code, error, stack trace)","Test execution environment metadata"],"output_types":["Corrected test code (string)","Explanation of fix strategy (string)","Proposed changes in diff format (string)"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-currents__cap_3","uri":"capability://planning.reasoning.test.failure.categorization.and.pattern.matching","name":"test failure categorization and pattern matching","description":"Provides AI agents with tools to categorize test failures by root cause type (selector changes, timing issues, API contract changes, environment issues) using pattern matching against failure messages and stack traces. Agents can identify common failure patterns across multiple test runs and suggest systematic fixes rather than one-off repairs.","intents":["I want to identify all tests failing due to the same root cause (e.g., CSS selector changes)","I need to detect if a test failure is a known flaky pattern vs a real regression","I want to group similar failures together to prioritize high-impact fixes"],"best_for":["Test failure triage systems that need to categorize hundreds of failures","Teams with large test suites looking to identify systematic issues","Agents that need to prioritize which failures to fix first"],"limitations":["Pattern matching relies on error message consistency — custom error messages may not match patterns","Cannot distinguish between similar-looking failures with different root causes without additional context","Requires training data or heuristics to identify patterns — no machine learning model included"],"requires":["Multiple test failure records from Currents (for pattern detection)","MCP client with tool-calling capability","LLM with reasoning capability for pattern analysis"],"input_types":["Test failure metadata (error messages, stack traces)","Test execution history (multiple runs)"],"output_types":["Failure category classification (string enum)","Confidence score for classification (number)","List of similar failures (array of failure IDs)"],"categories":["planning-reasoning","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-currents__cap_4","uri":"capability://tool.use.integration.mcp.tool.registry.and.schema.definition.for.test.operations","name":"mcp tool registry and schema definition for test operations","description":"Defines a standardized MCP tool schema that exposes Currents test operations (fetch failures, submit fixes, query test history) as callable tools for AI agents. The schema includes input validation, error handling, and response formatting that abstracts Currents' API complexity. Tools are discoverable and self-documenting through MCP's tool definition protocol.","intents":["I want my AI agent to discover what test operations are available without reading documentation","I need type-safe tool calling with input validation for Currents operations","I want standardized error responses when test operations fail"],"best_for":["AI agent frameworks (LangChain, AutoGPT, etc.) integrating Currents","Teams building custom test automation workflows on top of Currents","Developers building multi-tool agents that need consistent interfaces"],"limitations":["Schema is static — does not auto-update if Currents API changes","Tool definitions are limited to what MCP protocol supports — complex nested operations may require multiple tool calls","No built-in rate limiting or quota management — agents can spam Currents API"],"requires":["MCP client implementation","Understanding of MCP tool definition schema","Currents API credentials"],"input_types":["MCP tool definition requests"],"output_types":["MCP tool definitions (JSON schema)","Tool execution results (JSON)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-currents__cap_5","uri":"capability://memory.knowledge.test.execution.environment.context.and.metadata.retrieval","name":"test execution environment context and metadata retrieval","description":"Provides agents with access to test execution environment metadata (browser version, OS, Node.js version, test configuration) from Currents, enabling context-aware failure analysis and fix generation. Agents can understand if a failure is environment-specific (e.g., only fails on Chrome 120) and generate environment-appropriate fixes.","intents":["I need to know what browser and OS a test failed on to understand if it's environment-specific","I want to generate fixes that account for the specific Node.js or Playwright version in use","I need to identify if a test failure is reproducible across all environments or only specific ones"],"best_for":["Teams running tests across multiple browser/OS combinations","Agents that need to generate environment-specific test fixes","Test failure analysis systems that need to correlate failures with environment changes"],"limitations":["Environment metadata is only available if Currents captures it — custom test runners may not report full environment details","Cannot access local machine environment — only what Currents has recorded","Environment context is historical — does not reflect current CI environment state"],"requires":["Currents test runs with environment metadata captured","MCP client with tool-calling capability"],"input_types":["Test run ID (string)"],"output_types":["Environment metadata (JSON with browser, OS, Node.js version, etc.)","Test configuration (JSON)"],"categories":["memory-knowledge","testing-quality"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Currents account with API credentials","Playwright test suite configured to report to Currents","MCP client implementation (Claude Desktop, custom agent framework, etc.)","Network connectivity to Currents API endpoints","Currents API access with test execution history","Test run ID or failure ID from Currents","MCP client with tool-calling capability","Currents account with write permissions to test runs","LLM with code generation capability (Claude, GPT-4, etc.)","MCP client with tool-calling and code generation support"],"failure_modes":["Requires Currents account and active test runs — cannot ingest failures from local Playwright runs or other CI platforms","MCP protocol overhead adds ~100-200ms latency per failure event delivery","Failure context is limited to what Currents captures — custom test metadata not automatically included","Only retrieves test metadata stored in Currents — does not have direct access to git history or source control","Stack trace parsing depends on Playwright's error formatting — custom test frameworks may have incomplete context","Large test files (>50KB) may exceed MCP message size limits, requiring pagination","Generated fixes require human review before merging — no automatic commit capability","Cannot fix failures requiring changes to application code, only test code","Agents may generate overly broad fixes (e.g., adding excessive waits) rather than addressing root causes","No built-in validation that generated fixes actually pass — requires re-running test suite","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.49999999999999994,"match_graph":0.25,"freshness":0.52,"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:03.037Z","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=currents","compare_url":"https://unfragile.ai/compare?artifact=currents"}},"signature":"Dpcx+qYPIMt9F0c1SLaTI5gPdWj0LbZqqmg+c2D7MwjjEe6wJZX8+NDHa04bvtI6aVXiP2HnAxEVs8V9Z8axDg==","signedAt":"2026-06-23T11:43:48.699Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/currents","artifact":"https://unfragile.ai/currents","verify":"https://unfragile.ai/api/v1/verify?slug=currents","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"}}