A
licenseB
qualityF
maintenanceA Model Context Protocol (MCP) server that provides JSON-RPC functionality through OpenRPC.
2
38 npm
43
Apache 2.0
JSON-RPC
Related Servers
Alternatives to JSON-RPC
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server generated from an OpenAPI Specification, exposing tools via HTTP. It allows clients to invoke API operations using JSON-RPC 2.0 requests.7 npmArtistic 2.0
- AlicenseBqualityAmaintenanceA lightweight server implementation that exposes Python functions as discoverable tools via HTTP using the Machine-to-Machine Communication Protocol (MCP). Enables remote execution of Python functions through a JSON-RPC interface with async support and type safety.430 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseNot gradedqualityBmaintenanceA generic, modular server for implementing the Model Context Protocol (MCP).43 npm45ISC
TDQS
B3.2/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: rpc_call executes specific JSON-RPC methods with parameters, while rpc_discover queries a server for available methods. There is no overlap in functionality, and an agent can easily differentiate between calling a method and discovering what methods exist.
Naming Consistency5/5
Both tools follow a consistent snake_case naming pattern with the 'rpc_' prefix, clearly indicating their domain. The verbs 'call' and 'discover' are distinct and appropriate for their respective actions, maintaining a predictable structure throughout the set.
Tool Count3/5
With only two tools, the server feels thin for a JSON-RPC domain, as it lacks operations like listing servers, handling authentication, or managing connections. While the tools cover basic calling and discovery, the count is borderline minimal for a server that could support more comprehensive RPC interactions.
Completeness2/5
The tool surface is significantly incomplete for a JSON-RPC server. It provides call and discovery but misses essential operations such as server management (e.g., add/remove servers), error handling, batch requests, or method documentation retrieval. This will likely cause agent failures when attempting more complex RPC workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues