← All servers

PersuadioAI

warnings

api.persuadioai.com

Analyze leads, draft follow-up campaigns, and launch SMS outreach only with explicit human approval.

https://api.persuadioai.com/mcpWebsiteOAuthMCP 2025-11-25v1.3.0last checked 24 Aug 2026spoke MCP on 3 of 3 checks (30 days)initialize in 409 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme
OAuth
Issuer
https://dev-j28v1bnr0o00f4g6.us.auth0.com/
Dynamic client registration
Advertised (RFC 7591)
Client ID Metadata Document
Not advertised
PKCE
S256, plain
Grant types
client_credentials, authorization_code, refresh_token, password, implicit, urn:ietf:params:oauth:grant-type:device_code, urn:ietf:params:oauth:grant-type:token-exchange, http://auth0.com/oauth/grant-type/password-realm, http://auth0.com/oauth/grant-type/passwordless/otp, http://auth0.com/oauth/grant-type/mfa-oob, http://auth0.com/oauth/grant-type/mfa-otp, http://auth0.com/oauth/grant-type/mfa-recovery-code, urn:ietf:params:oauth:grant-type:jwt-bearer
Scopes
openid, profile, offline_access, name, given_name, family_name, nickname, email, email_verified, picture, created_at, identities, phone, address
Protected-resource metadata
Published (RFC 9728)
Anonymous access
Handshake succeeds; 18 tools listable
Credentials demanded in prose
add_leads_to_campaign, create_lead, import_leads_from_file

These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

Documentation
https://persuadioai.com

What the probe found

warningTools needing credentials are listed without a challenge

3 of the 18 tools listed anonymously say in their own descriptions that they need an account or a key (add_leads_to_campaign, create_lead, import_leads_from_file), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

18 tools usable without signing in

The server exposes a public surface before authorization: add_leads_to_campaign, analyze_lead_source, clone_campaign_draft, create_campaign_draft, create_lead, find_lead, get_campaign_status, get_interested_leads, import_leads_from_file, launch_approved_campaign, list_from_addresses, list_leads, pause_campaign, preview_lead_import, recommend_followup_campaign, review_campaign_readiness, search_leads, select_and_attach_leads.

Tools

add_leads_to_campaignanalyze_lead_sourceclone_campaign_draftcreate_campaign_draftcreate_leadfind_leadget_campaign_statusget_interested_leadsimport_leads_from_filelaunch_approved_campaignlist_from_addresseslist_leadspause_campaignpreview_lead_importrecommend_followup_campaignreview_campaign_readinesssearch_leadsselect_and_attach_leads

Contract history

24 Aug 2026v1.3.03 compatible1 cosmeticinstructions rewritten

Instructions rewritten: add_leads_to_campaign, list_leads. The description an agent follows changed; the callable contract may not have.

24 Aug 2026v1.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

MCP status badge for PersuadioAI
[![MCP status](https://mcpi.app/servers/persuadioai/badge.svg)](https://mcpi.app/servers/persuadioai)

Own this server?

Sign in to claim this listing by proving control of the endpoint.