Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ClaraConverts

REMOTE · CLARACONVERTS.COM · SCANNED SEP 25

Provision and manage a ClaraConverts AI conversion-agent widget: pricing, trials, account setup.

+1 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1755 tokens (~175/item across 10 items; 10 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the ClaraConverts MCP server?

ClaraConverts is a hosted endpoint at https://claraconverts.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 · claraconverts.com

# add to Claude Code
claude mcp add --transport http com-claraconverts-clara 'https://claraconverts.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-claraconverts-clara": {
      "url": "https://claraconverts.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-claraconverts-clara": {
      "type": "http",
      "url": "https://claraconverts.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-claraconverts-clara]
url = "https://claraconverts.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-claraconverts-clara": {
      "type": "remote",
      "url": "https://claraconverts.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-claraconverts-clara --url 'https://claraconverts.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-claraconverts-clara:
    url: "https://claraconverts.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-claraconverts-clara": {
      "Transport": "http",
      "Url": "https://claraconverts.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-claraconverts-clara -t streamable-http -u 'https://claraconverts.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-claraconverts-clara": {
      "type": "http",
      "url": "https://claraconverts.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 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
  • 20 Sept 26 0
    • Stability: 0.97 → pass security
  • 19 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.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 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.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 25 Sept 2026 · Probed https://claraconverts.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=claraconverts.com CN=WE1,O=Google Trust Services,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA256 2c2df33db802eb1132e5e92f12a8e90
SANs: claraconverts.com, www.claraconverts.com, *.www.claraconverts.com
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 claraconverts.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
claraconverts.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://claraconverts.com/mcp Verified 200
http (plaintext) http://claraconverts.com/mcp HTTPS enforced 301 https://claraconverts.com/mcp
MCP tools · 10 exposed · ~1,393 tokens

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 →

Tool Tokens
configure_integration ~240

Connect an integration from list_integrations to your trial tenant. For API-key providers, pass api_key and any required config fields and it connects immediately (Cal.com needs list_calcom_event_types called first for event_type_id — every other provider's config fields are typed directly from that provider's own dashboard). For OAuth providers (Shopify, HubSpot, Google Calendar, Square, ...), returns a connect_url a human must open and approve — it can't be completed headlessly. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
api_keystring–The provider's API key/token, for API-key-based providers.
configobject–Provider-specific config fields (see the provider's configFields — e.g. Cal.com needs event_type_id).
providerstringyesThe integration name from list_integrations, e.g. "calcom".
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.

No output schema declared.

No examples provided.

create_trial_tenant ~199

Create a free, no-card ClaraConverts trial for a website. Returns a working embed snippet and a bearer token for follow-up calls (get_embed_snippet, get_upgrade_link). Trial lasts 14 days. One live trial per owner_email — provisioning multiple sites (e.g. for an agency's clients) isn't supported by these tools yet; each site needs its own contact email for now.

NameTypeReqDescription
conversion_goalstring–Optional: what Clara should drive (e.g. "book a demo", "capture a lead").
display_namestring–Optional display name for the business.
owner_emailstringyesThe site owner's real, monitored email — this is the only place their Studio login link and trial-expiry reminders go. Ask the human for it; don't invent one or reuse an address found elsewhere (requ…
site_urlstringyesURL of the site Clara will be installed on (required).

No output schema declared.

No examples provided.

get_embed_snippet ~88

Get the <script> embed snippet for your trial tenant. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.

No output schema declared.

No examples provided.

get_pricing ~26

Get ClaraConverts plan pricing (Standard, Pro, Volume) in USD/month.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_tenant_settings ~124

Read back your trial tenant's current persona/widget settings and which integrations are connected — the read counterpart to update_tenant_settings and configure_integration, useful for confirming a change actually took or resuming work without re-guessing current state. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.

No output schema declared.

No examples provided.

get_upgrade_link ~101

Get a Stripe Checkout link to upgrade your trial tenant to a paid plan. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.
tierstringyesPlan to upgrade to.

No output schema declared.

No examples provided.

list_calcom_event_types ~145

List the meeting types on a Cal.com account by name (with account timezone). Call this BEFORE configure_integration with provider="calcom" — its required event_type_id can't be typed from memory, it has to be picked from this list. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
api_keystringyesThe Cal.com API key to look up meeting types for.
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.

No output schema declared.

No examples provided.

list_integrations ~29

List the CRM, booking, commerce, payments, and other integrations ClaraConverts can connect to.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

refresh_site_knowledge ~124

Re-crawl your site and update what Clara knows about it. Trials skip the crawl at creation to stay fast, so Clara knows nothing about your business until this runs at least once. Can take up to a minute for a large site. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.

No output schema declared.

No examples provided.

update_tenant_settings ~317

Update your trial tenant's persona and widget settings (name, goal, branding, position, lead notification email). Only the fields you pass are changed. Requires the secret_key from create_trial_tenant, either as the secret_key argument or an "Authorization: Bearer <secret_key>" header.

NameTypeReqDescription
brand_colorstring–Hex color, e.g. "#0b5ed7".
chatbot_avatar_urlstring–URL of a custom avatar image for the widget.
chatbot_namestring–Override the AI's name (defaults to "Clara").
conversion_goalstring–What Clara should drive (e.g. "book a demo", "capture a lead").
display_namestring–Business/display name shown in the widget chrome.
languagestring–"auto" detects from the visitor's browser, or pin a fixed language.
lead_destinationstring–Email address captured leads are sent to.
outbound_webhookstring–Optional webhook URL for lead notifications (Zapier/Make/etc.).
secret_keystring–The secret_key returned by create_trial_tenant, if your client can't send it as an "Authorization: Bearer <secret_key>" header instead.
site_urlstring–The site Clara is installed on.
voice_idstring–Voice for spoken replies (only honored on the Pro plan — safe to set now for after an upgrade).
widget_positionstring–Where the widget bubble docks.

No output schema declared.

No examples provided.

Common questions

What is the ClaraConverts MCP server?

ClaraConverts is an MCP server listed in the public MCP registry as com.claraconverts/clara. Provision and manage a ClaraConverts AI conversion-agent widget: pricing, trials, account setup. This page covers its hosted endpoint (https://claraconverts.com/mcp).

Is the ClaraConverts MCP server safe to use?

ClaraConverts 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 ClaraConverts MCP server expose?

ClaraConverts exposes 10 tools: get_pricing, list_integrations, create_trial_tenant, get_embed_snippet, get_tenant_settings, and 5 more. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.

Does the ClaraConverts MCP server require authentication?

No. We connected to ClaraConverts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ClaraConverts MCP server still maintained?

ClaraConverts is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.