# Legacy (remote · donate.givewithlegacy.com)

Give to UK registered charities: check charity numbers, price a gift and get a checkout link.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `donate.givewithlegacy.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-givewithlegacy-donate/donate.md), [page](https://verifymcp.io/servers/com-givewithlegacy-donate/donate)

## Channel facts

- Endpoint: `https://donate.givewithlegacy.com/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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 (good).
  - Tool/resource definitions use about 380 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Legacy is a hosted endpoint at https://donate.givewithlegacy.com/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 com-givewithlegacy-donate 'https://donate.givewithlegacy.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-givewithlegacy-donate": {
      "url": "https://donate.givewithlegacy.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-givewithlegacy-donate": {
      "type": "http",
      "url": "https://donate.givewithlegacy.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-givewithlegacy-donate]
url = "https://donate.givewithlegacy.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-givewithlegacy-donate --url 'https://donate.givewithlegacy.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-givewithlegacy-donate:
    url: "https://donate.givewithlegacy.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-givewithlegacy-donate": {
      "Transport": "http",
      "Url": "https://donate.givewithlegacy.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-givewithlegacy-donate -t streamable-http -u 'https://donate.givewithlegacy.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-givewithlegacy-donate": {
      "type": "http",
      "url": "https://donate.givewithlegacy.com/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-04 (score 80, +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-11-02 (score 79, +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-31 (score 78, +1)

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

### 2026-10-29 (score 77, +1)

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

### 2026-10-28 (score 76, 0)

- [functional] Server version: 0dfd954 → 4c987c5

### 2026-10-27 (score 76, 0)

- [functional] Server version: 9744d13 → 0dfd954

### 2026-10-26 (score 76, +1)

- [functional] Server version: 95b343c-dirty → 9744d13

### 2026-10-25 (score 75, 0)

- [functional] Server version: f632066 → 95b343c-dirty

## MCP tools (3)

### `check_charities` (~54 tokens)

Check charities

Look up UK registered charities by charity number and say which can take a gift through Legacy. Gives our name for each number, so you can confirm it is the charity the donor meant.

Input parameters:

- `charityNumbers` (array, required)

Output parameters:

- `charities` (array)

### `quote` (~104 tokens)

Price a gift

What a gift to these charities comes to: what the donor pays, the payment processing fee, each charity’s share and, if asked, the Gift Aid they could claim. The donor chooses Gift Aid and any tip at checkout, so these are assumptions.

Input parameters:

- `charities` (array, required)
- `giftAid` (boolean): Whether to show Gift Aid, which only a UK taxpayer can add
- `tipPercentage` (number): An optional tip to Legacy, taken from the gift

Output parameters:

- `charities` (array)
- `charitiesReceive` (number)
- `donorPays` (number)
- `giftAid` (number)
- `maximumTotal` (number|null)
- `minimumPerCharity` (number)
- `minimumTotal` (number)
- `paymentProcessing` (number)
- `platformTip` (number)

### `create_checkout_link` (~61 tokens)

Create a checkout link

A link to Legacy’s checkout with these charities, and the amounts when given. The donor opens it to give their details, answer Gift Aid, choose an optional tip and pay by card; the amounts stay theirs to change.

Input parameters:

- `charities` (array, required)

Output parameters:

- `charities` (array)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70

## Common questions

### What is the Legacy MCP server?

Legacy is an MCP server listed in the public MCP registry as com.givewithlegacy/donate. Give to UK registered charities: check charity numbers, price a gift and get a checkout link. This page covers its hosted endpoint (https://donate.givewithlegacy.com/mcp).

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

Legacy scores 80 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 Legacy MCP server expose?

Legacy exposes 3 tools: check_charities, quote, create_checkout_link. Their descriptions and schemas cost roughly 219 tokens of context every time the server is loaded.

### Does the Legacy MCP server require authentication?

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

### Is the Legacy MCP server still maintained?

Legacy 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.

### What did VerifyMCP test on the Legacy MCP server?

VerifyMCP ran 13 checks on Legacy, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://donate.givewithlegacy.com/mcp
- Website: https://donate.givewithlegacy.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-givewithlegacy-donate/donate.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-givewithlegacy-donate/donate/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-givewithlegacy-donate/donate.json
- HTML version of this page: https://verifymcp.io/servers/com-givewithlegacy-donate/donate