Skip to main content
Glama
xiaobenyang-com

JSON-RPC

README.md
# JSON-RPC服务 JSON-RPC

一个基于OpenRPC的Model Context Protocol (MCP)服务器,提供JSON-RPC功能调用和方法发现服务。
A Model Context Protocol (MCP) server based on OpenRPC, providing JSON-RPC function invocation and method discovery services.## 工具列表 Tool List

本MCP服务封装下列工具,可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具,可让模型通过标准化接口调用以下功能。

| 工具 Tool   | 描述 Description         |
|-------|--------------------|
| rpc_call | Call any JSON-RPC method on a server with parameters. A user would prompt: Call method <method> on <server url> with params <params> |
| rpc_discover | This uses JSON-RPC to call `rpc.discover` which is part of the OpenRPC Specification for discovery for JSON-RPC servers. A user would prompt: What JSON-RPC methods does this server have? <server url> |


## 检查服务 ## Inspector

工具在线测试: [https://mcp.xiaobenyang.com/inspector/1777316659903491](https://mcp.xiaobenyang.com/inspector/1777316659903491)

Online Tool test [https://mcp.xiaobenyang.com/inspector/1777316659903491](https://mcp.xiaobenyang.com/inspector/1777316659903491)

## 服务配置 MCP Server Config


> #### 如何获取 XBY-APIKEY ? How to get XBY-APIKEY ?
> 访问小笨羊科技网站 [https://xiaobenyang.com](https://xiaobenyang.com),注册用户即可获得APIKEY
> Visit XiaoBenYang website [https://xiaobenyang.com](https://xiaobenyang.com), register and get the APIKEY.

### SSE
```json
{
  "mcpServers": {
    "JSON-RPC服务": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "sse",
      "url": "https://mcp.xiaobenyang.com/1777316659903491/sse"
    }
  }
}
```
### STREAMABLE HTTP
```json
{
  "mcpServers": {
    "JSON-RPC服务": {
      "headers": {
        "XBY-APIKEY": "<YOUR_XBY_APIKEY>"
      },
      "type": "streamable_http",
      "url": "https://mcp.xiaobenyang.com/1777316659903491/mcp"
    }
  }
}
```
### STDIO
```json
{
    "mcpServers": {
        "JSON-RPC服务": {
          "command": "npx",
          "args": [
            "-y",
            "xiaobenyang-mcp"
          ],
          "env": {
            "XBY_APIKEY": "<YOUR_XBY_APIKEY>",
            "mcpId": "1777316659903491",
          },
          "transport": "stdio"
        }
      }
}

```

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