WeInc
REMOTE · MY.WE.INC
Start, browse and manage your WeInc websites from your AI assistant.
Available components
Last scanned (18 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 −43
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 8 Nov 26 −11
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “create_client” was removed ▼ security
- Tool “create_project” was removed ▼ security
- Tool “get_analytics” was removed ▼ security
- Tool “get_preview_urls” was removed ▼ security
- Tool “get_project” was removed ▼ security
- Tool “list_clients” was removed ▼ security
- Tool “list_plans” was removed ▼ security
- Tool “list_projects” was removed ▼ security
- Tool “list_templates” was removed ▼ security
- Tool “update_project” was removed ▼ security
- Tool “create_website_from_template” rewrote its description, which is the text the model reads security
- Tool “find_templates” rewrote its description, which is the text the model reads security
- Tool “publish_website” rewrote its description, which is the text the model reads security
- Tool “start_website” rewrote its description, which is the text the model reads security
- Tool “publish_website” is now declared destructive security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 43% → 100% ▲ functional
- “create_website_from_template” dropped the optional parameter “publish” cosmetic
- 7 Nov 26 +3
- Tool “start_website” rewrote its description, which is the text the model reads security
- Schema quality: 52 → 71 ▼ functional
- Tool coverage: 25% → 43% ▲ functional
- Schema quality: unverified → 100 ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- Destructive annotations: pass → 100 functional
- New resource “WeInc website card” functional
- New tool “create_website_from_template” functional
- New tool “publish_website” functional
- 6 Nov 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
- 31 Oct 26 0
- Tool “create_project” rewrote its description, which is the text the model reads security
- “create_project” added an optional parameter “client_id” cosmetic
- “create_project” made “client_email” optional cosmetic
- 20 Oct 26 0
- Tool “update_project” rewrote its description, which is the text the model reads security
- Tool “update_project” is now declared destructive security
- 14 Oct 26 0
- Schema quality: 32 → 48 ▼ functional
- Tool coverage: 0% → 26% ▲ functional
- Schema quality: fair → good functional
- New tool “find_templates” functional
- New tool “my_websites” functional
- New tool “request_change” functional
- New tool “start_website” functional
- New tool “website_details” functional
- 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
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 21 Nov 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 | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2d5860d1113dad3c13f6dc215127d942 |
| 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. | DS published | 13114, 18077 | 8, 8 | Verified |
| we.inc. | No DS | 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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://my.we.inc/.well-known/oauth-protected-resource/api/mcp"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://my.we.inc/.well-known/oauth-protected-resource/api/mcp" | 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://*.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 https://static.cloudflareinsights.com 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' data: https://cloudflare |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://my.we.inc/.well-known/oauth-protected-resource/api/mcp" |
Protected resource metadata
| Document | https://my.we.inc/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://my.we.inc/api/mcp |
| 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 | Auth required | 401 | |
| http (plaintext) | http://my.we.inc/api/mcp | HTTPS enforced | 301 | 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_website_from_template Create website from template ~322
Instantly make a finished website in the person's own WeInc account from one of WeInc's ready-made designs, personalised with their business name and details. Takes about a second and returns the editor link where they can see it, change anything and publish. A few general sections (such as service highlights) are placeholder text for the person to edit. Use this when the person wants a WeInc website made from a ready-made design. Call it right away with what they have told you; the business name is enough, so do not ask follow-up questions first (they can change anything afterwards). Pass `template_id` from find_templates, or leave it out and give `business_type` and/or `description` so the best design is picked. Only pass details the person actually gave; never invent a phone number, email or city. For a custom AI-designed site use start_website instead.It is not published; offer publish_website afterwards if the person wants it live.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | The business name, exactly as the person gave it. |
| business_type | string | – | What the business is, e.g. 'bakery' or 'plumber'. |
| city | string | – | Town or city it serves, if given. |
| description | string | – | A sentence or two about the business, in the person's words. |
| string | – | Contact email, if given. | |
| phone | string | – | Phone number, if given. |
| template_id | string | – | Design id from find_templates (optional). |
No output schema declared.
No examples provided.
find_templates Find website templates ~84
Search WeInc's website templates by keywords (e.g. 'restaurant', 'portfolio', 'online store') and/or category. Returns id, name, description, category, features and a start link. Pass a chosen id to create_website_from_template as template_id.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Limit to one category. |
| query | string | – | Keywords to match. |
No output schema declared.
No examples provided.
my_websites List my websites ~47
List the signed-in person's own WeInc websites, newest activity first: name, live URL if published, editor link and last updated time. Use the id with website_details or request_change.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_website Publish website ~127
Put one of the person's own WeInc websites live on the internet at its weinc.app address (or its connected domain), exactly like pressing Publish in the editor. Usually takes 15-45 seconds and returns the live link; if it takes longer it answers 'publishing' and website_details gives the live link shortly after. The site becomes public, so ask the person before calling this. The account's plan sets how many sites can be live at once; a refusal explains why.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Website id from my_websites or create_website_from_template. |
No output schema declared.
No examples provided.
request_change Request a website change ~93
Prepare a change to one of the person's own websites. Returns an editor link that opens their site with the instruction already typed in the WeInc chat box; it is NOT sent until they press send. The instruction should say what to change, where, and the exact new text.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | yes | The change to make, in plain language. |
| projectId | string | yes | Website id from my_websites. |
No output schema declared.
No examples provided.
start_website Start a new website ~172
Only for when the person explicitly asks for a custom, from-scratch, AI-designed WeInc website. It does NOT make a site: it returns a link, and the AI build starts only after the person confirms in their browser. For any other request for a WeInc website ("make me a website for my bakery"), use create_website_from_template instead: it makes the finished site immediately. Put everything you know into `brief`: business name, what they do, location, services, audience, tone, pages wanted, contact details. Optionally pass `template_id` from find_templates. The build starts only after the person confirms on that page.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | Full description of the business and the website wanted. |
| template_id | string | – | Template id from find_templates (optional). |
No output schema declared.
No examples provided.
website_details Website details ~53
Details of one of the person's own websites: name, whether it is published, live URL, custom domains with status, last published time and editor link.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Website id from my_websites. |
No output schema declared.
No examples provided.
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'
What is the WeInc MCP server?
WeInc is an MCP server listed in the public MCP registry as io.github.umairalisadaqat/weinc. Start, browse and manage your WeInc websites from your AI assistant. This page covers its hosted endpoint (https://my.we.inc/api/mcp).
Is the WeInc MCP server safe to use?
WeInc scores 38 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 7 tools: start_website, find_templates, create_website_from_template, my_websites, website_details, and 2 more. Their descriptions and schemas cost roughly 898 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the WeInc MCP server?
VerifyMCP ran 5 checks on WeInc, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about WeInc: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.