invokit-mcp
OfficialRelated Servers
Alternatives to invokit-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityFmaintenanceMCP server that exposes 300+ AI agents as tools via a single API key. Supports listing agents, invoking any agent with chat-completion style messages, checking agent health, and retrieving platform statistics.54-
- FlicenseNot gradedqualityCmaintenanceOfficial MCP Server for GPT-5.6 Sol Coding & Reasoning API. Connects extended reasoning capabilities directly into Claude Desktop, Cursor, and Windsurf.-
- AlicenseAqualityDmaintenanceAn MCP server that gives AI coding agents real-time access to the public-apis dataset, enabling search, live probing, and code snippet generation for 1,500+ free public APIs.736 npm5MIT
- AlicenseBqualityCmaintenanceMCP (Model Context Protocol) Server for skill4agent - Search, view, and install AI skills in AI conversations.310 npm4MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server exposing 58 online tools (crypto, data, image, text, etc.) and workflow execution, enabling MCP clients like Claude Desktop to invoke them via natural language.584 npmMIT
- AlicenseNot gradedqualityFmaintenanceTool search engine for AI agents. One API call to discover the best MCP server for any task. 900+ services indexed with 4-dimensional value ranking.MIT
TDQS
Scored across 14 tools
Every tool targets a distinct action and resource: quality scores, raw metrics, alternatives, tool details, skills, apps, categories, invocation, and feedback are all clearly separated. The two most similar tools, get_tool_quality and get_tool_metrics, explicitly cross-reference each other to eliminate ambiguity.
Tool names consistently follow a verb_noun snake_case pattern across get, search, list, check, submit, and invoke. Entity types like tool, skill, app, and category appear in predictable positions, making the naming scheme easy to learn and anticipate.
14 tools is well within the ideal range for a marketplace platform server. Each tool covers a necessary step in the workflow: discover, inspect, check usage, invoke, give feedback, and retrieve platform metadata. No tool feels redundant or extraneous.
The tool surface covers the full marketplace lifecycle: searching and retrieving tools/skills/apps/categories, inspecting quality and raw metrics, finding alternatives, checking quota, invoking tools, and submitting outcome feedback. The only possible gap would be direct invocation of skills or apps, but those are not advertised as invocable resources.