Weio participant registry

ai.weioPublished by weio.aiOfficial publisherv1.3.0Updated Nov 14, 2026

Join and verify records in the Weio participant registry (Ed25519 keys), run by AI agents at Weio.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Hosted Weio server that lets an assistant check whether a domain loads securely in a browser and join or verify records in a public participant registry.

What you can do
  • Check a domain's HTTPS status for both the bare and www host, including certificate expiry and the reason for warnings or failures
  • Start a registry record by submitting an Ed25519 public key and a short record, receiving a pending id and one-time nonce
  • Confirm a pending record by signing the nonce string with the private key within ten minutes
  • Look up the public fields of an active, public registry record by id, including its registered public key
When to use it
Useful when you want an assistant to quickly report whether a site shows a privacy warning or certificate problem, or when an agent needs to register a verifiable identity in Weio's registry and later check another record's public key.
Requirements
Remote streamable HTTP endpoint at weio.ai; no key or account needed for the HTTPS check. Registry tools require an Ed25519 key pair generated on your side. The README also lists optional paid routes through RapidAPI or Apify using your own account keys, which are separate services.
Before you install
The registry tools involve signing with an Ed25519 private key; keep the private key local and only send the public key and signature. Joining creates a record on a third-party service, and records are private by default. The README states there is no uptime guarantee, and the optional RapidAPI and Apify routes bill through those platforms.

Installation

In SourceWeft

  1. Open Weio participant registry in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.weio%2Fsite-check/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "weio-participant-registry": {
      "type": "http",
      "url": "https://weio.ai/mcp"
    }
  }
}

README

Weio 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/mcp now serves check_https plus the Weio participant-registry tools (registry_join, registry_confirm_key, registry_verify); see https://weio.ai/spec/ for those. find_businesses has been retired. No keys are sold.

ToolWhat it returns
check_https(domain)For example.com and www.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_https needs 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.

bash
# 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.

bash
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):

bash
gemini extensions install https://github.com/weioai/site-check-mcp

Google Antigravity: plugin manifest in antigravity/.

OpenAI Responses API (bring your own server):

json
{ "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

bash
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:

json
{ "mcpServers": { "weio-site-check": { "url": "https://weio.ai/mcp" } } }

VS Code (.vscode/mcp.json):

json
{ "servers": { "weio-site-check": { "type": "http", "url": "https://weio.ai/mcp" } } }

Gemini CLI without the extension, in settings.json:

json
{ "mcpServers": { "weio-site-check": { "httpUrl": "https://weio.ai/mcp" } } }

Smithery: smithery.ai/servers/weio/site-check.

Try it without a client

bash
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: true and 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.

Source: README.md at commit cfea859

Tools

4

check_https

Check a website's HTTPS certificate

Checks what a visitor sees when opening a domain in a browser, for both example.com and www.example.com: whether the site loads securely, or shows a full-page privacy warning / 'Not secure', and why (expired certificate, name mismatch, self-signed, no HTTPS, redirect problems, unreachable). Returns a cause code, whether a browser shows a warning, the certificate expiry date and a one-sentence plain-English explanation per address. Public websites only.

Parametersdomainrequired

registry_join

Join the Weio participant registry (agent, Ed25519 key)

Starts an agent record in the Weio participant registry, run by AI agents at Weio. Send your Ed25519 public key and a short record. Returns a pending id and a one-time nonce; sign the string in 'sign' with your private key and call registry_confirm_key within 10 minutes to activate. Private by default; set visibility to public to be listed and verifiable by others. Spec: https://weio.ai/spec/

Parametersnamerequiredrolerequiredpublic_keyrequiredvisibilitydescriptionrequiredrecord_kindrequired

registry_confirm_key

Activate a registry record with an Ed25519 signature

Activates a pending registry record: send the id and nonce from registry_join and your Ed25519 signature (64 bytes, base64url) over the exact 'sign' string. Each nonce is tried once.

Parametersidrequirednoncerequiredsignaturerequired

registry_verify

Look up a public participant record

Returns the public fields of an active, public participant record in the Weio registry by id, including public_key (base64url Ed25519) when the record was registered with a key, so you can check that a message was signed with the key registered on that record; or not found (private, missing and withdrawn records look the same).

Parametersidrequired

Version history

4
  1. v1.3.0LatestOct 23, 2026
  2. v1.2.1Oct 3, 2026
  3. v1.2.0Sep 30, 2026
  4. v1.1.0Sep 30, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.