MySSL MCP

Created By
trustasia-coma year ago
Overview

what is MySSL MCP?

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

how to use MySSL MCP?

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

key features of MySSL MCP?

  • 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 MySSL MCP?

  1. Checking the security status of a domain before deployment.
  2. Monitoring the operational status of the MySSL service.
  3. Integrating with AI clients for automated security checks.

FAQ from MySSL MCP?

  • What are the requirements to use MySSL MCP?

You need MySSL API credentials (AccessKey and SecretKey) and a compatible AI client that supports MCP servers.

  • How do I install MySSL MCP?

Download the release, extract the package, and set your MySSL API credentials as environment variables.

  • Can I use MySSL MCP with any AI client?

Yes, as long as the AI client supports MCP servers.

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

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago