F
licenseA
qualityD
maintenanceCentral registry for AI tools with vector search and knowledge graph, enabling intelligent tool discovery, chaining, and execution via MCP.
12
-
ToolForge MCP
Related Servers
Alternatives to ToolForge MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables agents to securely discover and invoke a centrally governed catalog of tools from distributed internal and external providers, with policy enforcement, quotas, inspection, and audit controls.-
- AlicenseAqualityBmaintenanceEnables AI agents to manage, search, plan, and execute reusable skills while automatically enforcing always-on coding and reasoning guidelines. It provides workflow orchestration, permission-controlled execution, dynamic skill registration, and feedback-based ranking.913 npm1MIT
- AlicenseAqualityBmaintenanceA Python framework that exposes developer tools through MCP, REST API, and CLI from a single shared registry, enabling AI assistants, HTTP clients, and terminal users to access the same tools.12GPL 3.0
ibm-watsonx-gov-catalog-mcpofficial
AlicenseNot gradedqualityDmaintenanceBridges AI agents with tools on IBM watsonx governed agentic catalog, enabling secure governance and tool invocation via the Model Context Protocol.1Apache 2.0- FlicenseNot gradedqualityBmaintenanceCentralized registry for MCP tools, resources, and prompt templates with JSON schema validation and role-based access control filtering.-
TDQS
A3.9/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clear, distinct purpose covering the full tool lifecycle: registering, viewing, listing, searching, running, approving, deprecating, updating, and rolling back. No two tools have overlapping responsibilities.
Naming Consistency4/5
All tools follow a verb_noun pattern (e.g., approve_tool, get_tool), though there is a minor inconsistency between singular 'tool' and plural 'tools' in names like list_tools and search_tools vs others.
Tool Count5/5
9 tools is well-scoped for a tool registry server, covering all necessary operations without unnecessary bloat. Each tool serves a distinct and necessary function.
Completeness4/5
The tool surface covers the core lifecycle: registration, update, approval, execution, deprecation, and rollback. Minor gaps exist, such as the absence of a reject or unapprove operation, but overall it is fairly complete.
Maintenance
ActivityStale
ResponsivenessNo issues