rickandmorty-mcp
Related Servers
Alternatives to rickandmorty-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceA deliberately small MCP server that demonstrates security hardening against the OWASP MCP Top 10 with tools for file search, record queries, and document fetching, each defended against path traversal, SQL injection, and SSRF.4MIT
- AlicenseNot gradedqualityCmaintenanceA safe, allowlisted MCP server that lets AI agents run only a tiny set of harmless tools (echo, datetime, hash, dig, GET-only curl, whois, status checks) against explicitly allowed hosts, with sanitization, rate limiting, timeouts, and full audit logging.MIT
- AlicenseAqualityDmaintenanceA compact MCP server demonstrating explicit tool boundaries, least-privilege discovery, execution-time authorization, destructive-action confirmation, and metadata-only audit logs using a local note store.3MIT

masaro-infra-mcpofficial
FlicenseNot gradedqualityCmaintenanceA secure MCP server providing read-only tools to interact with Cloudflare, Coolify, and other infrastructure services, enabling AI clients to safely diagnose and validate environments.-- AlicenseAqualityCmaintenanceRead-only MCP server providing AI access to verifiable web, GitHub, and local sources, plus a managed fantasy entity catalog, with strong security and provenance tracking.101MIT
- AlicenseAqualityCmaintenanceA read-only MCP server that enables AI assistants to query ServiceNow instances—incidents, changes, users, CMDB—with malformed query linting and injection protection.7MIT
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: list_* tools search with filters, get_* tools fetch by ID, and get_characters is explicitly for bulk retrieval. The singular/plural distinction between get_character and get_characters is clarified in descriptions.
All tools follow a consistent verb_noun pattern (list_<resource>, get_<resource>) using snake_case. The naming is predictable and immediately conveys the action and target resource.
Seven tools is well-scoped for a read-only API client covering three resource types with list and get operations plus a bulk getter. Every tool serves a distinct need without redundancy.
For a read-only Rick and Morty data access server, the surface is complete: all three core resources (characters, locations, episodes) have both search and direct lookup. The bulk character fetch complements the list results and episode character ID lists.