# io.usefulapi/neon-crm (remote · neon-crm.usefulapi.io)

Search Neon CRM accounts, donations, memberships and events; create accounts and activities.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `neon-crm.usefulapi.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm.md), [page](https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm)

## Channel facts

- Endpoint: `https://neon-crm.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2698 tokens (~122/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 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 io.usefulapi/neon-crm MCP server?

io.usefulapi/neon-crm is a hosted endpoint at https://neon-crm.usefulapi.io/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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-neon-crm 'https://neon-crm.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-neon-crm": {
      "url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-neon-crm": {
      "type": "http",
      "url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-neon-crm]
url = "https://neon-crm.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-neon-crm": {
      "type": "remote",
      "url": "https://neon-crm.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-neon-crm --url 'https://neon-crm.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-neon-crm:
    url: "https://neon-crm.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-neon-crm": {
      "Transport": "http",
      "Url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-neon-crm -t streamable-http -u 'https://neon-crm.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-neon-crm": {
      "type": "http",
      "url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
```

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-10-02 (score 77, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Authorization: partial
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (22)

### `neon_get_organization_profile` (~52 tokens)

Get the organization profile

Fetch the Neon CRM organization these credentials belong to — its name, org ID and app URL. A cheap way to confirm the org ID and API key work. Neon: GET /properties/organizationProfile.

### `neon_list_accounts` (~131 tokens)

List accounts

List constituent accounts (individuals and companies), optionally filtered by email, first or last name, or type. Returns accountId, names, email and userType. For richer queries use neon_search. Neon: GET /accounts.

Input parameters:

- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `email` (string): Exact email address.
- `first_name` (string): First name.
- `last_name` (string): Last name.
- `page_size` (integer): Results per page.
- `user_type` (string): Account type.

### `neon_get_account` (~59 tokens)

Get one account

Fetch one account in full — returned as individualAccount or companyAccount with its primary contact, addresses, consent, custom fields, current membership status and timestamps. Neon: GET /accounts/{id}.

Input parameters:

- `account_id` (string, required): The account id.

### `neon_list_search_fields` (~98 tokens)

List search or output fields

Discover the field names neon_search accepts for a resource: kind=searchFields gives filterable fields with their allowed operators; kind=outputFields gives the columns you can return (standard field names plus custom fields with numeric ids). Call this before neon_search. Neon: GET /{resource}/search/searchFields or /outputFields.

Input parameters:

- `kind` (string, required): Filter fields or output columns.
- `resource` (string, required): Which record type.

### `neon_search` (~235 tokens)

Search records

Report-style search over accounts, donations (includes pledges and pledge payments), activities or events. Give filter criteria (field + operator + value), the output columns to return (standard field NAMES as strings, or custom-field IDS as integers — both from neon_list_search_fields), and 0-based pagination. Results come back as searchResults rows keyed by output field name, plus pagination totals. Neon allows only ONE concurrent search per endpoint. Neon: POST /{resource}/search.

Input parameters:

- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `output_fields` (array, required): Columns to return: standard field names (strings) and/or custom-field ids (integers). Max 300.
- `page_size` (integer): Results per page.
- `resource` (string, required): Which record type to search.
- `search_fields` (array, required): Filter criteria, ANDed together. Neon requires at least one.
- `sort_column` (string): Output field name to sort by — it must also appear in output_fields.
- `sort_direction` (string): Sort direction.

### `neon_list_account_donations` (~107 tokens)

List an account's donations

List one account's donations (amount, date, fund, campaign, purpose, status, payments), newest first by default. Neon: GET /accounts/{id}/donations.

Input parameters:

- `account_id` (string, required): The account id.
- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `sort_column` (string): Sort by date or amount.
- `sort_direction` (string): Sort direction.

### `neon_list_account_memberships` (~168 tokens)

List an account's memberships

List one account's membership history — level, term, start and end dates, fee, status (e.g. SUCCEEDED/FAILED) and auto-renewal. Filter to active or the primary active membership. Neon: GET /accounts/{id}/memberships.

Input parameters:

- `account_id` (string, required): The account id.
- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `is_active` (boolean): Only memberships matching the account's Active member flag.
- `page_size` (integer): Results per page.
- `primary_active_membership` (boolean): Only the highest-value active membership.
- `sort_column` (string): Sort by date or amount.
- `sort_direction` (string): Sort direction.

### `neon_list_account_event_registrations` (~99 tokens)

List an account's event registrations

List the event registrations one account has made, optionally for a single event. Neon: GET /accounts/{id}/eventRegistrations.

Input parameters:

- `account_id` (string, required): The account id.
- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `event_id` (string): Only registrations for this event.
- `sort_direction` (string): Sort direction.

### `neon_get_donation` (~56 tokens)

Get one donation

Fetch one donation — amount, date, fund, campaign, purpose, source, tribute, soft-credit solicitor, payments and status. Neon: GET /donations/{id}.

Input parameters:

- `donation_id` (string, required): The donation id.

### `neon_get_membership` (~55 tokens)

Get one membership

Fetch one membership — level, term, dates, fee, status, auto-renewal, sub-members and payments. Neon: GET /memberships/{membershipId}.

Input parameters:

- `membership_id` (string, required): The membership id.

### `neon_list_membership_levels` (~86 tokens)

List membership levels

List the organization's membership levels (id, code, description, rank, type, status). Neon: GET /memberships/levels.

Input parameters:

- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `page_size` (integer): Results per page.
- `status` (string): Only levels with this status.

### `neon_list_events` (~222 tokens)

List events

List events, filterable by name, category, date window, published or archived state. Dates are YYYY-MM-DD. Only Neon's legacy events are exposed by the API. Neon: GET /events.

Input parameters:

- `archived` (boolean): Only archived (true) or active (false) events.
- `current_page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `end_date_after` (string): Events ending after this date (YYYY-MM-DD).
- `end_date_before` (string): Events ending before this date (YYYY-MM-DD).
- `event_category` (string): Event category (a delimited list is allowed).
- `event_name` (string): Event name.
- `page_size` (integer): Results per page.
- `published_event` (boolean): Only published (true) or unpublished (false) events.
- `start_date_after` (string): Events starting after this date (YYYY-MM-DD).
- `start_date_before` (string): Events starting before this date (YYYY-MM-DD).

### `neon_get_event` (~51 tokens)

Get one event

Fetch one event — name, summary, dates, location, capacity, category, campaign, registration and financial settings. Neon: GET /events/{id}.

Input parameters:

- `event_id` (string, required): The event id.

### `neon_list_event_registrations` (~122 tokens)

List an event's registrations

List the registrations for one event — registrant account, tickets and attendees, amount, payments. Optionally only one registrant. Neon: GET /events/{id}/eventRegistrations.

Input parameters:

- `event_id` (string, required): The event id.
- `page` (integer): 0-based page number (Neon pages start at 0). Default 0.
- `page_size` (integer): Results per page.
- `registrant_account_id` (string): Only this registrant's registrations.
- `sort_direction` (string): Sort direction.

### `neon_list_campaigns` (~29 tokens)

List campaigns

List fundraising campaigns (id, code, name, status). Neon: GET /campaigns.

### `neon_get_campaign` (~52 tokens)

Get one campaign

Fetch one campaign — dates, goal, fund, purpose, parent campaign, status, page URLs and fundraising statistics. Neon: GET /campaigns/{id}.

Input parameters:

- `campaign_id` (string, required): The campaign id.

### `neon_get_activity` (~55 tokens)

Get one activity

Fetch one activity (a logged interaction or task) — subject, note, dates, linked accounts, assigned users, status and priority. Neon: GET /activities/{id}.

Input parameters:

- `activity_id` (string, required): The activity id.

### `neon_list_properties` (~84 tokens)

List lookup values

List one of the organization's lookup lists — the ids other tools need: funds, purposes, sources, solicitation methods, activity statuses and system time zones (for neon_create_activity), system users, individual and company types, event categories, countries, states/provinces, genders, prefixes. Neon: GET /properties/{name}.

Input parameters:

- `name` (string, required): Which lookup list.

### `neon_create_account` (~343 tokens)

Create an account

Create a constituent account: an INDIVIDUAL (a person) or a COMPANY (with company_name, plus an optional primary contact). Neon's Account Match may merge it into an existing account with the same name and email, so check neon_list_accounts by email first. Returns the new id. Neon: POST /accounts.

Input parameters:

- `address_line1` (string): Primary address, line 1.
- `address_line2` (string): Primary address, line 2.
- `city` (string): City.
- `company_name` (string): Company name — required when type is COMPANY.
- `country_id` (string): Country id (see neon_list_properties name=countries).
- `email` (string): Primary email (primaryContact.email1).
- `email2` (string): Secondary email (primaryContact.email2).
- `first_name` (string): First name (primaryContact.firstName).
- `job_title` (string): Job title (primaryContact.title).
- `last_name` (string): Last name.
- `middle_name` (string): Middle name.
- `no_solicitation` (boolean): Mark the account as do-not-solicit.
- `phone` (string): Phone number (stored on the primary address as phone1).
- `phone_type` (string): Phone type.
- `preferred_name` (string): Preferred name.
- `source_id` (string): Source id (see neon_list_properties name=sources).
- `state_province_code` (string): State/province code, e.g. CA.
- `type` (string, required): Individual person or company account.
- `zip_code` (string): ZIP / postal code.

### `neon_update_account` (~239 tokens)

Update an account

Change an account's name, email, job title, company name or do-not-solicit / email opt-out flags. Only the fields you pass are changed (PATCH). The type must match the account (see neon_get_account). Addresses are not edited here. Neon: PATCH /accounts/{id}.

Input parameters:

- `account_id` (string, required): The account id.
- `company_name` (string): New company name (COMPANY accounts only).
- `email` (string): Primary email (primaryContact.email1).
- `email2` (string): Secondary email (primaryContact.email2).
- `email_opt_out` (boolean): Opt the primary email out of email (email1OptOut).
- `first_name` (string): First name (primaryContact.firstName).
- `job_title` (string): Job title (primaryContact.title).
- `last_name` (string): Last name.
- `middle_name` (string): Middle name.
- `no_solicitation` (boolean): Do-not-solicit flag.
- `preferred_name` (string): Preferred name.
- `type` (string, required): The account's type (individualAccount vs companyAccount).

### `neon_create_activity` (~244 tokens)

Log an activity

Create an activity — log an interaction with a constituent (call, meeting, note) or schedule a task. Needs a subject, a start date, a time zone id (neon_list_properties name=systemTimezones), a status id (name=activityStatuses) and a priority; link it to accounts and assign it to system users. Returns the new id. Neon: POST /activities.

Input parameters:

- `account_ids` (array): Accounts this activity is about.
- `end_date` (string): End date, YYYY-MM-DD.
- `end_time` (string): End time.
- `note` (string): The body / notes.
- `priority` (string, required): Priority.
- `start_date` (string, required): Start date, YYYY-MM-DD.
- `start_time` (string): Start time, e.g. 09:30.
- `status_id` (string, required): Activity status id (neon_list_properties name=activityStatuses).
- `subject` (string, required): Short subject line.
- `system_user_ids` (array): System users it is assigned to.
- `time_zone_id` (string, required): Time zone id (neon_list_properties name=systemTimezones).

### `neon_update_activity` (~111 tokens)

Update an activity

Change an activity's subject, note, status (e.g. mark it completed) or priority. Only the fields you pass are changed (PATCH). Neon: PATCH /activities/{id}.

Input parameters:

- `activity_id` (string, required): The activity id.
- `note` (string): New note (replaces the old one).
- `priority` (string): New priority.
- `status_id` (string): New status id (neon_list_properties name=activityStatuses).
- `subject` (string): New subject.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm#diagnostics

## Score history

- 2026-10-03: 77
- 2026-10-02: 77
- 2026-10-01: 76
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/neon-crm MCP server?

io.usefulapi/neon-crm is an MCP server listed in the public MCP registry as io.usefulapi/neon-crm. Search Neon CRM accounts, donations, memberships and events; create accounts and activities. This page covers its hosted endpoint (https://neon-crm.usefulapi.io/mcp).

### Is the io.usefulapi/neon-crm MCP server safe to use?

io.usefulapi/neon-crm scores 77 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 io.usefulapi/neon-crm MCP server expose?

io.usefulapi/neon-crm exposes 22 tools: neon_get_organization_profile, neon_list_accounts, neon_get_account, neon_list_search_fields, neon_search, and 17 more. Their descriptions and schemas cost roughly 2,698 tokens of context every time the server is loaded.

### Does the io.usefulapi/neon-crm MCP server require authentication?

Yes. io.usefulapi/neon-crm asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/neon-crm MCP server still maintained?

io.usefulapi/neon-crm is still listed as active in the MCP registry. We last reached this channel on 3 October 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://neon-crm.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-neon-crm/neon-crm