WeInc
REMOTE · MY.WE.INC · SCANNED SEP 28
Manage WeInc AI website builder orgs: projects, publishing, custom domains, and previews.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 328 tokens (~32/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the WeInc MCP server?
WeInc is a hosted endpoint at https://my.we.inc/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · my.we.inc
claude mcp add --transport http umairalisadaqat-weinc 'https://my.we.inc/api/mcp'
{
"mcpServers": {
"umairalisadaqat-weinc": {
"url": "https://my.we.inc/api/mcp"
}
}
} {
"servers": {
"umairalisadaqat-weinc": {
"type": "http",
"url": "https://my.we.inc/api/mcp"
}
}
} [mcp_servers.umairalisadaqat-weinc] url = "https://my.we.inc/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"umairalisadaqat-weinc": {
"type": "remote",
"url": "https://my.we.inc/api/mcp",
"enabled": true
}
}
} openclaw mcp add umairalisadaqat-weinc --url 'https://my.we.inc/api/mcp' --transport streamable-http
mcp_servers:
umairalisadaqat-weinc:
url: "https://my.we.inc/api/mcp" {
"McpServers": {
"umairalisadaqat-weinc": {
"Transport": "http",
"Url": "https://my.we.inc/api/mcp"
}
}
} assistant mcp add umairalisadaqat-weinc -t streamable-http -u 'https://my.we.inc/api/mcp'
{
"mcpServers": {
"umairalisadaqat-weinc": {
"type": "http",
"url": "https://my.we.inc/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://my.we.inc/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=we.inc | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | a8092e552f6f2f0b13659c2d38e2250a |
| SANs: we.inc, *.we.inc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of my.we.inc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| inc. | present | 13114, 18077 | 8, 8 | Verified |
| we.inc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://my.we.inc/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://my.we.inc/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://js.stripe.com https://challenges.cloudflare.com https://us-assets.i.posthog.com https://va.vercel-scripts.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://unpkg.com https://widget.intercom.io https://js.intercomcdn.com https://cdn.tailwindcss.com https://esm.sh https://connect.facebook.net blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://api.fontshare.com https://db.onlinewebfonts.com; font-src 'self' https://fonts.gstatic.com https://cdn.jsdelivr.net https://cdn.fontshare.com https://db.onlinewebfonts.com data:; img-src 'self' data: blob: https:; media-src 'self' https://d8j0ntlcm91z4.cloudfront.net https://res.cloudinary.com https://*.cloudinary.com https://stream.mux.com https://*.mux.com https://*.cloudflarestream.com https://cdn.coverr.co https://videos.pexels.com blob:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://js.stripe.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://my.we.inc/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://my.we.inc |
| Authorisation server | https://my.we.inc |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://my.we.inc/api/mcp | Verified | 200 | |
| http (plaintext) | http://my.we.inc/api/mcp | HTTPS enforced | 308 | https://my.we.inc/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_client Create client ~49
Create a client (end-customer) for the org.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | yes | – | |
| name | string | – | – |
| plan_id | string | – | – |
No output schema declared.
No examples provided.
create_project Create project ~52
Create a project for one of the org's clients (by email).
| Name | Type | Req | Description |
|---|---|---|---|
| client_email | string | yes | – |
| description | string | – | – |
| name | string | yes | – |
| template_id | string | – | – |
No output schema declared.
No examples provided.
get_analytics Get analytics ~36
Aggregated analytics for the org (optionally one project).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| project_id | string | – | – |
No output schema declared.
No examples provided.
get_preview_urls Get preview URLs ~26
Get published/preview URLs for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
get_project Get project ~23
Get a single project by id.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | – |
No output schema declared.
No examples provided.
list_clients List clients ~14
List the org's clients.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_plans List plans ~17
List the org's client-facing plans.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects List projects ~50
List builder projects for the org (paginated, filterable).
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_templates List templates ~14
List the org's templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_project Update project ~47
Update a project's name, description, or status.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | – | – |
| projectId | string | yes | – |
| status | string | – | – |
No output schema declared.
No examples provided.
What is the WeInc MCP server?
WeInc is an MCP server listed in the public MCP registry as io.github.umairalisadaqat/weinc. Manage WeInc AI website builder orgs: projects, publishing, custom domains, and previews. This page covers its hosted endpoint (https://my.we.inc/api/mcp).
Is the WeInc MCP server safe to use?
WeInc scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WeInc MCP server expose?
WeInc exposes 10 tools: list_projects, create_project, get_project, update_project, get_preview_urls, and 5 more. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.
Does the WeInc MCP server require authentication?
Yes. WeInc asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the WeInc MCP server still maintained?
WeInc is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.