The Grant Readiness Checklist | The Document Pro
REMOTE · GRANTREADINESSCHECKLIST.COM
Assess your nonprofit's grant readiness with The Grant Readiness Checklist by the Nonprofit Lau
Available components
Last scanned (19 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability49
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1017 tokens (~1017/item across 1 items; 1 tools + 0 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 2 Nov 26 −4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “assess_grant_readiness” rewrote its description, which is the text the model reads security
- Schema quality: 267 → 1017 ▼ functional
- Schema quality: excellent → good functional
- Server version: 2.0.0 → 3.0.0 functional
- “assess_grant_readiness” added an optional parameter “B1” cosmetic
- “assess_grant_readiness” added an optional parameter “B2” cosmetic
- “assess_grant_readiness” added an optional parameter “B3” cosmetic
- “assess_grant_readiness” added an optional parameter “B4” cosmetic
- “assess_grant_readiness” added an optional parameter “B5” cosmetic
- “assess_grant_readiness” added an optional parameter “B6” cosmetic
- “assess_grant_readiness” added an optional parameter “B7” cosmetic
- “assess_grant_readiness” added an optional parameter “B8” cosmetic
- “assess_grant_readiness” added an optional parameter “B9” cosmetic
- “assess_grant_readiness” added an optional parameter “C1” cosmetic
- “assess_grant_readiness” added an optional parameter “C2” cosmetic
- “assess_grant_readiness” added an optional parameter “C3” cosmetic
- “assess_grant_readiness” added an optional parameter “C4” cosmetic
- “assess_grant_readiness” added an optional parameter “C5” cosmetic
- “assess_grant_readiness” added an optional parameter “C6” cosmetic
- “assess_grant_readiness” added an optional parameter “F1” cosmetic
- “assess_grant_readiness” added an optional parameter “F2” cosmetic
- “assess_grant_readiness” added an optional parameter “F3” cosmetic
- “assess_grant_readiness” added an optional parameter “F4” cosmetic
- “assess_grant_readiness” added an optional parameter “G1” cosmetic
- “assess_grant_readiness” added an optional parameter “G1a” cosmetic
- “assess_grant_readiness” added an optional parameter “G2” cosmetic
- “assess_grant_readiness” added an optional parameter “G3” cosmetic
- “assess_grant_readiness” added an optional parameter “P1” cosmetic
- “assess_grant_readiness” added an optional parameter “P2” cosmetic
- “assess_grant_readiness” added an optional parameter “P3” cosmetic
- “assess_grant_readiness” added an optional parameter “P4” cosmetic
- “assess_grant_readiness” added an optional parameter “P5” cosmetic
- “assess_grant_readiness” added an optional parameter “P6” cosmetic
- “assess_grant_readiness” added an optional parameter “P7” cosmetic
- “assess_grant_readiness” added an optional parameter “P8” cosmetic
- “assess_grant_readiness” added an optional parameter “T1” cosmetic
- “assess_grant_readiness” added an optional parameter “T2” cosmetic
- “assess_grant_readiness” added an optional parameter “T3” cosmetic
- “assess_grant_readiness” added an optional parameter “T4” cosmetic
- “assess_grant_readiness” added an optional parameter “T5” cosmetic
- “assess_grant_readiness” added an optional parameter “T6” cosmetic
- “assess_grant_readiness” added an optional parameter “answers” cosmetic
- “assess_grant_readiness” added an optional parameter “engine_version” cosmetic
- “assess_grant_readiness” reworded the description of “financials” cosmetic
- “assess_grant_readiness” reworded the description of “governance” cosmetic
- “assess_grant_readiness” reworded the description of “org_background” cosmetic
- “assess_grant_readiness” reworded the description of “policies” cosmetic
- “assess_grant_readiness” reworded the description of “program_project” cosmetic
- “assess_grant_readiness” reworded the description of “supporting_docs” cosmetic
- “assess_grant_readiness” reworded the description of “tax_registrations” cosmetic
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Sept 26 0
First indexed and scored.
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 · Probed https://grantreadinesschecklist.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=grantreadinesschecklist.com | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f072226c071a87af132ba82c089351a4 |
| SANs: grantreadinesschecklist.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 grantreadinesschecklist.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| grantreadinesschecklist.com. | absent | 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://grantreadinesschecklist.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://grantreadinesschecklist.com/api/mcp | HTTPS enforced | 301 | https://grantreadinesschecklist.com/api/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 →
assess_grant_readiness Grant Readiness Assessment ~888
Grant readiness check for nonprofits. Default (engine v3): about 36 Yes / In progress / No questions across six sections (Governance, Tax and registrations, Financials, Organizational background, Program or project, Policies). Returns a readiness bar per section with "[x] ready, [y] in progress, [z] missing", up to four biggest gaps with a short expert answer, and a getting-started result when the organization has no bylaws and no Articles of Incorporation. Unanswered or "not_sure" items are reported as Not answered and excluded from the math (missing data is not the same as No). No overall score in v3. The legacy 91-field scan (0-100 score) remains available with engine_version "2".
| Name | Type | Req | Description |
|---|---|---|---|
| B1 | string | – | Organizational background: A written mission statement |
| B2 | string | – | Organizational background: A written organization description |
| B3 | string | – | Organizational background: A defined target population |
| B4 | string | – | Organizational background: Service area |
| B5 | string | – | Organizational background: Current programs and services written down |
| B6 | string | – | Organizational background: People served each year |
| B7 | string | – | Organizational background: Full-time employees |
| B8 | string | – | Organizational background: Part-time employees |
| B9 | string | – | Organizational background: Volunteers |
| C1 | string | – | Policies: Conflict of interest policy |
| C2 | string | – | Policies: Anti-discrimination policy |
| C3 | string | – | Policies: Anti-harassment policy |
| C4 | string | – | Policies: Financial management policy |
| C5 | string | – | Policies: Gift acceptance policy |
| C6 | string | – | Policies: Social media policy |
| F1 | string | – | Financials: Organizational budget |
| F2 | string | – | Financials: Detailed organizational budget |
| F3 | string | – | Financials: Most recent audit, review or compilation report |
| F4 | string | – | Financials: Program budget |
| G1 | string | – | Governance: Does your organization have bylaws? |
| G1a | string | – | Governance: Have you filed Articles of Incorporation? |
| G2 | string | – | Governance: A board of at least 3 members |
| G3 | string | – | Governance: An organization chart |
| P1 | string | – | Program or project: Problem, need and case statement |
| P2 | string | – | Program or project: Program or project description |
| P3 | string | – | Program or project: Program target population |
| P4 | string | – | Program or project: Number served each year, tracked for this program |
| P5 | string | – | Program or project: Goals and objectives |
| P6 | string | – | Program or project: Methodology and activities |
| P7 | string | – | Program or project: Outcomes |
| P8 | string | – | Program or project: Work plan |
| T1 | string | – | Tax and registrations: Articles of Incorporation |
| T2 | string | – | Tax and registrations: Federal tax-exempt letter (IRS determination letter) |
| T3 | string | – | Tax and registrations: State tax-exempt letter |
| T4 | string | – | Tax and registrations: Which IRS return did you file most recently? |
| T5 | string | – | Tax and registrations: Which California FTB return did you file most recently? |
| T6 | string | – | Tax and registrations: Registered with SAM.gov, with a UEI number |
| answers | object | – | – |
| engine_version | string | – | Defaults to "3". |
| financials | object | – | Legacy v2 only: answers for Financials. |
| governance | object | – | Legacy v2 only: answers for Governance. |
| org_background | object | – | Legacy v2 only: answers for Organizational Background. |
| policies | object | – | Legacy v2 only: answers for Policies. |
| program_project | object | – | Legacy v2 only: answers for Program/Project Fit. |
| supporting_docs | object | – | Legacy v2 only: answers for Supporting Documents. |
| tax_registrations | object | – | Legacy v2 only: answers for Tax & Registrations. |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | v2 only. |
| context | array | – | – |
| engine | string | yes | – |
| gaps | array | – | – |
| gettingStarted | object|null | – | – |
| limitations | array | yes | – |
| routedOut | boolean | – | – |
| score | integer | – | v2 only. |
| sections | array | – | v3: one entry per section with ready / inProgress / missing / notAnswered / percent / summary. |
| totals | object | – | – |
| version | string | yes | – |
No examples provided.
How do I install the The Grant Readiness Checklist | The Document Pro MCP server?
The Grant Readiness Checklist | The Document Pro is a hosted endpoint at https://grantreadinesschecklist.com/api/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 · grantreadinesschecklist.com
claude mcp add --transport http janoliverautomation-stack-grantreadinesschecklis 'https://grantreadinesschecklist.com/api/mcp'
What is the The Grant Readiness Checklist | The Document Pro MCP server?
The Grant Readiness Checklist | The Document Pro is an MCP server listed in the public MCP registry as io.github.janoliverautomation-stack/grantreadinesschecklist…. Assess your nonprofit's grant readiness with The Grant Readiness Checklist by the Nonprofit Lau. This page covers its hosted endpoint (https://grantreadinesschecklist.com/api/mcp).
Is the The Grant Readiness Checklist | The Document Pro MCP server safe to use?
The Grant Readiness Checklist | The Document Pro scores 79 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 The Grant Readiness Checklist | The Document Pro MCP server expose?
The Grant Readiness Checklist | The Document Pro exposes 1 tool: assess_grant_readiness. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.
Does the The Grant Readiness Checklist | The Document Pro MCP server require authentication?
No. We connected to The Grant Readiness Checklist | The Document Pro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The Grant Readiness Checklist | The Document Pro MCP server still maintained?
The Grant Readiness Checklist | The Document Pro 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.