Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/neon-crm

REMOTE · NEON-CRM.USEFULAPI.IO · SCANNED OCT 3

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

77 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · neon-crm.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-neon-crm 'https://neon-crm.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-neon-crm": {
      "url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-neon-crm": {
      "type": "http",
      "url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-neon-crm --url 'https://neon-crm.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-neon-crm:
    url: "https://neon-crm.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-neon-crm": {
      "Transport": "http",
      "Url": "https://neon-crm.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-neon-crm -t streamable-http -u 'https://neon-crm.usefulapi.io/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Oct 26 +1
    • Server version: 1.3.0 → 1.5.1 functional
  • 1 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.3.0 functional
  • 30 Sept 26 +53
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Authorization: partial security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • 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 functional
  • 29 Sept 26 18

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Oct 2026 · Probed https://neon-crm.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of neon-crm.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://neon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://neon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://neon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://neon-crm.usefulapi.io/mcp
Authorisation server https://neon-crm.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://neon-crm.usefulapi.io/mcp Verified 200
http (plaintext) http://neon-crm.usefulapi.io/mcp HTTPS enforced 301 https://neon-crm.usefulapi.io/mcp
MCP tools · 22 exposed · ~2,698 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
neon_create_account ~343

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.

NameTypeReqDescription
address_line1string–Primary address, line 1.
address_line2string–Primary address, line 2.
citystring–City.
company_namestring–Company name — required when type is COMPANY.
country_idstring–Country id (see neon_list_properties name=countries).
emailstring–Primary email (primaryContact.email1).
email2string–Secondary email (primaryContact.email2).
first_namestring–First name (primaryContact.firstName).
job_titlestring–Job title (primaryContact.title).
last_namestring–Last name.
middle_namestring–Middle name.
no_solicitationboolean–Mark the account as do-not-solicit.
phonestring–Phone number (stored on the primary address as phone1).
phone_typestring–Phone type.
preferred_namestring–Preferred name.
source_idstring–Source id (see neon_list_properties name=sources).
state_province_codestring–State/province code, e.g. CA.
typestringyesIndividual person or company account.
zip_codestring–ZIP / postal code.

No output schema declared.

No examples provided.

neon_create_activity ~244

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.

NameTypeReqDescription
account_idsarray–Accounts this activity is about.
end_datestring–End date, YYYY-MM-DD.
end_timestring–End time.
notestring–The body / notes.
prioritystringyesPriority.
start_datestringyesStart date, YYYY-MM-DD.
start_timestring–Start time, e.g. 09:30.
status_idstringyesActivity status id (neon_list_properties name=activityStatuses).
subjectstringyesShort subject line.
system_user_idsarray–System users it is assigned to.
time_zone_idstringyesTime zone id (neon_list_properties name=systemTimezones).

No output schema declared.

No examples provided.

neon_get_account ~59

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}.

NameTypeReqDescription
account_idstringyesThe account id.

No output schema declared.

No examples provided.

neon_get_activity ~55

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

NameTypeReqDescription
activity_idstringyesThe activity id.

No output schema declared.

No examples provided.

neon_get_campaign ~52

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

NameTypeReqDescription
campaign_idstringyesThe campaign id.

No output schema declared.

No examples provided.

neon_get_donation ~56

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

NameTypeReqDescription
donation_idstringyesThe donation id.

No output schema declared.

No examples provided.

neon_get_event ~51

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

NameTypeReqDescription
event_idstringyesThe event id.

No output schema declared.

No examples provided.

neon_get_membership ~55

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

NameTypeReqDescription
membership_idstringyesThe membership id.

No output schema declared.

No examples provided.

neon_get_organization_profile ~52

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

neon_list_account_donations ~107

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

NameTypeReqDescription
account_idstringyesThe account id.
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
sort_columnstring–Sort by date or amount.
sort_directionstring–Sort direction.

No output schema declared.

No examples provided.

neon_list_account_event_registrations ~99

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

NameTypeReqDescription
account_idstringyesThe account id.
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
event_idstring–Only registrations for this event.
sort_directionstring–Sort direction.

No output schema declared.

No examples provided.

neon_list_account_memberships ~168

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.

NameTypeReqDescription
account_idstringyesThe account id.
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
is_activeboolean–Only memberships matching the account's Active member flag.
page_sizeinteger–Results per page.
primary_active_membershipboolean–Only the highest-value active membership.
sort_columnstring–Sort by date or amount.
sort_directionstring–Sort direction.

No output schema declared.

No examples provided.

neon_list_accounts ~131

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.

NameTypeReqDescription
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
emailstring–Exact email address.
first_namestring–First name.
last_namestring–Last name.
page_sizeinteger–Results per page.
user_typestring–Account type.

No output schema declared.

No examples provided.

neon_list_campaigns ~29

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

neon_list_event_registrations ~122

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

NameTypeReqDescription
event_idstringyesThe event id.
pageinteger–0-based page number (Neon pages start at 0). Default 0.
page_sizeinteger–Results per page.
registrant_account_idstring–Only this registrant's registrations.
sort_directionstring–Sort direction.

No output schema declared.

No examples provided.

neon_list_events ~222

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.

NameTypeReqDescription
archivedboolean–Only archived (true) or active (false) events.
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
end_date_afterstring–Events ending after this date (YYYY-MM-DD).
end_date_beforestring–Events ending before this date (YYYY-MM-DD).
event_categorystring–Event category (a delimited list is allowed).
event_namestring–Event name.
page_sizeinteger–Results per page.
published_eventboolean–Only published (true) or unpublished (false) events.
start_date_afterstring–Events starting after this date (YYYY-MM-DD).
start_date_beforestring–Events starting before this date (YYYY-MM-DD).

No output schema declared.

No examples provided.

neon_list_membership_levels ~86

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

NameTypeReqDescription
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
page_sizeinteger–Results per page.
statusstring–Only levels with this status.

No output schema declared.

No examples provided.

neon_list_properties ~84

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}.

NameTypeReqDescription
namestringyesWhich lookup list.

No output schema declared.

No examples provided.

neon_list_search_fields ~98

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.

NameTypeReqDescription
kindstringyesFilter fields or output columns.
resourcestringyesWhich record type.

No output schema declared.

No examples provided.

neon_search ~235

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.

NameTypeReqDescription
current_pageinteger–0-based page number (Neon pages start at 0). Default 0.
output_fieldsarrayyesColumns to return: standard field names (strings) and/or custom-field ids (integers). Max 300.
page_sizeinteger–Results per page.
resourcestringyesWhich record type to search.
search_fieldsarrayyesFilter criteria, ANDed together. Neon requires at least one.
sort_columnstring–Output field name to sort by — it must also appear in output_fields.
sort_directionstring–Sort direction.

No output schema declared.

No examples provided.

neon_update_account ~239

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}.

NameTypeReqDescription
account_idstringyesThe account id.
company_namestring–New company name (COMPANY accounts only).
emailstring–Primary email (primaryContact.email1).
email2string–Secondary email (primaryContact.email2).
email_opt_outboolean–Opt the primary email out of email (email1OptOut).
first_namestring–First name (primaryContact.firstName).
job_titlestring–Job title (primaryContact.title).
last_namestring–Last name.
middle_namestring–Middle name.
no_solicitationboolean–Do-not-solicit flag.
preferred_namestring–Preferred name.
typestringyesThe account's type (individualAccount vs companyAccount).

No output schema declared.

No examples provided.

neon_update_activity ~111

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}.

NameTypeReqDescription
activity_idstringyesThe activity id.
notestring–New note (replaces the old one).
prioritystring–New priority.
status_idstring–New status id (neon_list_properties name=activityStatuses).
subjectstring–New subject.

No output schema declared.

No examples provided.

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.