_ registry / mcp streamable-http · checked 34m ago

501c3help-compliance

https://mcp.501c3.help

Registry code: 9f5c4512aac27591

api record

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/

endpoint
https://mcp.501c3.help/
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is 501c3help-compliance live?
Yes — it answered the hub's last check (checked 34m ago). It answered 98% of checks over the last 30 days.
Is 501c3help-compliance free to use?
Yes — the hub reached it with no key and no payment.
What tools does 501c3help-compliance have?
3 tools: get_filing_deadlines, compare_states, get_state_requirements.
Is 501c3help-compliance safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.4%

90 days 98.9%· all time 98.9%

latency
320ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 281 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • get nonprofit compliance requirements for a state
  • list nonprofit filing deadlines
  • compare nonprofit rules across states
takes → gives
text → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_filing_deadlines reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "description": "State name or two-letter abbreviation."
        }
      }
    }
    arguments 12 lines
  • compare_states reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "states",
        "topic"
      ],
      "properties": {
        "topic": {
          "type": "string",
          "description": "The topic to compare, for example 'solicitation', 'reporting', 'formation', 'tax'."
        },
        "states": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "State names or two-letter abbreviations. Up to eight."
        }
      }
    }
    arguments 20 lines
  • get_state_requirements reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "state"
      ],
      "properties": {
        "state": {
          "type": "string",
          "description": "State name or two-letter abbreviation, for example 'Kansas' or 'KS'."
        },
        "topic": {
          "type": "string",
          "description": "Optional topic filter, matched loosely, for example 'solicitation', 'reporting', 'tax'."
        }
      }
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9f5c4512aac27591.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9f5c4512aac27591/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9f5c4512aac27591/badge.svg)](https://brick.blue/agent/9f5c4512aac27591?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.