PulsyAI
REMOTE · MCP.UI-API.PULSEEM.COM · 2 COMPONENTS · SCANNED SEP 27
Send SMS, WhatsApp & email, manage contacts and campaigns, and pull reports via Pulseem.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 441 tokens (~147/item across 3 items; 3 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "call_pulseem_ui_api" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 3 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
How do I install the PulsyAI MCP server?
PulsyAI is a hosted endpoint at https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/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 · mcp.ui-api.pulseem.com
claude mcp add --transport http com-pulseem-pulsyai 'https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp'
{
"mcpServers": {
"com-pulseem-pulsyai": {
"url": "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp"
}
}
} {
"servers": {
"com-pulseem-pulsyai": {
"type": "http",
"url": "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp"
}
}
} [mcp_servers.com-pulseem-pulsyai] url = "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pulseem-pulsyai": {
"type": "remote",
"url": "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp",
"enabled": true
}
}
} openclaw mcp add com-pulseem-pulsyai --url 'https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp' --transport streamable-http
mcp_servers:
com-pulseem-pulsyai:
url: "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp" {
"McpServers": {
"com-pulseem-pulsyai": {
"Transport": "http",
"Url": "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp"
}
}
} assistant mcp add com-pulseem-pulsyai -t streamable-http -u 'https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp'
{
"mcpServers": {
"com-pulseem-pulsyai": {
"type": "http",
"url": "https://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/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.
- 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 27 Jul 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
- 26 Jul 26 0
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 27 Sept 2026 · Probed https://mcp.ui-api.pulseem.com/mcp_{token}/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=mcp.ui-api.pulseem.com | CN=YR1,O=Let's Encrypt,C=US | 15 Aug 2026 | 13 Nov 2026 | RSA 3072 | SHA256-RSA | 63866e9504fed162703aca11f1b5f12be0c |
| SANs: mcp.ui-api.pulseem.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 mcp.ui-api.pulseem.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pulseem.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://mcp.ui-api.pulseem.com/mcp_{token}/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ui-api.pulseem.com/mcp_%7Btoken%7D/mcp | Inconclusive | 404 |
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_pulseem_ui_api ~266
Executes any Pulseem UI API operation. BEFORE CALLING: Always call GetPulseemUiInstructions first. operationId (case-insensitive): CheckConnection [GET], CreateEmailCampaign [POST], CreateSmsCampaign [POST], AddClients [POST], GetClientsData [POST], AddClientProduct [POST], AddClientPageView [POST], GetAllGroups [POST], AddGroups [POST], GetStatistics [GET+pathParam], GetSubscribersCount [GET], GetAccountTotalSubscribers [GET], AddProduct [POST], GetSmsReport [POST], GetEmailReport [POST], GetEmailDetailReport [POST], GetCampaignReportByReceipients [POST] pathParamsJson — ONLY for GetStatistics: {"id":"<notificationId>"} For GET operations (CheckConnection, GetStatistics, GetSubscribersCount, GetAccountTotalSubscribers), payloadJson is ignored — pass {} for payloadJson.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | Operation name. Case-insensitive. |
| pathParamsJson | string | – | Path parameters as JSON — ONLY for GetStatistics: {"id":"<campaignId>"} |
| payloadJson | string | – | JSON body for POST requests. Use {} for operations with no body or GET operations. |
No output schema declared.
No examples provided.
get_pulseem_ui_instructions ~127
⚠️ ALWAYS call this tool FIRST before any other Pulseem UI tool. Returns: - All available operations and their required fields - Full JSON examples for CreateEmailCampaign, CreateSmsCampaign, AddClients, AddGroups - Report operations: GetEmailReport, GetEmailDetailReport, GetSmsReport, GetCampaignReportByReceipients - Client/product operations: GetClientsData, AddClientProduct, AddClientPageView, AddProduct - Statistics operations: GetStatistics, GetSubscribersCount, GetAccountTotalSubscribers - Authentication rules and error codes
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pulseem_ui_operations ~48
Returns live list of ALL available Pulseem UI operations (from the live Swagger spec). Use this ONLY if you need to verify exact operationIds before calling CallPulseemUiApi.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the PulsyAI MCP server?
PulsyAI is an MCP server listed in the public MCP registry as com.pulseem/pulsyai. Send SMS, WhatsApp & email, manage contacts and campaigns, and pull reports via Pulseem. This page covers its hosted endpoint (https://mcp.ui-api.pulseem.com/mcp_{token}/mcp).
Is the PulsyAI MCP server safe to use?
PulsyAI scores 71 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 PulsyAI MCP server expose?
PulsyAI exposes 3 tools: get_pulseem_ui_instructions, list_pulseem_ui_operations, call_pulseem_ui_api. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the PulsyAI MCP server require authentication?
No. We connected to PulsyAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PulsyAI MCP server still maintained?
PulsyAI is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.