# 501c3.HELP nonprofit compliance (remote · mcp.501c3.help)

Nonprofit compliance rules for all 50 US states, each with its official citation and status

- Trust score: 73/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.501c3.help`: 73/100 (this document), [markdown](https://verifymcp.io/servers/help-501c3-compliance/mcp.md), [page](https://verifymcp.io/servers/help-501c3-compliance/mcp)

## Channel facts

- Endpoint: `https://mcp.501c3.help/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 389 tokens (~129/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 97/100
  - Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the 501c3.HELP nonprofit compliance MCP server?

501c3.HELP nonprofit compliance is a hosted endpoint at https://mcp.501c3.help/, 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.

### Claude

```bash
claude mcp add --transport http help-501c3-compliance 'https://mcp.501c3.help/'
```

### Cursor

```json
{
  "mcpServers": {
    "help-501c3-compliance": {
      "url": "https://mcp.501c3.help/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "help-501c3-compliance": {
      "type": "http",
      "url": "https://mcp.501c3.help/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.help-501c3-compliance]
url = "https://mcp.501c3.help/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "help-501c3-compliance": {
      "type": "remote",
      "url": "https://mcp.501c3.help/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add help-501c3-compliance --url 'https://mcp.501c3.help/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  help-501c3-compliance:
    url: "https://mcp.501c3.help/"
```

### Netclaw

```json
{
  "McpServers": {
    "help-501c3-compliance": {
      "Transport": "http",
      "Url": "https://mcp.501c3.help/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add help-501c3-compliance -t streamable-http -u 'https://mcp.501c3.help/'
```

### Other

```json
{
  "mcpServers": {
    "help-501c3-compliance": {
      "type": "http",
      "url": "https://mcp.501c3.help/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, −1)

- [functional] Stability: pass → 0.97

### 2026-10-31 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-10-29 (score 73, +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.

### 2026-10-27 (score 72, +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.

### 2026-10-24 (score 71, +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.

### 2026-10-22 (score 70, +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.

### 2026-10-20 (score 69, +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.

### 2026-10-18 (score 68, +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.

## MCP tools (3)

### `get_state_requirements` (~141 tokens)

Nonprofit compliance requirements for one US state, from 501c3.help's sourced records: formation, governance, charitable solicitation registration, reporting, tax and employment. Every record carries its official citation and a verification status. Records marked review_required are unsettled and must be presented as such, never as a settled rule. Optionally narrow by topic. Returns a limited number of records, not the whole state.

Input parameters:

- `state` (string, required): State name or two-letter abbreviation, for example 'Kansas' or 'KS'.
- `topic` (string): Optional topic filter, matched loosely, for example 'solicitation', 'reporting', 'tax'.

### `compare_states` (~116 tokens)

The same compliance topic across several US states, for deciding where to incorporate or for an organization that operates in more than one state. Each state's records carry their own citation and verification status; a record marked review_required is unsettled and must not be presented as a settled rule. Accepts up to eight states.

Input parameters:

- `states` (array, required): State names or two-letter abbreviations. Up to eight.
- `topic` (string, required): The topic to compare, for example 'solicitation', 'reporting', 'formation', 'tax'.

### `get_filing_deadlines` (~85 tokens)

Every 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. Use this for 'what is due and when'. Deadlines on records marked review_required are not settled and must be shown as unconfirmed.

Input parameters:

- `state` (string, required): State name or two-letter abbreviation.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/help-501c3-compliance/mcp#diagnostics

## Score history

- 2026-11-04: 73
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 71
- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 69
- 2026-10-20: 69
- 2026-10-19: 68
- 2026-10-18: 68
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 65
- 2026-10-12: 65
- 2026-10-10: 64
- 2026-10-08: 63
- 2026-10-06: 62
- 2026-10-04: 61
- 2026-10-03: 61
- 2026-10-02: 60

## Common questions

### What is the 501c3.HELP nonprofit compliance MCP server?

501c3.HELP nonprofit compliance is an MCP server listed in the public MCP registry as help.501c3/compliance. Nonprofit compliance rules for all 50 US states, each with its official citation and status. This page covers its hosted endpoint (https://mcp.501c3.help/).

### Is the 501c3.HELP nonprofit compliance MCP server safe to use?

501c3.HELP nonprofit compliance scores 73 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 501c3.HELP nonprofit compliance MCP server expose?

501c3.HELP nonprofit compliance exposes 3 tools: get_state_requirements, compare_states, get_filing_deadlines. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.

### Does the 501c3.HELP nonprofit compliance MCP server require authentication?

No. We connected to 501c3.HELP nonprofit compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 501c3.HELP nonprofit compliance MCP server still maintained?

501c3.HELP nonprofit compliance 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.

## Links

- Remote endpoint: https://mcp.501c3.help/
- Website: https://501c3.help/license/
- Changelog RSS feed: https://verifymcp.io/servers/help-501c3-compliance/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/help-501c3-compliance/mcp.json
- HTML version of this page: https://verifymcp.io/servers/help-501c3-compliance/mcp