# Ptally (remote · app.ptally.ai)

Insurance pricing: build, validate and test rating models, then price quotes from your AI client.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `app.ptally.ai`: 70/100 (this document), [markdown](https://verifymcp.io/servers/ai-ptally-ptally/app.md), [page](https://verifymcp.io/servers/ai-ptally-ptally/app)

## Channel facts

- Endpoint: `https://app.ptally.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4611 tokens (~461/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Ptally MCP server?

Ptally is a hosted endpoint at https://app.ptally.ai/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.

### Claude

```bash
claude mcp add --transport http ai-ptally-ptally 'https://app.ptally.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-ptally-ptally": {
      "url": "https://app.ptally.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-ptally-ptally": {
      "type": "http",
      "url": "https://app.ptally.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-ptally-ptally]
url = "https://app.ptally.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-ptally-ptally": {
      "type": "remote",
      "url": "https://app.ptally.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-ptally-ptally --url 'https://app.ptally.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-ptally-ptally:
    url: "https://app.ptally.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-ptally-ptally": {
      "Transport": "http",
      "Url": "https://app.ptally.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-ptally-ptally -t streamable-http -u 'https://app.ptally.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-ptally-ptally": {
      "type": "http",
      "url": "https://app.ptally.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 69)

First indexed and scored.

## MCP tools (10)

### `get_docs` (~109 tokens)

Guides

Fetch Ptally documentation by topic. Call BEFORE building or editing a config to load the rules and reference material you need. Topics: "rules" = agent rules, constraints, expression syntax, quality gates, and debugging guidance (start here); "readme" = full engine reference with step types, query language, input/output blocks, and code examples.

Input parameters:

- `topic` (string, required): Documentation topic. "rules" for agent rules and constraints (start here). "readme" for full engine reference.

### `get_schema` (~35 tokens)

Model layout

Fetch the full JSON schema for Ptally project config files. Use to check exact field requirements, allowed step types, and property constraints.

### `validate_project` (~186 tokens)

Check a model for mistakes

Server-side schema validation of a project config. Returns { valid: true/false, errors: [...] } with the JSON path, keyword, and message for each issue. Prefer local validation against get_schema during authoring; use this as a ground-truth check, including on an amended model before handing it back to the user as a file. Pass exactly one of inline `project` or a base64-gzipped `project_gz` (if the inline form is too large for your client); passing neither or both returns an error result.

Input parameters:

- `project` (object)
- `project_gz` (string): Optional. Base64-encoded gzip of the project JSON, used as an alternative to inline `project` when the caller cannot fit the full payload in a single tool argument. Mutually exclusive with `project`.…

### `get_starter` (~124 tokens)

Example models

Fetch a worked-example Ptally project for a common line of business. Each example is a small, fully valid project with realistic collection tables, calculations, exclusions and refers, plus an embedded tests[] suite for reference. Use as a template — copy and adapt rather than authoring from scratch. Pass no arguments (or `list: true`) to get the catalog.

Input parameters:

- `list` (boolean): When true (or when type is omitted), return the catalog of available examples with their descriptions instead of a single project.
- `type` (string): Which starter example to return.

### `get_projects` (~61 tokens)

List projects

List every project stored on this self-host instance. Returns `{ count, projects: [{ project_reference, name, description }] }`. Descriptions are truncated to 100 characters so the response stays compact — call get_project for the full record. Archived projects are excluded.

### `get_project` (~397 tokens)

See a project

Fetch a project by `project_reference` from the self-host store. Optional `version_reference` pins to a specific version of that project (a version from another project is a tool error); otherwise the latest live (published or approved) version is used, or the latest non-archived version of any status if none is live. Returns `{ project_reference, version_reference, version, name, description, status, summary, created_at, updated_at, project_url, version_url, latest_draft, clipped_collections, next_steps, model }`. The model is a summary for reading, never a file to hand back. Every `collection` step is stamped with `__context` (`total_rows`, `shown_rows`, `columns`, `shape`, `truncated`, `patchable`; an empty table gets `total_rows: 0`, `columns: []`, `patchable: true`): tables of up to 100 rows are shown whole and can be changed with patch_version; bigger ones are clipped, listed in `clipped_collections`, and can only change by the user downloading the model from `version_url`, you amending it, and the user uploading it. `latest_draft` is the newest draft version (null if none) — patches go there, so call get_project again with its version_reference before patching. Follow `next_steps` and tell the user which route applies before making changes. All other model content — input.format, steps, expressions, output — is returned verbatim so an LLM caller can understand what the project does and how to build a valid input payload. Precursor to run_quote and patch_version.

Input parameters:

- `project_reference` (string, required): UUID of the project to fetch.
- `version_reference` (string): Optional. Specific version UUID of this project; defaults to the latest live version, or the latest non-archived version of any status if none are live.

### `run_quote` (~254 tokens)

Try a quote

Dry-run a quote against a stored project. Takes `project_reference`, an optional `version_reference` (defaults to the latest live version; there is no fallback to drafts, so pass `version_reference` to price one — it must belong to the project and not be archived, else a tool error), and an `input` payload that matches the project's input schema. Runs the pricing engine and returns the quote envelope — `output`, `result`, `valid`, `status`, `error`, the engine's `errors` log, `exec_time_ms`, `dry_run: true` and a null `quote_reference` — WITHOUT persisting a quotes row. Call get_project first to inspect `input.format` and build a valid input.

Input parameters:

- `input` (object, required): Flat quote input object matching the project's input.format schema. Use get_project to discover the required keys.
- `project_reference` (string, required): UUID of the project to price against.
- `source` (string): Optional engine `source` label passed through to the model. Defaults to "mcp".
- `version_reference` (string): Optional. Specific non-archived version UUID of this project; defaults to the latest live version (no fallback to drafts).

### `run_version_tests` (~330 tokens)

Run a version's tests

Price every test in a version's tests[] against that version's stored model and compare each with its expected output. Takes `version_reference` (any status but archived — a draft after patch_version, or a live version for a baseline). Runs against the stored model, so a patch saved a moment ago is included. A test passes when its result is within 0.005 of the expected result and its valid flag equals the expected valid. Expectations are read from output { result, valid }, or, when output has neither (tests imported from the hosted service), from result { result, valid }; `expected_from` says which. A test with neither is priced but unchecked (passed: null). Returns `{ project_reference, version_reference, version, status, updated_at, total, passed, failed, unchecked, results: [{ id, name, passed, expected: { result, valid }, expected_from, actual: { result, valid }, problems, errors }], version_url, next_steps }` — `problems` says why a test failed, `errors` is up to 5 of the engine's step errors for that run. Nothing is persisted. Use after patch_version, after adding or changing tests, or before a change to record the baseline. To change a test's expected output, patch_version on /tests/<test id>/output/result (drafts only) — output takes precedence over result.

Input parameters:

- `version_reference` (string, required): UUID of the version whose tests to run — e.g. get_project's latest_draft.version_reference, or the version_reference patch_version returned.

### `patch_version` (~1057 tokens)

Edit a draft

Change a DRAFT version's stored model with an RFC 6902 JSON Patch, merged on the server. Use it for targeted edits; any change to a clipped collection (__context.patchable: false) goes through download and upload instead (see next_steps in get_project).

BEFORE CALLING
1\. The version must be a draft: use get_project's latest_draft. If it is null, ask the user to click New Version on the project page (it copies the live model), then call get_project again.
2\. Call get_project with the draft's version_reference and build every path from that response. Pass its updated_at as base_updated_at.
3\. Tell the user what you will change (old → new) and get their go-ahead.

PATHS (JSON Pointer)
\- Name steps, tests and other id'd array elements by id (else key) instead of index: /steps/<step id>/... and /tests/<test id>/... Ids survive other steps being inserted or removed in the same patch.
\- Model layout: /meta/..., /input/format/<input key>/... (format is an object keyed by input key), /steps/<id>/..., /output/format/<key>/..., /tests/<id>/...
\- Collection rows by index. Compressed collection ([[col1, col2, ...], [v1, v2, ...], ...]): index 0 is the header row, so the first data row is /collection/1, and a cell is /collection/<row>/<column index>. Uncompressed collection (array of row objects): the first row is /collection/0, and a cell is /collection/<row>/<column name>. Check __context.shape and __context.columns.
\- Append with "-" (/steps/-, /steps/<id>/collection/-). Insert at a numeric index; step order is execution order, so a new step goes after the steps whose outputs it reads.
\- Escape "~" as ~0 and "/" as ~1 inside a segment.

EXAMPLES
\- Change a rate cell: {"op":"replace","path":"/steps/region_rates/collection/1/1","value":4.5}
\- Guard then change: [{"op":"test","path":"/steps/base_premium/formula","value":"<current formula>"},{"op":"replace","path":"/steps/base_premium/formula","value":"<new formula>"}]
\- Add a table row: {"op":"add","path":"/steps/type_factors/c…

Input parameters:

- `base_updated_at` (string, required): The draft's updated_at exactly as get_project (called with this version_reference) or the previous patch returned it. A mismatch means someone changed the draft since — the patch is refused.
- `operations` (array, required): RFC 6902 JSON Patch operations, applied in order to the full stored model, all or nothing. At most 200.
- `version_reference` (string, required): UUID of the draft version to patch: get_project's latest_draft.version_reference. Never a published or approved version.

### `get_health` (~105 tokens)

Health check

Diagnostic snapshot of the deployed MCP server plus a live probe of its store (sqlite or Postgres). Returns server name and version, protocol version, root, boot time, advertised tool names and count, a hash of the tool surface, and `store` — `{ ok, latency_ms, counts: { projects, quotes } }` from counting rows in the projects table (one row per version) and the quotes table, or `{ ok: false, latency_ms, error }`.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-ptally-ptally/app#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 69

## Common questions

### What is the Ptally MCP server?

Ptally is an MCP server listed in the public MCP registry as ai.ptally/ptally. Insurance pricing: build, validate and test rating models, then price quotes from your AI client. This page covers its hosted endpoint (https://app.ptally.ai/mcp).

### Is the Ptally MCP server safe to use?

Ptally scores 70 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 Ptally MCP server expose?

Ptally exposes 10 tools: get_docs, get_schema, validate_project, get_starter, get_projects, and 5 more. Their descriptions and schemas cost roughly 2,658 tokens of context every time the server is loaded.

### Does the Ptally MCP server require authentication?

No. We connected to Ptally without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Ptally MCP server still maintained?

Ptally is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.ptally.ai/mcp
- Website: https://ptally.ai/developer/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-ptally-ptally/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-ptally-ptally/app.json
- HTML version of this page: https://verifymcp.io/servers/ai-ptally-ptally/app