com.giveradar/charity-registry
REMOTE · GIVERADAR.COM
Search, verify and compare 7.9M+ nonprofits from official charity registries in 100+ countries.
Available components
Last scanned (14 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1876 tokens (~34/item across 54 items; 4 tools + 50 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 4 Nov 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 3 Nov 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 2 Nov 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 1 Nov 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 31 Oct 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 30 Oct 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
- 29 Oct 26 0
- Resource “00” now points somewhere else: gr://charity/00-a19a46 → gr://charity/00-bp-1 security
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://giveradar.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=giveradar.com | CN=YE1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 603b84eaeca910b2098bcd3025790f1e69e |
| SANs: *.giveradar.com, giveradar.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of giveradar.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| giveradar.com. | DS published | 2371 | 13 | Verified |
| giveradar.com. | Verified address RRset verified with the apex keys |
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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google.com https://www.gstatic.com https://js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https:; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-src https://www.google.com https://js.stripe.com https://checkout.stripe.com https://www.youtube-nocookie.com https://www.youtube.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(self), usb=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://giveradar.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://giveradar.com/mcp/ | HTTPS enforced | 301 | https://giveradar.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 →
compare_charities Compare Charities ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | Charity slugs to compare (2-5). |
No output schema declared.
No examples provided.
find_similar Find Similar Charities ~66
Given one charity's slug, return up to `limit` other charities in the same country + category. Useful for 'find more like this' recommendations. Excludes the input charity from the result.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| slug | string | yes | Source charity slug. |
No output schema declared.
No examples provided.
search_charities Search Charities ~130
Search the charity registry by free-text name. Returns up to `limit` matches, each with slug, name, country, city/state, foundation_type, integrity_score, and the canonical page URL. Use this BEFORE resources/read when the user names a charity but you don't know its slug. The match is case-insensitive substring on the charity's name.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO 3166-1 alpha-2 country filter (e.g. 'ID', 'NL'). |
| limit | integer | – | – |
| query | string | yes | Name search query, 2+ chars. |
No output schema declared.
No examples provided.
verify_charity Verify Charity Registration ~112
Look up a charity by its official registry identifier - EIN (US), Charity Commission number (GB), RSIN (NL), AHU/Kemenkumham reg number (ID), or a generic registration_number for other countries. Returns the matched charity or null. Use this when the user provides a registry number and wants to confirm what's registered under it.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code. |
| id_value | string | yes | The registration / EIN / charity number. |
No output schema declared.
No examples provided.
How do I install the com.giveradar/charity-registry MCP server?
com.giveradar/charity-registry is a hosted endpoint at https://giveradar.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 · giveradar.com
claude mcp add --transport http com-giveradar-charity-registry 'https://giveradar.com/mcp/'
What is the com.giveradar/charity-registry MCP server?
com.giveradar/charity-registry is an MCP server listed in the public MCP registry as com.giveradar/charity-registry. Search, verify and compare 7.9M+ nonprofits from official charity registries in 100+ countries. This page covers its hosted endpoint (https://giveradar.com/mcp/).
Is the com.giveradar/charity-registry MCP server safe to use?
com.giveradar/charity-registry scores 86 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 com.giveradar/charity-registry MCP server expose?
com.giveradar/charity-registry exposes 4 tools: search_charities, compare_charities, find_similar, verify_charity. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.
Does the com.giveradar/charity-registry MCP server require authentication?
No. We connected to com.giveradar/charity-registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.giveradar/charity-registry MCP server still maintained?
com.giveradar/charity-registry 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 com.giveradar/charity-registry MCP server?
VerifyMCP ran 13 checks on com.giveradar/charity-registry, 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.