All servers · Government & law · Markets & trading
Policy Pal
link.policypal/policypal · v1.0.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | experimental, tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Grounded, quoted readings of privacy policies and terms of service. Not legal advice.
Connect
streamable-http · https://api.policypal.link/mcp
claude mcp add --transport http policypal https://api.policypal.link/mcp{
"mcpServers": {
"policypal": {
"url": "https://api.policypal.link/mcp"
}
}
}Tools as reported by the server
check_policyRead 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 cocompare_policiesAnswer 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 dipolicy_changes_sinceSay 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 h
Website · JSON · Text for agents · Registry updated 2026-10-09