{"id":"trustasia-com-myssl-mcp-server-go","name":"myssl-mcp-server-go","homepage":null,"repo_url":"https://github.com/trustasia-com/myssl-mcp-server-go","category":"security","subcategories":[],"tags":["mcp","security","monitoring","go","api-integration","devtools"],"what_it_does":"myssl-mcp-server is an MCP server (Go) that exposes tools to query MySSL-based domain/IP security information (domain_check) and to check MySSL service health (health_check), intended to be used by compatible AI clients via the MCP protocol using MySSL AccessKey/SecretKey credentials.","use_cases":["Verify whether domains/IPs meet HTTPS/security-related checks via MySSL","Automate security posture checks for websites/IPs using an AI agent workflow","Operational monitoring via an MCP-accessible health check tool"],"not_for":["Production security decisioning without validating results and response provenance","Use without understanding MySSL API rate limits/costs and MCP client execution constraints","Handling highly sensitive credentials in untrusted environments"],"best_when":"You want lightweight, agent-invoked security/health lookups integrated into an AI client that supports MCP.","avoid_when":"You need a fully documented, contract-first API (OpenAPI) or strong least-privilege auth controls clearly documented for the MCP server itself.","alternatives":["Use MySSL API directly from your own backend with a REST client","Wrap MySSL API with a custom tool server that includes stricter auth, logging redaction, and structured errors","Use existing security scanning/monitoring tools (DNS/TLS/HTTP security checks) if MySSL coverage is not required"],"af_score":37.8,"security_score":47.5,"reliability_score":15.0,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:51:23.181042+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["MySSL AccessKey + SecretKey via environment variables"],"oauth":false,"scopes":false,"notes":"README instructs setting AccessKey and SecretKey as environment variables for the MCP server to call the MySSL API. No OAuth or explicit scope granularity for the MCP server is documented."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing/cost information provided in README."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":37.8,"security_score":47.5,"reliability_score":15.0,"mcp_server_quality":55.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":5.0,"tls_enforcement":80.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":30.0,"secret_handling":40.0,"security_notes":"Security posture inferred from README only. It suggests using AccessKey/SecretKey, but does not document TLS requirements for the MCP<>AI client channel or the underlying MySSL API usage, does not describe scope/least-privilege, and provides no details on secret handling/log redaction. Treat credentials as sensitive and avoid exposing them to untrusted MCP hosts.","uptime_documented":0.0,"version_stability":20.0,"breaking_changes_history":20.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"No guidance indicating whether domain_check/health_check are idempotent or how repeated calls are handled.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Credentials are provided via environment variables; ensure the MCP host process environment is secured and not logged.","The README does not describe tool argument schema, response format, or error codes—agents may require experimentation to craft correct inputs.","Rate limiting/cost behavior of the underlying MySSL API is not documented here, so agents may need conservative call patterns."]}}