PERSONAIZER
REMOTE · SESSIONS.PERSONAIZER.COM · SCANNED SEP 26
Free MCP API to create AI chat personas for websites — upload knowledge, search, and chat
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 Security63
- 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 5 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 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 638 tokens (~127/item across 5 items; 5 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 Management57
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 2 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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; "chat" implies "send" 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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the PERSONAIZER MCP server?
PERSONAIZER is a hosted endpoint at https://sessions.personaizer.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 · sessions.personaizer.com
claude mcp add --transport http personaizer-mcp 'https://sessions.personaizer.com/mcp'
{
"mcpServers": {
"personaizer-mcp": {
"url": "https://sessions.personaizer.com/mcp"
}
}
} {
"servers": {
"personaizer-mcp": {
"type": "http",
"url": "https://sessions.personaizer.com/mcp"
}
}
} [mcp_servers.personaizer-mcp] url = "https://sessions.personaizer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"personaizer-mcp": {
"type": "remote",
"url": "https://sessions.personaizer.com/mcp",
"enabled": true
}
}
} openclaw mcp add personaizer-mcp --url 'https://sessions.personaizer.com/mcp' --transport streamable-http
mcp_servers:
personaizer-mcp:
url: "https://sessions.personaizer.com/mcp" {
"McpServers": {
"personaizer-mcp": {
"Transport": "http",
"Url": "https://sessions.personaizer.com/mcp"
}
}
} assistant mcp add personaizer-mcp -t streamable-http -u 'https://sessions.personaizer.com/mcp'
{
"mcpServers": {
"personaizer-mcp": {
"type": "http",
"url": "https://sessions.personaizer.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.
- 26 Sept 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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
- 21 Sept 26 −6
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.0.0.0 ▼ security
- Tool “search_knowledge” was removed ▼ security
- Tool “chat” rewrote its description, which is the text the model reads security
- Tool “create_persona” rewrote its description, which is the text the model reads security
- Tool “upload_knowledge_docs” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “upload_knowledge_docs” added a required parameter “source”, so existing callers break ▼ functional
- “chat” made “personaId” required, so existing callers break ▼ functional
- “chat” changed the type of “personaId”: string|null → string ▼ functional
- New tool “upload_knowledge_text” functional
- “chat” reworded the description of “personaId” cosmetic
- “create_persona” reworded the description of “harvestContent” cosmetic
- “upload_knowledge_docs” reworded the description of “items” cosmetic
- 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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.
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 26 Sept 2026 · Probed https://sessions.personaizer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sessions.personaizer.com | CN=YR2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 69b40cf32d34c97a5d57524458248b62620 |
| SANs: sessions.personaizer.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 sessions.personaizer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| personaizer.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sessions.personaizer.com/mcp | Verified | 200 | |
| http (plaintext) | http://sessions.personaizer.com/mcp | HTTPS enforced | 308 | https://sessions.personaizer.com/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 →
chat ~102
Send a message to a PersonAIzer persona and get its reply, including any knowledge-base cards it surfaces. Requires your account API key and the persona_id to speak as.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The message to send. |
| personaId | string | yes | Which persona to chat with (its Persona ID). |
| sessionId | string|null | – | Continue an existing conversation by passing back the session_id from a previous chat call. Omit to start a new conversation. |
No output schema declared.
No examples provided.
check_persona_status ~46
Poll the status of a persona build started by create_persona. Requires an account-level API key.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The job_id returned by create_persona. |
No output schema declared.
No examples provided.
create_persona ~139
Start building a new PersonAIzer persona from a website URL — reads the site's brand facts, makes the brand, synthesizes the persona's identity and avatar, and (by default) crawls the site into the brand's knowledge; the persona and the crawl run in parallel. Asynchronous (~1 minute for the persona) — returns jobId, brandId and personaId; poll check_persona_status. Requires an account-level API key.
| Name | Type | Req | Description |
|---|---|---|---|
| harvestContent | boolean | – | Whether to crawl the site into the brand's knowledge alongside the persona build (default true). |
| websiteUrl | string | yes | The website URL to build the persona from. |
No output schema declared.
No examples provided.
upload_knowledge_docs ~157
Upsert up to 100 PRODUCTS (including services and unpriced catalog entries) into a knowledge source. For plain text (FAQs, policies, guides, articles, notes) use upload_knowledge_text instead. Requires your account API key; the source must exist (POST /v1/knowledge/sources).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | The products to upsert. Each needs title and categories (e.g. [["phones"]]); id, description, price, in_stock, attributes, variants, images and links are optional — see PersonAIzer's /v1/knowledge AP… |
| source | string | yes | The knowledge source the products belong to — its name, e.g. my-shop.ge. |
No output schema declared.
No examples provided.
upload_knowledge_text ~194
Add a piece of text — an FAQ, policy, guide, article or notes — to a knowledge source as a plain-text document. Uploading again with the same id replaces that document's text. For products (price, stock, attributes, variants) use upload_knowledge_docs. Requires your account API key and the source to write to; every persona speaking for that source's brand answers from it.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full text of the document. |
| id | string|null | – | Optional stable identifier. Uploading again with the same id replaces that document's text; omit it to create a new document. |
| source | string | yes | The knowledge source this belongs to — its name, e.g. my-shop.ge. |
| title | string | yes | Document title. |
| url | string|null | – | Optional URL where this content lives — shown as the document's link when the persona cites it. |
No output schema declared.
No examples provided.
What is the PERSONAIZER MCP server?
PERSONAIZER is an MCP server listed in the public MCP registry as io.github.PersonAIzer/mcp. Free MCP API to create AI chat personas for websites, upload knowledge, search, and chat. This page covers its hosted endpoint (https://sessions.personaizer.com/mcp).
Is the PERSONAIZER MCP server safe to use?
PERSONAIZER scores 74 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 PERSONAIZER MCP server expose?
PERSONAIZER exposes 5 tools: upload_knowledge_text, create_persona, chat, upload_knowledge_docs, check_persona_status. Their descriptions and schemas cost roughly 638 tokens of context every time the server is loaded.
Does the PERSONAIZER MCP server require authentication?
No. We connected to PERSONAIZER without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PERSONAIZER MCP server still maintained?
PERSONAIZER is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.