Community Funding NZ
REMOTE · FUNDING.ALLTOOHUMAN.NZ
Search 380+ New Zealand community grant funders, deadlines and application questions. No login.
Available components
Last scanned (18 hours ago)
Scores higher than 84% 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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability83
- 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 787 tokens (~98/item across 8 items; 8 tools + 0 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 Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 +1
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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://funding.alltoohuman.nz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=funding.alltoohuman.nz | CN=YE2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 384 | ECDSA-SHA384 | 643cc33d4e3db8113fedc38736655d2201e |
| SANs: funding.alltoohuman.nz | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 insecure
Validation of funding.alltoohuman.nz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| nz. | DS published | 38240, 62081 | 8, 8 | Verified |
| alltoohuman.nz. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://funding.alltoohuman.nz/mcp | Verified | 200 | |
| http (plaintext) | http://funding.alltoohuman.nz/mcp | Inconclusive | 405 |
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 →
flag_funder_detail Flag a wrong funder detail ~77
Report that a field on a funder profile is wrong or out of date, with the correction. Reviewed by All Too Human before any change is applied.
| Name | Type | Req | Description |
|---|---|---|---|
| correction | string | yes | What the correct value is, and where you saw it if possible |
| field | string | yes | – |
| funder_slug | string | yes | – |
No output schema declared.
No examples provided.
get_funder Get full funder profile ~72
Full profile for one funder by slug: what they prioritise, language tips, common mistakes, success factors, required documents, application sections, the extracted application form questions, and upcoming funding rounds. Use this before preparing or drafting an application.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Funder slug from search_funders |
No output schema declared.
No examples provided.
list_filters List valid search filters ~39
Returns the exact region slugs, organisation type values and difficulty levels accepted by search_funders. Call this first if you are unsure which value to use.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
report_outcome Report an application outcome ~111
Tell us how an application to a funder went. Outcomes are stored for All Too Human to analyse which funders say yes and are never published as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_received | integer | – | Whole NZ dollars received, if funded |
| funder_slug | string | yes | – |
| notes | string | – | Anything useful: what they asked for, timing, feedback received |
| outcome | string | yes | approved = funded in full, partial = funded less than asked, declined, waiting = no decision yet |
No output schema declared.
No examples provided.
rounds_closing_soon Funding rounds closing soon ~86
Funding rounds whose closing date falls within the next N days (default 30, max 180), soonest first. Optional region filter (slug from list_filters). Dates are New Zealand dates. Always confirm the date on the funder's own site before relying on it.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| region | string | – | – |
No output schema declared.
No examples provided.
rounds_opening_soon Funding rounds opening soon ~94
Funding rounds whose opening date falls within the next N days (default 60, max 180), soonest first. Optional region filter (slug from list_filters). Useful for planning applications ahead of time. Dates are New Zealand dates. Always confirm the date on the funder's own site before relying on it.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| region | string | – | – |
No output schema declared.
No examples provided.
search_funders Search grant funders ~195
Search New Zealand community grant funders. Returns up to 25 compact rows per call with a total count; use offset to page. Combine filters: region (slug from list_filters), org_type, purpose keywords, max_amount in NZD, difficulty. Use get_funder for the full profile of a result.
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | string | – | – |
| limit | integer | – | – |
| max_amount | integer | – | Only funders whose minimum grant is at or below this NZD amount |
| offset | integer | – | – |
| org_type | string | – | Applicant organisation type, e.g. charitable_trust |
| purpose | string | – | Keyword matched against eligible purposes and priorities, e.g. youth, environment, marae |
| query | string | – | Free text matched against funder name and description |
| region | string | – | Region slug, e.g. tasman. Funders tagged national always match. |
No output schema declared.
No examples provided.
suggest_funder Suggest a missing funder ~113
Suggest a New Zealand grant funder that is not in the database. All Too Human researches and reviews suggestions before adding them. Check search_funders first to avoid duplicates. Documentation: https://www.alltoohuman.nz/grants/connect
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| notes | string | – | What they fund, who is eligible, deadlines, anything you know |
| region | string | – | Region slug if the funder is regional |
| url | string | – | The funder's website or funding page |
No output schema declared.
No examples provided.
How do I install the Community Funding NZ MCP server?
Community Funding NZ is a hosted endpoint at https://funding.alltoohuman.nz/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 · funding.alltoohuman.nz
claude mcp add --transport http navtejdhillon-grants 'https://funding.alltoohuman.nz/mcp'
What is the Community Funding NZ MCP server?
Community Funding NZ is an MCP server listed in the public MCP registry as io.github.NavtejDhillon/grants. Search 380+ New Zealand community grant funders, deadlines and application questions. No login. This page covers its hosted endpoint (https://funding.alltoohuman.nz/mcp).
Is the Community Funding NZ MCP server safe to use?
Community Funding NZ scores 81 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 Community Funding NZ MCP server expose?
Community Funding NZ exposes 8 tools: list_filters, search_funders, get_funder, rounds_closing_soon, rounds_opening_soon, and 3 more. Their descriptions and schemas cost roughly 787 tokens of context every time the server is loaded.
Does the Community Funding NZ MCP server require authentication?
No. We connected to Community Funding NZ without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Community Funding NZ MCP server still maintained?
Community Funding NZ 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 Community Funding NZ MCP server?
VerifyMCP ran 12 checks on Community Funding NZ, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Community Funding NZ: HTTPS. 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.