Incwo MCP
REMOTE · WWW.INCWO.COM
Secure MCP server for exploring incwo CRM data, documents, and email workflows.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security83
- 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 873 tokens (~145/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 26.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 16 to 20.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 6 to 10.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 9 Nov 26 0
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.2.1 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- “complete_account_signup” added a required parameter “business_sector”, so existing callers break ▼ functional
- “complete_account_signup” added a required parameter “city”, so existing callers break ▼ functional
- “complete_account_signup” added a required parameter “in_creation”, so existing callers break ▼ functional
- “complete_account_signup” added a required parameter “siren”, so existing callers break ▼ functional
- “complete_account_signup” added a required parameter “street_address”, so existing callers break ▼ functional
- Tool coverage: 5% → 36% ▲ functional
- “complete_account_signup” added an optional parameter “ape” cosmetic
- “complete_account_signup” added an optional parameter “business_type_id” cosmetic
- “complete_account_signup” added an optional parameter “siret” cosmetic
- “complete_account_signup” reworded the description of “business_country” cosmetic
- “complete_account_signup” reworded the description of “business_location” cosmetic
- “complete_account_signup” reworded the description of “contact_phone” cosmetic
- 8 Nov 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: 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. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 5 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
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://www.incwo.com/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=incwo.com | CN=YR2,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 4096 | SHA256-RSA | 5cff2a3a00f925adbc6a869a36bc614b099 |
| SANs: *.incwo.com, incwo.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.incwo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| incwo.com. | 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 tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="incwo MCP", resource_metadata="https://www.incwo.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="incwo MCP", resource_metadata="https://www.incwo.com/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| strict-transport-security | max-age=15768000 |
Protected resource metadata
| Document | https://www.incwo.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.incwo.com/mcp |
| Authorisation server | https://www.incwo.com/oauth2/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.incwo.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.incwo.com/mcp | Inconclusive | 401 |
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 →
call_incwo_tool Call incwo tool ~62
Appelle un outil du catalogue renvoyé par get_incwo_tools, avec les droits natifs du compte connecté. Transmettre le business_file_id actif dans arguments pour chaque appel métier.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
complete_account_signup Complete account signup ~314
Crée le nouveau compte et le premier dossier après vérification et acceptation explicite des conditions. Réutiliser le code de l’e-mail. Ne retourne aucun identifiant de connexion ; la connexion aux données reste OAuth.
| Name | Type | Req | Description |
|---|---|---|---|
| accept_terms | boolean | yes | – |
| ape | string | – | Code NAF/APE si connu ; distinct du secteur d’activité incwo. |
| business_country | string | yes | Pays du siège, par exemple France. |
| business_location | string | yes | Code postal du siège. |
| business_sector | string | yes | Valeur du catalogue business_sectors de get_account_signup_requirements. |
| business_type_id | integer | – | Forme juridique, valeur du catalogue business_types si connue. |
| city | string | yes | – |
| code | string | yes | – |
| contact_phone | string | yes | Téléphone avec indicatif international, par exemple +33123456789. |
| first_name | string | yes | – |
| in_creation | boolean | yes | Vrai uniquement si l’entreprise est encore en cours de création. |
| last_name | string | yes | – |
| name | string | yes | – |
| signup_id | string | yes | – |
| siren | string | yes | SIREN à 9 chiffres en France ; numéro d’immatriculation local à l’étranger. Vide seulement pour une entreprise en création. |
| siret | string | – | SIRET du siège français si connu, cohérent avec le SIREN. |
| street_address | string | yes | – |
| terms_version | integer | yes | – |
No output schema declared.
No examples provided.
get_account_signup_requirements Get account signup requirements ~29
À appeler avant une inscription : renvoie les conditions natives à présenter et les champs requis.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_incwo_tools Get incwo tools ~103
Connecte votre compte par OAuth si nécessaire, puis renvoie le dossier actif et le catalogue des outils autorisés. À appeler après une inscription ou avant call_incwo_tool.
| Name | Type | Req | Description |
|---|---|---|---|
| business_file_id | integer | – | Dossier actif conservé par le client. Les droits sont vérifiés pour cet appel ; aucune sélection n'est mémorisée par le serveur. |
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
start_account_signup Start account signup ~68
Démarre une inscription directement dans la conversation et envoie un code valable dix minutes. La clé d’idempotence est un texte ordinaire : réutiliser la même demande après une réponse perdue.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| idempotency_key | string | yes | – |
No output schema declared.
No examples provided.
verify_account_signup Verify account signup ~48
Vérifie le code reçu par e-mail pour cette inscription. Aucun accès à un compte existant ni aux données métier.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| signup_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Incwo MCP server?
Incwo MCP is a hosted endpoint at https://www.incwo.com/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 · www.incwo.com
claude mcp add --transport http incwo-incwo 'https://www.incwo.com/mcp'
What is the Incwo MCP server?
Incwo MCP is listed in the public MCP registry as io.github.incwo/incwo. Secure MCP server for exploring incwo CRM data, documents, and email workflows. This page covers its hosted endpoint (https://www.incwo.com/mcp).
Is the Incwo MCP server safe to use?
Incwo MCP scores 75 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 Incwo MCP server expose?
Incwo MCP exposes 6 tools: get_account_signup_requirements, start_account_signup, verify_account_signup, complete_account_signup, get_incwo_tools, call_incwo_tool. Their descriptions and schemas cost roughly 624 tokens of context every time the server is loaded.
Does the Incwo MCP server require authentication?
Yes. Incwo MCP 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 Incwo MCP server still maintained?
Incwo MCP 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 Incwo MCP server?
VerifyMCP ran 12 checks on Incwo MCP, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Incwo MCP: HTTPS. 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.