io.github.gswardman/giveready
NPM · GIVEREADY-MCP
Search 41K+ nonprofits, get impact data, submit enrichments, donate USDC via x402.
Available components
Last scanned (23 hours ago)
Scores higher than 40% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 55 of 187 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 175 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability38
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1336 tokens (~222/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "donate_autonomous" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −2
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Security disclosure: unverified → fail ▼ 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 4 Nov 2026 · Analysed npm/giveready-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3gc7-fjrx-p6mg | CVE-2025-3194 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-hqr4-qq8f-hg3x | CVE-2026-104182 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-mjw6-4jj6-33hc | CVE-2026-104183 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 187 packages
| Packages resolved | 187 |
|---|---|
| Deprecated | 1 |
| Stale | 54 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
donate_autonomous ~532
Send a small USDC donation to a verified nonprofit on the GiveReady directory, signed and broadcast directly from this MCP server's configured Solana keypair via the x402 protocol. AUTHORISATION & SAFETY (read carefully — the user is trusting you with funds): - Only fires if the MCP server has SOLANA_PRIVATE_KEY set in its environment. Otherwise the tool throws a clear error and no transaction is built. - Hard caps: max $1 USDC per single call, max $5 USDC per day across all calls. The caps are enforced server-side; you cannot exceed them by retrying. - Wallet balance check happens before signing. If insufficient USDC, the tool fails fast. - Every successful donation appends a receipt to ~/.giveready/donations.log on the host machine. - The keypair MUST be a dedicated test wallet provisioned for this purpose, not the user's main wallet. The MCP user is responsible for that pre-commitment. WHAT THIS TOOL DOES: 1. Hits GET /api/donate/{slug}?amount=N — server returns HTTP 402 with payment requirements (recipient wallet, USDC mint, network). 2. Builds an SPL token transfer for the exact atomic amount, signs with the configured keypair. 3. POSTs the signed transaction back as the X-PAYMENT header. Server broadcasts to Solana mainnet via its own RPC, confirms, and writes to the donations table. 4. Returns the on-chain transaction hash and a Solscan link. WHEN TO USE: Use only when the user has clearly asked you to donate, named the recipient nonprofit (slug), and named an amount. Never default a donation. Never round up. If the user says "donate something" without an amount, ask for one before calling — this tool is not the place for guesses.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usdc | number | yes | Donation amount in USDC. Hard cap $1 per call, $5 per day. The user must have explicitly named this amount; never invent it. |
| confirm | boolean | yes | Pass true to confirm the user has explicitly authorised this exact donation. Refuse to set this if the user has not named the amount and recipient. |
| slug | string | yes | Verified-nonprofit slug (e.g., "finn-wardman-world-explorer-fund", "city-kids-surfing"). Must be a slug returned from search_nonprofits or known to have a usdc_wallet — endpoints without a wallet red… |
No output schema declared.
No examples provided.
get_nonprofit ~83
Get detailed information about a specific nonprofit including full description, programmes, impact metrics, registrations, and donation links. Use this when someone wants to learn more about a specific organisation before donating.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The nonprofit slug (e.g., "bridges-for-music", "the-wave-project", "finn-wardman-world-explorer-fund") |
No output schema declared.
No examples provided.
list_causes ~35
List all cause areas in the GiveReady directory. Use this to help someone explore what kinds of youth organisations are available before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_nonprofits ~295
Search 41,000+ verified nonprofits across 29 cause areas by keyword, cause, or country. Returns organisations with impact data and donation links. Use this when someone wants to find charities to support, discover mission-aligned programmes, or explore giving options. Cause IDs include: youth-empowerment, music-education, adventure-travel, mental-health, surf-therapy, entrepreneurship, poverty-reduction, creative-arts, education, community-development, peer-support, environment, health, animals, housing, food-security, disability, veterans, racial-justice, immigration, lgbtq, science-research, religion, gender-equality, refugees, sports-recreation, legal-justice, seniors, water-sanitation. Call list_causes for the live set with nonprofit counts. Countries: any country name (e.g. "South Africa", "United Kingdom", "United States", "Bermuda").
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | – | Cause area ID (e.g., "youth-empowerment", "music-education", "mental-health") |
| country | string | – | Country name (e.g., "South Africa", "United Kingdom") |
| ghd_aligned | boolean | – | Only show organisations in low/middle-income countries aligned with global health & development |
| query | string | – | Search keyword (e.g., "music education", "surf therapy", "adventure") |
No output schema declared.
No examples provided.
submit_enrichment ~385
Contribute missing data back to a nonprofit profile. Use this when get_nonprofit or search_nonprofits returns a profile with an empty high-value field and you have a well-sourced value to suggest. Auto-promotion rules (server-enforced): - STRUCTURED fields auto-promote when 2+ distinct agents submit the same normalised value. Fields: website, city, region, founded_year, contact_email. Submit canonical form — lowercase hostnames, no trailing slashes, lowercase emails, 4-digit year. - PROSE fields (mission, description, tagline) do NOT auto-promote yet — submissions queue for committee review. Still worth submitting; you get credit retroactively when review ships. - The server NEVER overwrites an existing non-empty value. Only empty fields can be promoted. Always provide a source_url that backs the value. Always pass a stable agent_id and a human-readable agent_name — these drive the public leaderboard at https://giveready.org/agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Stable identifier for your agent (e.g., "claude-3-5-sonnet-20250101", "my-enrichment-bot-v2"). |
| agent_name | string | yes | Human-readable name shown on the leaderboard (e.g., "Claude/3.5", "YourBot/1.0"). |
| field | string | yes | The field you are submitting data for. |
| slug | string | yes | The nonprofit slug (e.g., "bridges-for-music"). Get this from search_nonprofits or get_nonprofit. |
| source_url | string | yes | Public URL that supports the value (nonprofit website, news article, annual report, etc.). |
| value | string | yes | The value to submit. For structured fields, use canonical form. For founded_year, pass a 4-digit string. |
No output schema declared.
No examples provided.
How do I install the io.github.gswardman/giveready MCP server?
io.github.gswardman/giveready runs locally as an npm package, launched with npx -y giveready-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · giveready-mcp
claude mcp add gswardman-giveready -- npx -y giveready-mcp
What is the io.github.gswardman/giveready MCP server?
io.github.gswardman/giveready is an MCP server listed in the public MCP registry as io.github.gswardman/giveready. Search 41K+ nonprofits, get impact data, submit enrichments, donate USDC via x402. This page covers its npm package (giveready-mcp).
Is the io.github.gswardman/giveready MCP server safe to use?
io.github.gswardman/giveready scores 71 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.gswardman/giveready MCP server expose?
io.github.gswardman/giveready exposes 5 tools: search_nonprofits, get_nonprofit, list_causes, submit_enrichment, donate_autonomous. Their descriptions and schemas cost roughly 1,330 tokens of context every time the server is loaded.
Is the io.github.gswardman/giveready MCP server still maintained?
io.github.gswardman/giveready is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.gswardman/giveready MCP server under?
io.github.gswardman/giveready declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.