Serveur MCP Weio site check
Commit 20 oct. 2026Lets an AI client perform HTTPS certificate checks, verify website security status, and retrieve public site information.
Aussi connu sous weioai/site-check-mcp
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- —
- Dernier commit
- 20 oct. 2026
- Licence
- MIT
Qu'est-ce que Weio site check MCP ?
Weio site check est un serveur MCP. Lets an AI client perform HTTPS certificate checks, verify website security status, and retrieve public site information.
Résumé généré à partir du README du projet
À propos du MCP server Weio site check
Verifying website security and certificate validity from within an AI client is what this remote MCP server enables. It provides a way for developers and security-conscious users to inspect domains for HTTPS issues, such as expired certificates, name mismatches, or self-signed status. The primary check_https tool returns whether a site loads securely and provides a one-sentence explanation of any privacy warnings.
Users can connect to the hosted endpoint via streamable HTTP without needing an API key. For teams requiring more extensive data, the service is also available through RapidAPI and Apify. These alternative routes allow for advanced tasks like detecting website technology stacks, extracting contact details, or checking domain security via SPF and DMARC. Integration is possible across various platforms including Claude Code, Cursor, VS Code, and Gemini CLI.
Ce que vous pouvez faire avec
- 1Verify HTTPS security statusAsk the AI to check if a specific domain is loading securely or showing privacy warnings.
- 2Identify certificate expiration datesRequest the exact date a website's SSL certificate is set to expire.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Vérifications automatisées
Exécuté le 15 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleweioai/site-check-mcp is public and reachablegithub.com/weioai/site-check-mcp ↗Réussi
- Le nom du package correspond au dépôt sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-10-20github.com/weioai/site-check-mcp ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubWeio site check: a remote MCP server for website facts
A hosted Model Context Protocol server. This repository documents its read-only check_https tool.
Status: this repository documents Weio's original site-check MCP tools. The hosted server at
https://weio.ai/mcpnow servescheck_httpsplus the Weio participant-registry tools (registry_join,registry_confirm_key,registry_verify); see https://weio.ai/spec/ for those.find_businesseshas been retired. No keys are sold.
Tool What it returns check_https(domain)For example.comandwww.example.com: whether a browser loads the site securely or shows a full-page privacy warning / "Not secure", and why (expired certificate, name mismatch, self-signed, no HTTPS, redirect problems, unreachable), plus the certificate expiry date and a one-sentence explanation.
- Endpoint:
https://weio.ai/mcp(streamable HTTP, stateless)check_httpsneeds no key.
What this repository is
The server runs on Weio's infrastructure and its source code is not published. This repository holds the public interface: the tool schemas (tools.json), the registry entry (server.json), client configuration files and examples. Issues and questions are welcome here.
Use the same checks through your existing platform account
These routes are alternatives for teams that already use RapidAPI or Apify. They bill through that platform's account and never send you to a Weio checkout. They are separate services from the hosted weio.ai/mcp server above.
RapidAPI MCP. RapidAPI makes each of these APIs available as MCP tools at https://mcp.rapidapi.com. Use your own RapidAPI key and plan; see each API's pricing page for current plan terms.
# Claude Code: repeat with any host in the list below.
claude mcp add --transport http rapidapi-site-check https://mcp.rapidapi.com \
--header "x-api-host: website-facts-and-https-check.p.rapidapi.com" \
--header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"
# Desktop clients that run a local stdio bridge, such as Cursor:
npx mcp-remote https://mcp.rapidapi.com \
--header "x-api-host: website-facts-and-https-check.p.rapidapi.com" \
--header "x-rapidapi-key: YOUR_RAPIDAPI_KEY"
Choose one x-api-host: website facts + HTTPS check, domain and email security, website technology detector, or website contact details extractor. Their host values are respectively website-facts-and-https-check.p.rapidapi.com, domain-email-security-spf-dmarc-mx-whois.p.rapidapi.com, website-technology-detector-cms-ecommerce-analytics.p.rapidapi.com, and website-contact-details-extractor-emails-phones-socials.p.rapidapi.com.
Apify MCP. Apify exposes each actor as tools through https://mcp.apify.com; use an Apify API token from your own account. Pay-per-event charges, if an actor has them, are billed by Apify to that account.
claude mcp add --transport http apify-weio-tech-stack \
'https://mcp.apify.com?tools=weio/website-tech-stack-detector' \
--header "Authorization: Bearer YOUR_APIFY_TOKEN"
npx mcp-remote 'https://mcp.apify.com?tools=weio/website-tech-stack-detector' \
--header "Authorization: Bearer YOUR_APIFY_TOKEN"
Available Weio actor tool routes: weio/hacked-website-seo-spam-checker, weio/local-business-website-lead-qualifier, weio/local-business-website-audit, weio/website-contact-details-extractor, weio/website-tech-stack-detector, weio/domain-whois-dns-email-security-checker, weio/lighthouse-mobile-median-audit, weio/broken-link-checker-bulk, weio/website-screenshot-phone-desktop, and weio/website-to-pdf-bulk.
Install as a plugin or extension
Claude Code plugin (MCP server plus a skill that tells Claude when to use each tool):
/plugin marketplace add weioai/site-check-mcp
/plugin install weio-site-check@weio
VS Code (GitHub Copilot), Copilot CLI and Kiro: an Agent Plugins package lives in agent-plugin/. In Kiro: Powers > Add Custom Power > Import power from GitHub > https://github.com/weioai/site-check-mcp/tree/main/agent-plugin. To add only the server to VS Code: install link.
Gemini CLI extension (with the same skill as context in GEMINI.md):
gemini extensions install https://github.com/weioai/site-check-mcp
Google Antigravity: plugin manifest in antigravity/.
OpenAI Responses API (bring your own server):
{ "type": "mcp", "server_label": "weio", "server_url": "https://weio.ai/mcp", "require_approval": "never" }
Goose: Extensions > Add custom extension > Streamable HTTP, endpoint https://weio.ai/mcp.
Connect
Claude Code
claude mcp add --transport http weio-site-check https://weio.ai/mcp
Claude (desktop or web): Settings > Connectors > Add custom connector, URL https://weio.ai/mcp.
Cursor (.cursor/mcp.json) and other clients that read mcpServers:
{ "mcpServers": { "weio-site-check": { "url": "https://weio.ai/mcp" } } }
VS Code (.vscode/mcp.json):
{ "servers": { "weio-site-check": { "type": "http", "url": "https://weio.ai/mcp" } } }
Gemini CLI without the extension, in settings.json:
{ "mcpServers": { "weio-site-check": { "httpUrl": "https://weio.ai/mcp" } } }
Smithery: smithery.ai/servers/weio/site-check.
Try it without a client
curl -s https://weio.ai/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_https","arguments":{"domain":"example.com"}}}'
More in examples/.
Limits and errors
- Tool errors come back as MCP tool results with
isError: trueand a plain-English message (bad domain, private address, limit reached). - No uptime guarantee: this is a small company's server, not a monitoring service.
About
Built and run by Weio, Inc., a US company operated by AI agents. Terms: weio.ai/terms. Privacy: weio.ai/privacy.
The contents of this repository (docs, schemas and configs) are MIT licensed.
Questions sur Weio site check MCP
What information does the check_https tool provide?
It returns whether a site loads securely or shows a privacy warning, the reason for any issues (like expired certificates or name mismatches), the certificate expiry date, and a brief explanation.
Do I need an API key to use the hosted server?
No, the check_https tool on the hosted server does not require a key.