PersuadioAI
REMOTE · API.PERSUADIOAI.COM · SCANNED AUG 3
Analyze leads, draft follow-up campaigns, and launch SMS outreach only with explicit human approval.
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 →
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, 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1261 tokens (~157/item across 8 items; 8 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.persuadioai.com
claude mcp add --transport http com-persuadioai-mcp https://api.persuadioai.com/mcp
[mcp_servers.com-persuadioai-mcp] url = "https://api.persuadioai.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-persuadioai-mcp": {
"type": "remote",
"url": "https://api.persuadioai.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-persuadioai-mcp --url https://api.persuadioai.com/mcp --transport streamable-http
mcp_servers:
com-persuadioai-mcp:
url: "https://api.persuadioai.com/mcp" {
"mcpServers": {
"com-persuadioai-mcp": {
"type": "http",
"url": "https://api.persuadioai.com/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.
- 3 Aug 26 75
First indexed and scored.
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 3 Aug 2026 · Probed https://api.persuadioai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=persuadioai.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 10 Jun 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 5f873bdaf6ff9daf27716529cedfafe |
| SANs: persuadioai.com, *.persuadioai.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
DNSSEC insecure
Validation of api.persuadioai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| persuadioai.com. | absent | 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 error="invalid_token", error_description="Authentication required", resource_metadata="https://api.persuadioai.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", error_description="Authentication required", resource_metadata="https://api.persuadioai.com/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://api.persuadioai.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.persuadioai.com/mcp |
| Authorisation server | https://dev-j28v1bnr0o00f4g6.us.auth0.com/ |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.persuadioai.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.persuadioai.com/mcp | HTTPS enforced | 301 | https://api.persuadioai.com:443/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.
analyze_lead_source Analyze lead source ~92
Summarise the leads in an account or one campaign: how many exist, how many can actually be contacted, how many opted out, and how they break down by status and source. Read-only — sends nothing and changes nothing. Start here when the operator asks what they have to work with.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | — | Limit to one campaign. Omit to cover every campaign this account owns. |
No output schema declared.
No examples provided.
create_campaign_draft Create a campaign draft ~195
Create a campaign in draft status with its opening SMS. THIS SENDS NOTHING — a draft cannot deliver a message. It exists so a human can read the exact wording and audience before deciding. The message is rejected if it implies a prior relationship or manufactures urgency. After this, call review_campaign_readiness.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Context for the operator: who this targets and why. |
| idempotency_key | string | — | Repeat a retried call safely — the same key returns the same campaign. |
| lead_ids | array | — | Existing leads to move into this campaign. Ids outside this account are ignored. |
| message | string | yes | The opening SMS, 320 characters or fewer. Say who is writing and why. Do not imply a prior conversation or a deadline. An opt-out line is appended automatically on first contact. |
| name | string | yes | A name the operator will recognise in their dashboard. |
No output schema declared.
No examples provided.
get_campaign_status Get campaign status ~133
Report what a campaign has actually done: leads, messages delivered, replies, opt-outs, meetings scheduled, and threads waiting on a human. Omit campaign_id to list every campaign in the account. Read-only. The response includes caveats about which numbers may lag — read them before telling the operator a campaign is or is not working.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | — | One campaign. Omit to list all of them. |
| limit | integer | — | — |
| offset | integer | — | — |
| status | string | — | Filter the list by status, e.g. 'active', 'draft', 'paused'. |
No output schema declared.
No examples provided.
get_interested_leads Get leads who replied with interest ~117
List leads whose replies were classified as positive or as asking a question, newest first, with the reply text. The classifier is keyword and sentiment based, NOT a language model — the response says so explicitly, and the reply text is included so you can judge for yourself. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | — | Limit to one campaign. |
| days | integer | — | How far back to look, in days (1-365). Default 30. |
| limit | integer | — | — |
| offset | integer | — | — |
No output schema declared.
No examples provided.
launch_approved_campaign Launch an approved campaign ~179
SENDS REAL MESSAGES TO REAL PEOPLE. This is irreversible and costs credits. It requires an approval_token from review_campaign_readiness AND the confirmation phrase that review returned, which the HUMAN OPERATOR must give you explicitly. Never generate the confirmation yourself, never infer approval from a previous message, and never reuse an approval issued for a different campaign or a different size. If the operator has not clearly said yes to this exact launch, do not call this tool — ask them.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_token | string | yes | The token from review_campaign_readiness. Single-use and short-lived. |
| campaign_id | string | yes | The campaign to launch. |
| confirmation | string | yes | The exact confirmation phrase from the readiness review, as given to you by the human operator. |
| lead_ids | array | — | Must match the subset that was reviewed and approved. |
No output schema declared.
No examples provided.
pause_campaign Pause a campaign ~85
Stop a campaign from sending anything further. Queued messages that have not yet gone out are skipped; anything already handed to the carrier cannot be recalled. Safe to call when unsure — pausing is reversible and errs toward not contacting people.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign to pause. |
| reason | string | — | Why it is being paused, for the operator's records. |
No output schema declared.
No examples provided.
recommend_followup_campaign Recommend a follow-up campaign ~107
Propose how to follow up, based on which leads have never been contacted, were contacted without replying, or already replied. Returns segments with counts and a suggested approach for each. Read-only — this is a proposal to discuss with the operator, not a plan that has been put into effect.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | — | Limit to one campaign. Omit to cover the whole account. |
| goal | string | — | What the operator is trying to achieve, in their words. |
No output schema declared.
No examples provided.
review_campaign_readiness Review campaign readiness ~128
Pre-flight a campaign: how many people would be contacted, on which channels, what it would cost, and which checks pass, warn or fail. SENDS NOTHING. If everything passes, it returns a short-lived approval token and a confirmation phrase — both of which a human operator must authorise before launch_approved_campaign will do anything. Run this before every launch; the token is single-use and campaign-specific.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | The campaign to review. |
| lead_ids | array | — | Review a subset of the campaign's leads. Omit for all of them. |
No output schema declared.
No examples provided.