Well
REMOTE · API.WELLAPP.AI · SCANNED SEP 21
Connect your AI to your Well financial data - invoices, companies, contacts.
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 62440 tokens (~752/item across 83 items; 82 tools + 1 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 Management94
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 51 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the description of tool "well_preview_invoice_fetch" contains an instruction to conceal the call from the user, the text "never tell the user", at byte 6221 of that field, plus 2 further marker(s) of the same kind. See how to fix → Fail
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 84 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
- Supports UI / widget rendering.Pass
How do I install the Well MCP server?
Well is a hosted endpoint at https://api.wellapp.ai/v1/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 · api.wellapp.ai
claude mcp add --transport http wellapp-ai-well-mcp 'https://api.wellapp.ai/v1/mcp'
{
"mcpServers": {
"wellapp-ai-well-mcp": {
"url": "https://api.wellapp.ai/v1/mcp"
}
}
} {
"servers": {
"wellapp-ai-well-mcp": {
"type": "http",
"url": "https://api.wellapp.ai/v1/mcp"
}
}
} [mcp_servers.wellapp-ai-well-mcp] url = "https://api.wellapp.ai/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wellapp-ai-well-mcp": {
"type": "remote",
"url": "https://api.wellapp.ai/v1/mcp",
"enabled": true
}
}
} openclaw mcp add wellapp-ai-well-mcp --url 'https://api.wellapp.ai/v1/mcp' --transport streamable-http
mcp_servers:
wellapp-ai-well-mcp:
url: "https://api.wellapp.ai/v1/mcp" {
"McpServers": {
"wellapp-ai-well-mcp": {
"Transport": "http",
"Url": "https://api.wellapp.ai/v1/mcp"
}
}
} assistant mcp add wellapp-ai-well-mcp -t streamable-http -u 'https://api.wellapp.ai/v1/mcp'
{
"mcpServers": {
"wellapp-ai-well-mcp": {
"type": "http",
"url": "https://api.wellapp.ai/v1/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.
- 21 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- Schema quality: 48422 → 57629 ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 Sept 2026 · Probed https://api.wellapp.ai/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.wellapp.ai | CN=WR3,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | RSA 2048 | SHA256-RSA | ad5f31d94743cd7310d98dfac480b1dc |
| SANs: api.wellapp.ai | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.wellapp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| wellapp.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource="https://api.wellapp.ai/v1/mcp", authorization_server="https://api.wellapp.ai"
Bearer resource="https://api.wellapp.ai/v1/mcp", authorization_server="https://api.wellapp.ai"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.wellapp.ai/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.wellapp.ai/v1/mcp | HTTPS enforced | 301 | https://api.wellapp.ai:443/v1/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 →
well_update_person ~251
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| first_name | string | – | – |
| idempotency_key | string | – | – |
| job_title | – | – | – |
| last_name | string | – | – |
| person_id | string | yes | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | – |
| full_name | string | – | – |
| person_id | string | – | – |
| success | boolean | yes | – |
No examples provided.
well_upload_document ~533
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | – |
| filename | string | yes | – |
| idempotency_key | string | – | – |
| mime_type | string | yes | – |
| source_task_id | string | – | – |
| source_transaction_id | string | – | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| actual_bytes | number | – | – |
| deduplicated | boolean | – | – |
| document_id | string | – | – |
| error | string | – | – |
| error_code | string | – | – |
| filename | string | – | – |
| max_bytes | number | – | – |
| mime_type | string | – | – |
| outcome | – | – | – |
| size_bytes | number | – | – |
| source_task_id | – | – | – |
| source_transaction_id | – | – | – |
| success | boolean | yes | – |
No examples provided.
well_upload_statement_bytes ~398
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | – |
| filename | string | yes | – |
| idempotency_key | string | – | – |
| sha256 | string | – | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| byte_length | integer | – | – |
| content_sha256 | string | – | – |
| deduplicated | boolean | – | – |
| document_id | string | – | – |
| error | string | – | – |
| success | boolean | yes | – |
No examples provided.
well_upload_statement_content ~393
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| content_text | string | yes | – |
| filename | string | yes | – |
| idempotency_key | string | – | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| byte_length | integer | – | – |
| content_sha256 | string | – | – |
| deduplicated | boolean | – | – |
| document_id | string | – | – |
| error | string | – | – |
| success | boolean | yes | – |
No examples provided.
well_upsert_accounting_settings ~559
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_framework | string | – | – |
| base_currency | string | – | – |
| coa_confirmed | boolean | – | – |
| country | string | – | – |
| first_fiscal_year_start_date | – | – | – |
| fiscal_year_start_month | – | – | – |
| idempotency_key | string | – | – |
| incorporation_date | – | – | – |
| tax_id_type | string | – | – |
| tax_id_value | string | – | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accounting_framework | – | – | – |
| base_currency | – | – | – |
| coa_confirmed | – | – | – |
| country | – | – | – |
| error | string | – | – |
| first_fiscal_year_start_date | – | – | – |
| fiscal_year_start_month | – | – | – |
| incorporation_date | – | – | – |
| success | boolean | yes | – |
| tax_id_type | – | – | – |
| tax_id_value | – | – | – |
No examples provided.
well_wait_for_selection ~1,592
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| timeout_s | number | – | – |
| waiting_notice | string | – | – |
| workspace_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| already_set | boolean | – | – |
| error | string | – | – |
| hint | string | – | – |
| kind | string | – | – |
| resolved_workspace | object | – | – |
| selection | object | – | – |
| status | string | – | – |
| success | boolean | yes | – |
No examples provided.
What is the Well MCP server?
Well is an MCP server listed in the public MCP registry as io.github.WellApp-ai/well-mcp. Connect your AI to your Well financial data - invoices, companies, contacts. This page covers its hosted endpoint (https://api.wellapp.ai/v1/mcp).
Is the Well MCP server safe to use?
Well 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.
Does the Well MCP server require authentication?
Yes. Well 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 Well MCP server still maintained?
Well is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.