# compare_charities

Side-by-side comparison of 2-5 charities by slug. Returns their integrity scores, program/admin/fundraising ratios, annual revenue, founding year, foundation type, and a deterministic verdict on which has the strongest transparency signal. Use this when the user wants to choose between named charities.

Agent View of the PolicyLayer registry record for `compare_charities`. HTML page: https://policylayer.com/tools/com-giveradar-charity-registry/compare-charities

## Facts

- Tool: `compare_charities`
- Server: Charity Registry (`https://giveradar.com/mcp/`) — https://policylayer.com/tools/com-giveradar-charity-registry.md
- Homepage: https://github.com/matt-timmermans/giveradar-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `slugs` | array | yes | Charity slugs to compare (2-5). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compare_charities",
    "arguments": {
      "slugs": []
    }
  }
}
```

## Why compare_charities is rated Low

This tool retrieves and presents comparative information about charities from a read-only registry. It queries existing data and synthesizes it for user comparison, with no capability to modify, delete, or execute external actions. The deterministic verdict is analytical output, not a state-changing operation.

From the tool's own definition: "Tool description specifies 'side-by-side comparison' and 'returns' data (integrity scores, ratios, revenue, founding year, foundation type, transparency signal). No mutations, deletions, or external operations are performed."

Risk signals: Admin/system-level operation

## Use case

AI agents call compare_charities to retrieve information from Charity Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Charity Registry:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_charities": {}
  }
}
```

## Other tools on Charity Registry (3)

- `find_similar` — Read — https://policylayer.com/tools/com-giveradar-charity-registry/find-similar.md
- `search_charities` — Read — https://policylayer.com/tools/com-giveradar-charity-registry/search-charities.md
- `verify_charity` — Read — https://policylayer.com/tools/com-giveradar-charity-registry/verify-charity.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-giveradar-charity-registry · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-giveradar-charity-registry