Productivity
grantreadinesschecklist.com
Assesses a nonprofit's preparedness for grant funding through structured evaluation.
ENDPOINT 1
https://grantreadinesschecklist.com/api/mcp
MCP server metadata
- Name
- grant-readiness-checklist
- Version
- 2.0.0
Call tools/call with name "assess_grant_readiness" and a JSON object of grant-readiness answers to receive a 0-100 readiness score, category breakdown, risk flags, a prioritized action plan and grant-packet guidance.
Known tools 1
assess_grant_readinessStructured decision-support tool that evaluates how prepared a nonprofit is to pursue grant funding.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.grant-readiness-checklist]
url = "https://grantreadinesschecklist.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"grant-readiness-checklist": {
"type": "http",
"url": "https://grantreadinesschecklist.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: grant-readiness-checklist
Remote MCP URL: https://grantreadinesschecklist.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"grant-readiness-checklist": {
"url": "https://grantreadinesschecklist.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"grant-readiness-checklist": {
"type": "http",
"url": "https://grantreadinesschecklist.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "grant-readiness-checklist",
"transport": "streamable-http",
"url": "https://grantreadinesschecklist.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.