trustcase-mcp
Related Servers
Alternatives to trustcase-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving details of 41,000+ agent skills, MCP servers, Claude Code plugins, and agentic loops from any MCP-capable agent.MIT
- FlicenseNot gradedqualityBmaintenanceProvides protocol-neutral market intelligence for the AI agent economy, with read-only tools to search agents, retrieve details and histories, compare agents, list categories, view category rankings, and access methodology.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables users to search and discover over 500 AI agent endpoints and x402 APIs directly from MCP-compatible clients like Claude and Cursor. It provides tools to query endpoints by keyword, category, or capability while offering access to detailed provider statistics.-
- FlicenseNot gradedqualityDmaintenanceEnables searching for AI agents by keywords or categories, allowing users to discover tools like coding agents, GUI agents, or industry-specific assistants across marketplaces.52-
- AlicenseAqualityAmaintenanceSearch and discover AI agents, skills, prompts, bundles and MCP connectors from the Spark catalog. Seven tools: search assets, get asset details and raw content, list popular assets and categories, check API key usage, and report the outcome of applying fetched content. No API key needed.510 npm4MIT

TAAFT MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables searching and retrieving public catalog details across 28 tools covering AI tools, MCP servers, models, tasks, companies, events, papers, and repositories. Clients can look up entries by query or fetch full details by slug or id through a stateless, no-auth Streamable HTTP endpoint.-
TDQS
Scored across 2 tools
The two tools form a clear search-then-detail workflow: search_use_cases returns candidate slugs, and get_use_case retrieves the full entry for one slug. Their descriptions explicitly state this sequence, so an agent should not confuse them.
Both names follow the same snake_case verb_noun pattern: search_use_cases and get_use_case. The resource noun is consistent, making the pair predictable.
Two tools is minimal but appropriate for a read-only directory lookup service with a search/detail split. It is slightly thin compared to richer API surfaces, but no tool appears redundant.
The surface covers the core workflow: find a use case by task description and retrieve its full trust assessment, approval boundaries, setup prompt, and link. Minor gaps exist, such as browsing by category or fetching an entry by slug without first searching, but these are workable.