Legacy
REMOTE · DONATE.GIVEWITHLEGACY.COM
Give to UK registered charities: check charity numbers, price a gift and get a checkout link.
Available components
Last scanned (9 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 380 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 0
- Server version: 0dfd954 → 4c987c5 functional
- 27 Oct 26 0
- Server version: 9744d13 → 0dfd954 functional
- 26 Oct 26 +1
- Server version: 95b343c-dirty → 9744d13 functional
- 25 Oct 26 0
- Server version: f632066 → 95b343c-dirty functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://donate.givewithlegacy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=givewithlegacy.com | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1baa372248b7ae230e4d480c60189596 |
| SANs: givewithlegacy.com, donate.givewithlegacy.com, *.donate.givewithlegacy.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of donate.givewithlegacy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| givewithlegacy.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://donate.givewithlegacy.com/mcp | Verified | 200 | |
| http (plaintext) | http://donate.givewithlegacy.com/mcp | HTTPS enforced | 301 | https://donate.givewithlegacy.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_charities Check charities ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| charityNumbers | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| charities | array | yes | – |
No examples provided.
create_checkout_link Create a checkout link ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| charities | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| charities | array | yes | – |
| url | string | yes | – |
No examples provided.
quote Price a gift ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| charities | array | yes | – |
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| charities | array | yes | – |
| charitiesReceive | number | yes | – |
| donorPays | number | yes | – |
| giftAid | number | yes | – |
| maximumTotal | number|null | yes | – |
| minimumPerCharity | number | yes | – |
| minimumTotal | number | yes | – |
| paymentProcessing | number | yes | – |
| platformTip | number | yes | – |
No examples provided.
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.
remote · donate.givewithlegacy.com
claude mcp add --transport http com-givewithlegacy-donate 'https://donate.givewithlegacy.com/mcp'
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.