Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Ptally is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Insurance pricing: build, validate and test rating models, then price quotes from your AI client.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ptally-mcp https://app.ptally.ai/mcp
# 2 — ask your agent for something these tools do
# get_docs, get_schema, validate_project and 7 more
Ptally costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PTAll 1 server
ptally1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ptally-mcp https://app.ptally.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | Documentation topic. "rules" for agent rules and constraints (start here). "readme" for full engine reference. |
Fetch the full JSON schema for Ptally project config files. Use to check exact field requirements, allowed step types, and property constraints.
No parameter schema on file.
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | object | no | — |
| project_gz | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Which starter example to return. |
| list | boolean | no | When true (or when type is omitted), return the catalog of available examples with their descriptions instead of a single project. |
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.
No parameter schema on file.
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, sta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_reference | string | yes | UUID of the project to fetch. |
| version_reference | string | no | 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. |
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 envel
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_reference | string | yes | UUID of the project to price against. |
| version_reference | string | no | Optional. Specific non-archived version UUID of this project; defaults to the latest live version (no fallback to drafts). |
| input | object | yes | Flat quote input object matching the project's input.format schema. Use get_project to discover the required keys. |
| source | string | no | Optional engine source label passed through to the model. Defaults to "mcp". |
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 eq
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version_reference | string | yes | UUID of the version whose tests to run — e.g. get_project's latest_draft.version_reference, or the version_reference patch_version returned. |
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 pa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version_reference | string | yes | UUID of the draft version to patch: get_project's latest_draft.version_reference. Never a published or approved version. |
| base_updated_at | string | yes | 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 | yes | RFC 6902 JSON Patch operations, applied in order to the full stored model, all or nothing. At most 200. |
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, late
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ptally or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 5 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestf3268dbe05bc61061aab3d28fd51a8da719c7bff8f32261099d1a0c00458991c
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_docs | untrusted-input | untrusted-input: keyword "fetch" |
| get_schema | untrusted-input | untrusted-input: keyword "fetch" |
| validate_project | no tags | |
| get_starter | untrusted-input | untrusted-input: keyword "fetch" |
| get_projects | no tags | |
| get_project | untrusted-input | untrusted-input: keyword "fetch" |
| run_quote | no tags | |
| run_version_tests | no tags | |
| patch_version | untrusted-inputstate-write | untrusted-input: keyword "download"; state-write: declares readOnlyHint: false |
| get_health | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestf3268dbe05bc6106
Scanned2026-11-05
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ptally can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.