# Policy Pal (remote · api.policypal.link)

Grounded, quoted readings of privacy policies and terms of service. Not legal advice.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.policypal.link`: 69/100 (this document), [markdown](https://verifymcp.io/servers/link-policypal-policypal/api.md), [page](https://verifymcp.io/servers/link-policypal-policypal/api)

## Channel facts

- Endpoint: `https://api.policypal.link/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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 921 tokens (~307/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Policy Pal MCP server?

Policy Pal is a hosted endpoint at https://api.policypal.link/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 link-policypal-policypal 'https://api.policypal.link/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "link-policypal-policypal": {
      "url": "https://api.policypal.link/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "link-policypal-policypal": {
      "type": "http",
      "url": "https://api.policypal.link/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.link-policypal-policypal]
url = "https://api.policypal.link/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add link-policypal-policypal --url 'https://api.policypal.link/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  link-policypal-policypal:
    url: "https://api.policypal.link/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "link-policypal-policypal": {
      "Transport": "http",
      "Url": "https://api.policypal.link/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add link-policypal-policypal -t streamable-http -u 'https://api.policypal.link/mcp'
```

### Other

```json
{
  "mcpServers": {
    "link-policypal-policypal": {
      "type": "http",
      "url": "https://api.policypal.link/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 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 67, +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.

### 2026-10-30 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `check_policy` (~307 tokens)

Check one policy

Read one privacy policy or terms-of-service page and return a grounded verdict, eight fixed yes/no/partly/not-stated answers, and up to five findings, each with a verbatim quote from the document.

Use this instead of fetching and reading the page yourself. A policy page is 20,000-60,000 tokens of context, and many are rendered by JavaScript so a plain fetch returns an empty shell without saying so. This returns about 1,000 tokens: a 20-60x saving with a quote behind every claim.

Guarantees: every claim carries a verbatim sentence from that document, and a question the document does not address is answered not_stated -- never as a promise the document did not make. The eight questions are identical across services, so two reports can be set side by side.

A report may be served from an earlier reading of the same document, which is what makes it cheap and instant. readAt says when that reading was taken; call policy_changes_since if it matters whether anything has moved since.

Do not use this for a document that is not a legal agreement; it is refused, and a refusal costs nothing. Do not use it to summarise a page in general, to read a document the user pasted rather than published at a URL, or for legal advice: Automated reading of one document. Not legal advice.

Input parameters:

- `url` (string, required): The https address of the published policy page itself, not the service homepage.

### `compare_policies` (~260 tokens)

Compare services

Answer the same eight fixed questions across two to five services at once, so their policies can actually be compared.

Use this instead of reading each document yourself. Doing it yourself needs N full reads and a rubric you have to keep consistent between them; the questions here are fixed, so a difference in the answers is a difference in the policies rather than a difference in how you read them. Each answer also carries how common that answer is across every comparable document Policy Pal has read.

Guarantees: identical questions, a verbatim quote behind every stated answer, not_stated where a document is silent, and not_asked where that kind of document was never asked that question -- a silence is never invented to fill a table. A service whose report is not comparable, or that there was no time to read, is reported as such rather than filled in.

Do not use this for one service -- call check_policy. Do not expect a score or a ranking: Policy Pal publishes qualitative verdicts and refuses to reduce a policy to a number. Automated reading of one document. Not legal advice.

Input parameters:

- `urls` (array, required): Two to five https addresses of published policy pages. Compare documents of the same kind: a privacy policy and a terms page answer different questions.

### `policy_changes_since` (~229 tokens)

What changed since

Say what changed in a service's policy since a date, expressed as changes to the eight fixed answers.

You cannot do this yourself at any context size: it needs the earlier version of the document, and the earlier version is gone from the web. Policy Pal keeps the eight answers for every version it has read, so the difference is a fact rather than a reconstruction.

It reports answer changes -- for example forced arbitration moving from no to yes -- and not text edits. A changed comma is noise; a changed answer is the thing worth telling someone about.

Returns nothing to report when the answers are unchanged, and says so explicitly when it has no reading from before that date rather than guessing. A question the earlier reading did not answer is reported as not compared, never as not_stated. Automated reading of one document. Not legal advice.

Input parameters:

- `since` (string, required): The date you last looked, as YYYY-MM-DD or an ISO timestamp. The answer is the difference between what was true then and what is true now.
- `url` (string, required): The https address of the published policy page.

## Diagnostics

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

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 61
- 2026-10-19: 61
- 2026-10-18: 60
- 2026-10-17: 60
- 2026-10-16: 59
- 2026-10-15: 59
- 2026-10-14: 58
- 2026-10-13: 58
- 2026-10-12: 57
- 2026-10-10: 57

## Common questions

### What is the Policy Pal MCP server?

Policy Pal is an MCP server listed in the public MCP registry as link.policypal/policypal. Grounded, quoted readings of privacy policies and terms of service. Not legal advice. This page covers its hosted endpoint (https://api.policypal.link/mcp).

### Is the Policy Pal MCP server safe to use?

Policy Pal scores 69 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 Policy Pal MCP server expose?

Policy Pal exposes 3 tools: check_policy, compare_policies, policy_changes_since. Their descriptions and schemas cost roughly 796 tokens of context every time the server is loaded.

### Does the Policy Pal MCP server require authentication?

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

### Is the Policy Pal MCP server still maintained?

Policy Pal 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://api.policypal.link/mcp
- Website: https://policypal.link/bot
- Changelog RSS feed: https://verifymcp.io/servers/link-policypal-policypal/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/link-policypal-policypal/api.json
- HTML version of this page: https://verifymcp.io/servers/link-policypal-policypal/api