F
licenseNot graded
qualityD
maintenanceEnables querying and managing the JSONPlaceholder API (posts, users, comments) through natural language via the Model Context Protocol.
-
JSONPlaceholder MCP Server
by danielpdev
Related Servers
Alternatives to JSONPlaceholder MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides AI assistants with access to the Fake Store API for e-commerce prototyping and testing, enabling queries on products, carts, and users.97 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query keyless mock REST data — products, users, posts, comments, recipes, quotes, and todos — with search, paging, and field selection for prototyping, demos, and test scaffolds. Offers a gateway-hosted or local stdio MCP endpoint plus plain-HTTP tool calls, requiring no API key or account for initial use.390 npmMIT
- AlicenseAqualityDmaintenanceProvides seamless access to the Fake Store API for AI assistants with 18 CRUD tools for managing e-commerce data including products, carts, and users. Perfect for e-commerce demos, testing, and learning MCP development with zero configuration required.1810 npmMIT
- AlicenseNot gradedqualityDmaintenanceHosted MCP endpoint that returns realistic fake data for prototyping agents. Paste one URL into Claude Code, Cursor, or Claude Desktop — 12 pre-built tools covering users, products, orders, events, email, and knowledge base search. No signup, no config, no auth. Built for developers who want to prototype agent workflows before wiring up a real backend.MIT
- AlicenseBqualityDmaintenanceManages user data with resources, tools, and prompts for CRUD operations on a JSON file.21MIT
TDQS
B3.2/5.0
Scored across 8 tools
Disambiguation4/5
Most tools are clearly distinct by resource type (posts, albums, comments, photos, todos, users), but 'get_posts' and 'search_posts' have overlapping purposes since both retrieve posts with different filtering approaches. The descriptions help clarify the distinction, but an agent might occasionally misselect between them.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with 'create_' or 'get_' or 'search_' prefixes, all in snake_case. This predictability makes it easy for agents to understand and use the tool set without confusion.
Tool Count5/5
With 8 tools, this server is well-scoped for interacting with JSONPlaceholder's mock REST API resources. Each tool corresponds to a key resource (posts, albums, comments, photos, todos, users), and the count is neither too sparse nor bloated for the domain.
Completeness3/5
The server covers retrieval (get) operations for all major resources and creation for posts, but lacks update and delete operations, which are typical in CRUD workflows. This creates notable gaps that agents must work around, as they cannot modify or remove data beyond creating posts.
Maintenance
ActivityInactive
ResponsivenessNo issues