{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-renamify","slug":"renamify","name":"Renamify","type":"mcp","url":"https://docspring.github.io/renamify/mcp/overview/","page_url":"https://unfragile.ai/renamify","categories":["mcp-servers"],"tags":[],"pricing":{"model":"unknown","free":false,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-renamify__cap_0","uri":"capability://code.generation.editing.case.aware.symbol.renaming.with.automatic.convention.transformation","name":"case-aware symbol renaming with automatic convention transformation","description":"Intelligently renames code symbols (variables, functions, classes) across a codebase while automatically transforming the name across all detected naming conventions (camelCase, snake_case, PascalCase, SCREAMING_SNAKE_CASE). The system analyzes identifier usage patterns to determine which convention applies in each context, then applies the transformation consistently. For example, renaming 'user_name' to 'account_id' automatically generates 'userName' in camelCase contexts and 'USER_NAME' in constant contexts.","intents":["Rename a variable across multiple files while preserving naming convention in each context","Refactor a function name and have all camelCase/snake_case variants update automatically","Change a class name and ensure all related constants and properties follow the new convention"],"best_for":["polyglot development teams working across multiple naming convention styles","large codebases with inconsistent naming patterns that need systematic cleanup","AI assistants planning refactoring operations that need to respect language-specific conventions"],"limitations":["Language-specific support matrix unknown — unclear which programming languages have full convention detection","Requires prior analysis of codebase naming patterns; may fail on non-standard or mixed conventions","No support for partial renames or conditional transformations (e.g., rename only in specific modules)"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Local filesystem access to codebase"],"input_types":["string (old identifier name)","string (new identifier name)"],"output_types":["structured execution result with file paths and line numbers of changes"],"categories":["code-generation-editing","refactoring"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_1","uri":"capability://automation.workflow.atomic.file.and.directory.renaming.with.conflict.detection","name":"atomic file and directory renaming with conflict detection","description":"Renames files and directories in a codebase with built-in conflict detection and atomic transaction semantics — all changes succeed or none are applied. The system scans for references to the old file/directory name across the codebase (imports, requires, relative paths, configuration files) and updates them in a single atomic operation. If conflicts are detected (e.g., target name already exists, circular references), the entire operation is rejected before any changes are written.","intents":["Rename a source file and automatically update all import statements that reference it","Reorganize directory structure and have all relative paths and module references update consistently","Safely rename a file when a similarly-named file already exists, with conflict prevention"],"best_for":["teams managing large module hierarchies with complex interdependencies","developers refactoring project structure without manual import/reference updates","AI assistants that need to safely plan and preview file reorganization before execution"],"limitations":["Conflict detection behavior on edge cases (symlinks, circular references) is undocumented","No support for cross-repository file moves or renames","Reference detection may miss dynamic imports or string-based path construction"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Write permissions on local filesystem"],"input_types":["string (old file/directory path)","string (new file/directory path)"],"output_types":["structured execution result with list of updated references and file paths"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_2","uri":"capability://search.retrieval.codebase.wide.identifier.search.with.pattern.matching","name":"codebase-wide identifier search with pattern matching","description":"Searches for identifiers (variables, functions, classes, file names) across the entire codebase using pattern matching that understands code structure. The search tool can locate all occurrences of a symbol, filter by context (e.g., function definitions vs. usages), and return results with file paths, line numbers, and surrounding code context. This enables AI assistants to understand the scope and impact of a rename operation before planning it.","intents":["Find all usages of a variable or function to understand its scope before renaming","Locate all files matching a naming pattern to plan a bulk rename operation","Identify which modules import or reference a specific symbol"],"best_for":["AI assistants that need to analyze codebase impact before proposing refactoring","developers understanding symbol scope and dependencies before making changes","teams auditing codebase for naming inconsistencies or unused symbols"],"limitations":["Search pattern syntax and capabilities are undocumented","No support for semantic search (e.g., find functions with similar behavior)","Performance on very large codebases (>100k files) is unspecified","Cannot distinguish between symbol definitions and usages in results"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Read access to local filesystem"],"input_types":["string (identifier or pattern to search for)"],"output_types":["structured list with file paths, line numbers, and code context for each match"],"categories":["search-retrieval","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_3","uri":"capability://planning.reasoning.rename.operation.planning.with.preview.and.case.transformation.preview","name":"rename operation planning with preview and case transformation preview","description":"Creates a detailed execution plan for a rename operation before applying it, showing exactly which files will be modified, which lines will change, and how case transformations will be applied. The plan includes a preview of the changes in multiple formats (diff, side-by-side, summary) so AI assistants and developers can review the impact before execution. The plan object can then be passed to the apply tool to execute all changes atomically.","intents":["Preview how a rename will affect the codebase before committing to the change","Review case transformation logic to ensure it will apply correctly in all contexts","Generate a detailed change summary for code review or documentation purposes"],"best_for":["AI assistants that need to show users what changes will be made before applying them","developers reviewing complex refactoring plans involving multiple files","teams requiring change approval workflows before executing renames"],"limitations":["Preview format options are undocumented (diff, side-by-side, summary formats unknown)","Plan objects may not persist across sessions if no explicit serialization is provided","No support for conditional or partial previews (e.g., preview only in specific modules)"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Read access to local filesystem"],"input_types":["string (old identifier/file name)","string (new identifier/file name)"],"output_types":["structured plan object with file modifications, line numbers, and case transformations","formatted preview string (format type unspecified)"],"categories":["planning-reasoning","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_4","uri":"capability://automation.workflow.atomic.execution.of.planned.rename.operations","name":"atomic execution of planned rename operations","description":"Executes a previously-planned rename operation atomically, applying all file modifications, symbol renames, and reference updates in a single transaction. If any part of the operation fails (e.g., file write error, conflict detected), the entire operation is rolled back and no changes are persisted. The execution returns a detailed result object with the status of each modified file and any errors encountered.","intents":["Apply a reviewed rename plan to the codebase with guaranteed atomicity","Execute a rename operation and receive confirmation of all changes made","Safely apply AI-planned refactoring with rollback on failure"],"best_for":["AI assistants executing refactoring operations with safety guarantees","developers applying complex multi-file renames with atomic semantics","teams requiring guaranteed consistency in refactoring operations"],"limitations":["Atomicity guarantees are claimed but implementation details are undocumented","No partial rollback support — entire operation fails if any file modification fails","Error handling and recovery behavior on filesystem errors is unspecified"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Write permissions on local filesystem","Valid plan object from renamify_plan tool"],"input_types":["plan object (from renamify_plan)"],"output_types":["structured execution result with status per file, error details, and summary"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_5","uri":"capability://automation.workflow.unlimited.undo.redo.with.operation.history.tracking","name":"unlimited undo/redo with operation history tracking","description":"Maintains a complete history of all rename and replace operations performed on the codebase, allowing unlimited undo and redo of any previous operation. Each operation is tracked with metadata (timestamp, old name, new name, files affected) and can be individually undone or redone. The history is accessible via the renamify_history tool, and undo/redo operations are themselves atomic and reversible.","intents":["Undo a rename operation that had unintended consequences","Redo a previously undone rename to restore it","Review the history of all refactoring operations performed on the codebase","Revert to a previous state after a series of renames"],"best_for":["developers experimenting with refactoring and needing to revert changes","teams auditing refactoring history for compliance or review purposes","AI assistants that need to recover from incorrect rename operations"],"limitations":["History persistence mechanism is undocumented — unclear if history survives process restarts","Undo/redo depth is claimed as 'unlimited' but no technical verification or memory limits documented","No support for selective history clearing or archival","History may be lost if the MCP server process terminates unexpectedly"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Write permissions on local filesystem (for undo/redo operations)"],"input_types":["operation reference (for undo/redo)","none (for history query)"],"output_types":["structured history list with operation metadata","undo/redo result object with status"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_6","uri":"capability://automation.workflow.simple.regex.and.literal.string.replacement.without.case.transformation","name":"simple regex and literal string replacement without case transformation","description":"Performs straightforward find-and-replace operations using regex patterns or literal strings, without applying case-aware transformations. This tool is useful for bulk replacements that don't require convention-aware logic (e.g., replacing a hardcoded string, updating a configuration value, or applying a simple regex pattern). Unlike the case-aware rename tool, this operates on exact pattern matches without analyzing naming conventions.","intents":["Replace a hardcoded string value across multiple files","Apply a regex pattern to update configuration or data files","Perform a bulk text replacement that doesn't require case transformation"],"best_for":["developers performing simple find-and-replace operations","bulk updates to configuration files or data strings","regex-based transformations that don't involve code symbols"],"limitations":["No case-aware transformation — replacements are literal or regex-based only","No semantic understanding of code context — may replace strings in comments or strings unintentionally","Regex syntax and supported features are undocumented","No preview or planning step — operates directly on codebase"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Write permissions on local filesystem"],"input_types":["string (regex pattern or literal string to find)","string (replacement text)"],"output_types":["structured execution result with file paths and number of replacements per file"],"categories":["automation-workflow","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_7","uri":"capability://tool.use.integration.mcp.server.integration.for.ai.assistant.tool.access","name":"mcp server integration for ai assistant tool access","description":"Exposes all Renamify capabilities as MCP (Model Context Protocol) tools that AI assistants can call directly. The MCP server runs as a Node.js process and communicates with AI assistants via the standard MCP protocol, allowing assistants to search, plan, preview, and apply rename operations without requiring manual CLI invocation. The server handles tool invocation, parameter validation, and result serialization according to MCP specifications.","intents":["Enable AI assistants to perform codebase refactoring autonomously via tool calling","Allow AI assistants to search and analyze codebase structure before planning changes","Integrate Renamify capabilities into AI-powered code generation and refactoring workflows"],"best_for":["AI assistant developers building autonomous code refactoring agents","teams using Claude, ChatGPT, or other MCP-compatible AI assistants for code tasks","developers integrating Renamify into larger AI-powered development workflows"],"limitations":["MCP transport mechanism is unspecified (stdio, SSE, HTTP assumed but not documented)","Tool invocation timeout and rate limits are undocumented","No authentication or authorization mechanism documented — assumes local-only access","Error handling and exception propagation to AI assistants is unspecified"],"requires":["Node.js 18+ (version requirement inferred, not explicitly stated)","@renamify/mcp-server npm package installed","AI assistant with MCP support (Claude, etc.)","MCP configuration in AI assistant settings"],"input_types":["MCP tool call with parameters (format varies by tool)"],"output_types":["MCP tool result with structured JSON response"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_8","uri":"capability://automation.workflow.optional.git.integration.with.automatic.commit.on.rename","name":"optional git integration with automatic commit on rename","description":"Optionally integrates with Git to automatically create commits after rename operations are applied. When enabled, each rename operation can be automatically committed with a generated or custom commit message, creating an audit trail of refactoring changes. The Git integration is optional and can be configured at the MCP server level, but specific configuration options and behavior are undocumented.","intents":["Automatically commit refactoring changes to Git with descriptive messages","Create an audit trail of rename operations for code review and history","Integrate Renamify operations into Git-based development workflows"],"best_for":["teams using Git for version control and requiring audit trails of refactoring","developers wanting automatic commit creation for rename operations","AI assistants that need to create trackable refactoring commits"],"limitations":["Git integration configuration options are completely undocumented","Commit message generation logic is unspecified","No support for custom commit messages or commit hooks","Behavior when Git is not initialized or on detached HEAD is unknown","No support for creating pull requests or branches for refactoring changes"],"requires":["Git installed and initialized in the codebase directory","Git configuration in Renamify MCP server (configuration method unknown)","Write permissions on Git repository"],"input_types":["none (automatic on rename operation)"],"output_types":["Git commit hash and message (format unspecified)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-renamify__cap_9","uri":"capability://automation.workflow.current.state.and.pending.operations.status.reporting","name":"current state and pending operations status reporting","description":"Provides a status endpoint that reports the current state of the Renamify server, including any pending rename plans that have been created but not yet applied, the current operation history depth, and the state of any in-progress operations. This allows AI assistants and developers to understand what operations are pending and avoid conflicts or unexpected state changes.","intents":["Check if there are any pending rename plans waiting to be applied","Verify the current state before applying a new rename operation","Monitor the status of long-running rename operations"],"best_for":["AI assistants that need to verify server state before planning operations","developers managing multiple concurrent refactoring operations","teams requiring visibility into pending changes before applying them"],"limitations":["Status object structure and fields are completely undocumented","No real-time status updates or polling mechanism documented","No support for detailed operation progress reporting","Unclear if status includes information about failed or partially-completed operations"],"requires":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed"],"input_types":["none"],"output_types":["structured status object with pending operations and server state"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":34,"verified":false,"data_access_risk":"high","permissions":["Node.js runtime (version unspecified)","@renamify/mcp-server npm package installed","Local filesystem access to codebase","Write permissions on local filesystem","Read access to local filesystem","Valid plan object from renamify_plan tool","Write permissions on local filesystem (for undo/redo operations)","Node.js 18+ (version requirement inferred, not explicitly stated)","AI assistant with MCP support (Claude, etc.)","MCP configuration in AI assistant settings"],"failure_modes":["Language-specific support matrix unknown — unclear which programming languages have full convention detection","Requires prior analysis of codebase naming patterns; may fail on non-standard or mixed conventions","No support for partial renames or conditional transformations (e.g., rename only in specific modules)","Conflict detection behavior on edge cases (symlinks, circular references) is undocumented","No support for cross-repository file moves or renames","Reference detection may miss dynamic imports or string-based path construction","Search pattern syntax and capabilities are undocumented","No support for semantic search (e.g., find functions with similar behavior)","Performance on very large codebases (>100k files) is unspecified","Cannot distinguish between symbol definitions and usages in results","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.55,"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.048Z","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=renamify","compare_url":"https://unfragile.ai/compare?artifact=renamify"}},"signature":"WnO01EXifso9hVYNb40SMFmKwu1jK+bmjfoe1kUkkHEKhH+MgSbrjtmWwP7Oxc4A3drYq4dvj1VwPNB7zvuHDQ==","signedAt":"2026-06-22T18:33:19.010Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/renamify","artifact":"https://unfragile.ai/renamify","verify":"https://unfragile.ai/api/v1/verify?slug=renamify","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"}}