OpenRPC

Created By
a year ago
Interact with and discover JSON-RPC APIs via OpenRPC.
Overview

What is OpenRPC?

OpenRPC is a Model Context Protocol (MCP) server that enables users to interact with and discover JSON-RPC APIs using the OpenRPC specification.

How to use OpenRPC?

To use OpenRPC, install the required dependencies, build the server, and configure it for use with clients such as Claude Desktop.

Key features of OpenRPC?

  • rpc_call: Call arbitrary JSON-RPC methods specifying server URL, method name, and parameters, with results returned in JSON format.
  • rpc_discover: Discover available JSON-RPC methods utilizing OpenRPC's rpc.discover specification to list all methods on a server.

Use cases of OpenRPC?

  1. Interfacing with JSON-RPC APIs for application development.
  2. Automating API interactions for testing and debugging.
  3. Discovering API capabilities for easier integration.

FAQ from OpenRPC?

  • What is JSON-RPC?

JSON-RPC is a remote procedure call (RPC) protocol encoded in JSON that allows for communication between a client and a server.

  • Is OpenRPC compatible with other RPC protocols?

OpenRPC is specifically tailored for JSON-RPC APIs, ensuring a smooth experience for applications that use this protocol.

  • How can I debug the server?

You can use the MCP Inspector for debugging, which provides a URL for accessing debugging tools in your browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago