MCP-Server-MySSL

Created By
trustasia-coma year ago
MySSL MCP Server
Overview

what is MCP-Server-MySSL?

MCP-Server-MySSL is an implementation of an MCP server that provides domain and IP security checking capabilities through the MySSL API.

how to use MCP-Server-MySSL?

To use MCP-Server-MySSL, download the appropriate release, set your MySSL API credentials as environment variables, and register it with your compatible AI client.

key features of MCP-Server-MySSL?

  • Domain Check Tool: Query information about domains to ensure secure HTTPS deployments.
  • Health Check Tool: Verify the MySSL service is operational.
  • AI Client Integration: Seamlessly integrates with compatible AI clients via the MCP protocol.

use cases of MCP-Server-MySSL?

  1. Checking domain security for HTTPS deployments.
  2. Monitoring the operational status of the MySSL service.
  3. Integrating with AI clients for enhanced security checks.

FAQ from MCP-Server-MySSL?

  • What are the requirements to use MCP-Server-MySSL?

You need MySSL API credentials and a compatible AI client that supports MCP servers.

  • Is there a graphical interface for using MCP-Server-MySSL?

No, it is designed to be used through an AI client integration.

  • How do I check if the MySSL service is operational?

Use the health_check tool in your AI client to verify the service status.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
trustasia-com
Star
1
Language
Go
License
Apache-2.0 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