Databases
501c3.help
Provides 501(c)(3) nonprofit compliance requirements, filing deadlines, and multi-state comparisons by US state.
ENDPOINT 1
https://mcp.501c3.help
MCP server metadata
- Name
- 501c3help-compliance
- Version
- 0.1.0
US nonprofit compliance requirements for all fifty states, sourced to official government citations. Always show the citation and the verification status alongside any requirement you repeat. Data licence and free API keys: https://501c3.help/license/
Known tools 3
get_state_requirementsNonprofit compliance requirements for one US state, from 501c3.
Inferred read-onlycompare_statesThe same compliance topic across several US states, for deciding where to incorporate or for an organization that operates in more than one state.
Inferred read-onlyget_filing_deadlinesEvery requirement in one US state that has a filing deadline attached, with the deadline in plain words, the form or portal, the fee, and the official citation.
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.501c3help-compliance]
url = "https://mcp.501c3.help"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"501c3help-compliance": {
"type": "http",
"url": "https://mcp.501c3.help"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: 501c3help-compliance
Remote MCP URL: https://mcp.501c3.help
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": {
"501c3help-compliance": {
"url": "https://mcp.501c3.help"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"501c3help-compliance": {
"type": "http",
"url": "https://mcp.501c3.help"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "501c3help-compliance",
"transport": "streamable-http",
"url": "https://mcp.501c3.help"
}
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.