A
licenseB
qualityD
maintenanceA Model Context Protocol (MCP) server based on OpenRPC, providing JSON-RPC function invocation and method discovery services.
2
1
Apache 2.0
openrpc-mpc-server
by shanejonas
Related Servers
Alternatives to openrpc-mpc-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA generic, modular server for implementing the Model Context Protocol (MCP).64 npm45ISC
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) Server for the mcp API.1,026 npmMIT
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- 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.1 npmArtistic 2.0
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that standardizes tool discovery, execution, and context management for AI applications.MIT
TDQS
B3.3/5.0
Scored across 2 tools
Disambiguation5/5
The two tools have clearly distinct purposes: rpc_call is for executing arbitrary JSON-RPC methods, while rpc_discover is specifically for server discovery to list available methods. There is no overlap in functionality, making them easy to distinguish.
Naming Consistency5/5
Both tools follow a consistent 'rpc_' prefix pattern with descriptive suffixes (call, discover), using snake_case throughout. This provides a predictable and readable naming convention across the tool set.
Tool Count3/5
With only 2 tools, the server feels minimal but appropriate for its narrow scope of JSON-RPC interaction. However, it lacks tools for common operations like server health checks or parameter validation, which could enhance usability in this domain.
Completeness3/5
The tools cover the core actions of calling methods and discovering server capabilities, which aligns with the OpenRPC domain. However, there are notable gaps such as error handling tools, batch request support, or schema validation that would provide more comprehensive coverage for JSON-RPC workflows.
Maintenance
ActivityInactive
ResponsivenessUnresponsive