{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-mcp-code-todo","slug":"npm-mcp-code-todo","name":"mcp-code-todo","type":"mcp","url":"https://www.npmjs.com/package/mcp-code-todo","page_url":"https://unfragile.ai/npm-mcp-code-todo","categories":["mcp-servers"],"tags":["mcp","code","todo"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-mcp-code-todo__cap_0","uri":"capability://code.generation.editing.recursive.codebase.todo.scanning.with.pattern.matching","name":"recursive codebase todo scanning with pattern matching","description":"Scans entire codebases recursively to identify TODO, FIXME, HACK, and NOTE comments using regex-based pattern matching across multiple file types. Implements file traversal with language-aware filtering to avoid scanning binary files and dependencies, returning structured results with file paths, line numbers, and comment content for integration into MCP-compatible clients.","intents":["I need to find all outstanding TODOs scattered across my codebase to prioritize technical debt","I want to audit code quality by identifying FIXME and HACK comments that indicate incomplete work","I need to export a list of all code annotations for team review and sprint planning","I want to track code comments that reference specific issues or PRs for traceability"],"best_for":["development teams managing technical debt across large codebases","solo developers building LLM agents that need code context and annotation awareness","CI/CD pipelines requiring automated code quality gates based on outstanding TODOs","code review tools and IDEs integrating MCP servers for enhanced code analysis"],"limitations":["Regex-based pattern matching may produce false positives in strings, comments within comments, or non-English TODO variants","No semantic understanding of TODO priority, urgency, or assignment — treats all matches equally","Performance degrades on very large codebases (100k+ files) without configurable depth limits or exclusion patterns","Does not parse TODO metadata like assignees, dates, or issue references — requires post-processing for structured extraction"],"requires":["Node.js 16+ for MCP server runtime","MCP client implementation (Claude Desktop, custom MCP host, or compatible IDE)","Read access to target codebase directory","npm or yarn for package installation"],"input_types":["file system path (directory or single file)","optional configuration for file patterns to include/exclude"],"output_types":["structured JSON with file path, line number, comment type, and text content","MCP resource format for client consumption"],"categories":["code-generation-editing","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-code-todo__cap_1","uri":"capability://tool.use.integration.mcp.resource.exposure.for.todo.data","name":"mcp resource exposure for todo data","description":"Exposes TODO scan results as MCP resources (standardized data objects) that MCP-compatible clients can query, cache, and subscribe to. Implements the MCP resource protocol to allow clients like Claude Desktop to treat TODO lists as first-class data sources, enabling multi-turn conversations about code annotations without re-scanning.","intents":["I want Claude to understand my codebase's outstanding TODOs in a conversation without me manually listing them","I need to query TODO data programmatically from an MCP client without writing custom parsing logic","I want to cache TODO results to avoid repeated filesystem scans during multi-turn conversations"],"best_for":["Claude Desktop users integrating code analysis into AI-assisted development workflows","teams building custom MCP hosts that need standardized code annotation data","developers creating AI agents that reason about technical debt and code quality"],"limitations":["Resource caching is client-dependent — no server-side caching mechanism for repeated queries","MCP protocol overhead adds latency compared to direct filesystem access for single queries","No real-time updates — clients must explicitly re-request resources to detect new TODOs"],"requires":["MCP client implementation with resource protocol support","Claude Desktop 0.1.0+ or compatible MCP host"],"input_types":["MCP resource request with optional path parameter"],"output_types":["MCP resource object containing TODO metadata and content"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-code-todo__cap_2","uri":"capability://code.generation.editing.multi.language.todo.pattern.detection","name":"multi-language todo pattern detection","description":"Detects TODO, FIXME, HACK, and NOTE comments across multiple programming languages using language-agnostic regex patterns that work in single-line comments (// # --) and block comments (/* */ <!-- -->). Filters by file extension to avoid scanning incompatible file types while maintaining broad language coverage without language-specific parsers.","intents":["I need to find TODOs across a polyglot codebase with JavaScript, Python, Go, and Rust files","I want to identify all code annotations regardless of comment syntax used in different languages","I need to exclude non-code files (images, binaries, node_modules) from TODO scanning"],"best_for":["polyglot teams with codebases spanning multiple programming languages","monorepo maintainers needing unified code annotation tracking across language boundaries","developers auditing legacy codebases with mixed language support"],"limitations":["Regex patterns may not handle language-specific comment edge cases (e.g., TODO in Python docstrings, Rust raw strings)","No semantic understanding of language-specific syntax — may match TODO-like patterns in string literals or comments within comments","File extension filtering is crude — may miss TODOs in files with non-standard extensions or no extension","Does not prioritize or weight TODOs by language or file type"],"requires":["Node.js 16+ with filesystem access","Target codebase with readable file permissions"],"input_types":["directory path or file path","optional file extension filter list"],"output_types":["structured results with language context (inferred from file extension)"],"categories":["code-generation-editing","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-mcp-code-todo__cap_3","uri":"capability://automation.workflow.configurable.file.and.directory.exclusion","name":"configurable file and directory exclusion","description":"Allows users to exclude specific files, directories, and patterns from TODO scanning via configuration (e.g., node_modules, .git, build directories, vendor folders). Implements glob-pattern matching or explicit path lists to prevent scanning of irrelevant files, reducing scan time and noise in results.","intents":["I want to exclude node_modules and vendor directories from TODO scans to focus on application code","I need to skip generated code and build artifacts that contain irrelevant TODOs","I want to configure exclusions per project without modifying the tool itself"],"best_for":["teams with large dependency trees or generated code that pollutes TODO results","developers managing multiple projects with different exclusion requirements","CI/CD pipelines needing consistent TODO scanning across environments"],"limitations":["Configuration mechanism unknown — may require hardcoded patterns or external config file support","No built-in understanding of common exclusion patterns (e.g., .gitignore) — requires explicit configuration","Glob pattern matching performance may degrade with complex patterns on large directory trees"],"requires":["Configuration file or CLI parameter support (implementation details unclear)"],"input_types":["configuration object or file with exclusion patterns"],"output_types":["filtered TODO results excluding matched paths"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["Node.js 16+ for MCP server runtime","MCP client implementation (Claude Desktop, custom MCP host, or compatible IDE)","Read access to target codebase directory","npm or yarn for package installation","MCP client implementation with resource protocol support","Claude Desktop 0.1.0+ or compatible MCP host","Node.js 16+ with filesystem access","Target codebase with readable file permissions","Configuration file or CLI parameter support (implementation details unclear)"],"failure_modes":["Regex-based pattern matching may produce false positives in strings, comments within comments, or non-English TODO variants","No semantic understanding of TODO priority, urgency, or assignment — treats all matches equally","Performance degrades on very large codebases (100k+ files) without configurable depth limits or exclusion patterns","Does not parse TODO metadata like assignees, dates, or issue references — requires post-processing for structured extraction","Resource caching is client-dependent — no server-side caching mechanism for repeated queries","MCP protocol overhead adds latency compared to direct filesystem access for single queries","No real-time updates — clients must explicitly re-request resources to detect new TODOs","Regex patterns may not handle language-specific comment edge cases (e.g., TODO in Python docstrings, Rust raw strings)","No semantic understanding of language-specific syntax — may match TODO-like patterns in string literals or comments within comments","File extension filtering is crude — may miss TODOs in files with non-standard extensions or no extension","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.18,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.9,"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-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:51.285Z","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=npm-mcp-code-todo","compare_url":"https://unfragile.ai/compare?artifact=npm-mcp-code-todo"}},"signature":"yDZPOQnx8yAYsLgu96chDABvIIiiYBGuloyAh1M4NHD5JTTsw4JHSfmq7lbkh0obXLDq4m9FtUP5S0dgcHlABQ==","signedAt":"2026-06-16T02:04:08.208Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-mcp-code-todo","artifact":"https://unfragile.ai/npm-mcp-code-todo","verify":"https://unfragile.ai/api/v1/verify?slug=npm-mcp-code-todo","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"}}