example-mcp
Related Servers
Alternatives to example-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceTurns any OpenAPI spec into two sandboxed tools, search and execute, so an AI agent can discover endpoints and run small JavaScript programs against an entire API using under 1,000 tokens of context. Requests are read-only by default and the API key never enters the sandbox.MIT
- AlicenseNot gradedqualityCmaintenanceExposes four stdio tools that let an agent research an application's documented interface, produce a validated single-use plan, and execute read-only operations against public HTTP JSON APIs, static HTML/JSON/text sources, and host-configured CLIs. Runs in-process with no listening port, accounts, or model dependency, returning bounded results while keeping inputs and outputs inside a host-enforced research-plan-execute lifecycle.MIT
- FlicenseNot gradedqualityDmaintenanceExposes tools to create and list tasks by wrapping a REST API, enabling LLMs to manage a TODO list via natural language.-
- AlicenseNot gradedqualityBmaintenanceExposes an OpenAI-compatible /v1/responses endpoint so a model can answer prompts by discovering and running a shared folder of sandboxed tools — shell commands, file editing, pull requests, persistent notes, time, sysinfo and Doxygen checks. Path-taking tools are bounded by a configurable file-system gate, and new tools added to the tools folder become available without code changes.MIT
- FlicenseAqualityCmaintenanceEnables a locally-run LLM to search the web, fetch pages as markdown, make arbitrary HTTP requests, and optionally render pages with headless Chromium.3-
- AlicenseNot gradedqualityDmaintenanceEnables LLM clients to fetch web pages as clean text, tail local logs, search the live web via DuckDuckGo, and run read-only SQL queries against SQLite or Postgres/Supabase.MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct resource and action: list users, get a single user, list todos, search posts, and search documentation. search_docs is explicitly contrasted with the live-data tools, and there is no overlap between user, todo, and post operations.
All tool names use a consistent snake_case verb_noun pattern: list_users, get_user, list_todos, search_posts, search_docs. The verbs are appropriately varied but predictable, and there is no mixing of naming conventions.
Five tools are well-scoped for a small example API covering users, todos, posts, and documentation. Each tool earns its place with a distinct resource area, and there are no redundant or filler tools.
The read-only surface covers listing users, getting a user, listing todos, searching posts, and searching docs, but there is no get_post tool to retrieve a full post body—search_posts only returns title, post id, and user id. If write operations are part of the domain, they are also entirely absent, leaving notable gaps for post content retrieval.