test-public-lunir

Created By
MarkO-Lunira year ago
testing the lunir mcp servers
Overview

what is test-public-lunir?

test-public-lunir is a project aimed at testing the Lunir MCP servers to ensure their functionality and performance.

how to use test-public-lunir?

To use test-public-lunir, clone the repository from GitHub and follow the instructions provided in the documentation to set up and run tests on the Lunir MCP servers.

key features of test-public-lunir?

  • Comprehensive testing framework for Lunir MCP servers
  • Easy setup and configuration
  • Detailed logging and reporting of test results

use cases of test-public-lunir?

  1. Validating the performance of Lunir MCP servers under various loads.
  2. Ensuring the reliability and stability of server operations.
  3. Identifying potential issues before deployment in production environments.

FAQ from test-public-lunir?

  • What is the purpose of this project?

The purpose of this project is to test the Lunir MCP servers for performance and reliability.

  • How can I contribute to this project?

You can contribute by submitting issues, feature requests, or pull requests on the GitHub repository.

  • Is there any documentation available?

Yes, documentation is available in the repository to guide users on how to set up and run tests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MarkO-Lunir
Star
0
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)

2 days ago