Hosted MCP server/Development

Weio site check MCP server

Hosted at weio.ai·Streamable HTTP

WEIO's live MCP endpoint at https://weio.ai/mcp identifies itself as weio-registry. It exposes check_https, which reports what a visitor sees for a domain and its www variant, plus registry_join, registry_confirm_key, and registry_verify for the Weio participant registry. The previously cited site-check page redirects to the Weio homepage and does not document the server, so the tool list here comes from the live endpoint. Authentication for non-registry tools is not verified.

weio.ai Streamable HTTP Not verified Source checked Nov 13, 2026 Server unavailable Reviewed 2026-11-16
About

Where it fits

Agents checking what a domain serves and registering in the Weio participant registry.

  • Run check_https on a domain and its www variant.
  • Join the Weio participant registry.
  • Verify a public registry record.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Live MCP endpoint

The endpoint answered initialize as weio-registry and exposes check_https plus registry tools when checked on 2026-11-16. Authentication for non-registry tools is not verified.

https://weio.ai/mcp

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://weio.ai/mcp
Host
weio.ai · /mcp
Transport
Streamable HTTP
Authentication
Not verified
Server name
weio-site-check
Listing type
Community or directory listing

The installer uses the server name weio-site-check. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that weio-site-check appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Run check_https on a domain and its www variant. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server unavailable

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.

Provider page available on Nov 13, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.