# PERSONAIZER

> Free MCP API to create AI chat personas for websites — upload knowledge, search, and chat

- name: io.github.PersonAIzer/mcp
- version: 1.0.1
- connection class: R1 (autonomous)
- trust: 64/100 flags: unreachable
- quality: 83/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.PersonAIzer%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/io.github.PersonAIzer%2Fmcp/tools

**An agent can connect on its own if it already holds `X_API_KEY`, `X_API_KEY`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "PersonAIzer": {
      "type": "http",
      "url": "https://sessions.personaizer.com/mcp",
      "headers": {
        "X-Api-Key": "${X_API_KEY}",
        "Authorization": "${X_API_KEY}"
      }
    }
  }
}
```

Placeholders to fill: `${X_API_KEY}`, `${X_API_KEY}`.

## Trust

- hygiene: 100
- liveness: 0
- freshness: 85
- provenance: 90
- drivers: +repository +namespace-matches-repo +website -unreachable(7 failures) ~updated-60d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 83/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_persona_status (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); upload_knowledge_text (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_persona (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 849 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 849 tokens to load them all
- tool set hash: 7893b3219b0d3fdc86dd39c448728354
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.PersonAIzer/mcp.svg)](https://protogrid.dev/servers/io.github.PersonAIzer/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://sessions.personaizer.com/mcp (streamable-http, auth api_key ${X_API_KEY}, reachable false, uptime30d 0.8695652)

## Packages

_none_

## Tools (5)

- `chat`: 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.
- `check_persona_status`: Poll the status of a persona build started by create_persona. Requires an account-level API key.
- `create_persona`: 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.
- `upload_knowledge_docs`: 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).
- `upload_knowledge_text`: 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.