MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

io.usefulapi/civicrm

Work with your own CiviCRM: contacts, contributions, memberships, events; log activities. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-24version 1.1.0JavaScriptstreamable HTTP24 tools

Summary

io.usefulapi/civicrm is a remote MCP server listed in the official MCP registry at version 1.1.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 24 tools, 0 resources and 1 prompt.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 24
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 5 tools whose name or declaration suggests they change data (civicrm_create_contact, civicrm_update_contact, civicrm_add_contact_note, civicrm_create_membership, civicrm_add_contact_to_group). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.1.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-24 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, all on 2026-10-24; 2 in the 90 days before the 2026-10-24 snapshot.

Most recent 2 versions

1.1.0 · 2026-10-24
1.0.0 · 2026-10-24

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.1.0 (published 2026-10-24).

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.

What it is

What does this server offer?

Observed inventory

24tools

0resources

1prompts

None of its 24 tools are described as changing anything. For 24 the reading was uncertain, so no mark is shown.

civicrm_whoami
“The CiviCRM contact this API key belongs to (contact id, display name, contact type) and how it authenticated.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
civicrm_search_contacts
“Find contacts (people, organizations, households) by a word in their name, e-mail address or phone number, optionally of one contact type.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- querystring“Text to look for in the display name, primary e-mail or primary phone (partial match).”
- contact_typestring“Only this contact type.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_get_contact
“One contact by id: name, type, job title, source, communication preferences (do not e-mail, opted out, ...), dates, plus all their e-mail addresses, phone numbers and postal addresses.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- contact_idintegerrequired“CiviCRM contact id (the cid in the contact's URL).”
civicrm_list_contact_notes
“The notes recorded on one contact (subject, text, who wrote it, when), newest first.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- contact_idintegerrequired“CiviCRM contact id.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_relationships
“The relationships of one contact (employee of, spouse of, volunteer for, ...) with the other contact, start and end date and whether it is active.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 1 required
- contact_idintegerrequired“CiviCRM contact id.”
- active_onlyboolean“Only active relationships (default true).”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_contributions
“Contributions (donations, membership dues, event fees) with contact, amount, currency, financial type, status, payment method, date and source, newest first.”
Publisher declares: read-only yes · destructive no · open-world yes
8 inputs
- contact_idinteger“Only this contact's contributions.”
- statusstring“Only this status by name, e.g.”
- financial_typestring“Only this financial type by name, e.g.”
- date_fromstring“Received on or after this date.”
- date_tostring“Received on or before this date (a plain date includes that whole day).”
- min_amountnumber“Only contributions of at least this amount.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_memberships
“Memberships with contact, membership type, status (New, Current, Grace, Expired, ...), join, start and end date.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs
- contact_idinteger“Only this contact's memberships.”
- statusstring“Only this status by name, e.g.”
- membership_typestring“Only this membership type by name, e.g.”
- ends_beforestring“Only memberships that end on or before this date.”
- ends_afterstring“Only memberships that end on or after this date.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_events
“Events with title, type, start and end date, whether active and public, maximum participants and summary.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- titlestring“Only events whose title contains this text.”
- upcoming_onlyboolean“Only events that have not ended yet (start date today or later).”
- active_onlyboolean“Only active events (default true).”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_participants
“Event registrations with event, contact, status (Registered, Attended, Cancelled, ...), role, registration date and fee.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- event_idinteger“Only this event's participants.”
- contact_idinteger“Only this contact's registrations.”
- statusstring“Only this participant status by name, e.g.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_activities
“Activities (meetings, phone calls, e-mails, follow-ups, ...) with type, subject, status, date and details, newest first.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs
- contact_idinteger“Only activities this contact is involved in.”
- activity_typestring“Only this activity type by name, e.g.”
- statusstring“Only this status by name, e.g.”
- date_fromstring“On or after this date.”
- date_tostring“On or before this date (a plain date includes that whole day).”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_cases
“Cases (CiviCase) with subject, case type, status and dates.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- contact_idinteger“Only cases of this client contact.”
- statusstring“Only this case status by name, e.g.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_list_groups
“Contact groups (mailing lists, static groups, smart groups) with title, description, visibility and type.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs
- titlestring“Only groups whose title contains this text.”
- active_onlyboolean“Only active groups (default true).”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”

Show 12 more tools

civicrm_list_group_contacts
“The members of one static group (or the groups one contact belongs to): contact, group and membership status (Added, Removed, Pending).”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs
- group_idinteger“Members of this group (from civicrm_list_groups).”
- contact_idinteger“The groups of this contact.”
- statusstring“Membership status (default Added).”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_get_fields
“The fields of one CiviCRM entity (Contact, Contribution, Event, ...) including custom fields: name, label, data type, whether required, and the allowed options for a pick-list field.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- entitystringrequired“APIv4 entity name, e.g.”
- fieldstring“Only this field, with its options (e.g.”
- actionstring“The action the fields are for (default get).”
civicrm_list_entities
“The APIv4 entities this CiviCRM site offers (Contact, Contribution, Event, plus those of installed extensions), with a short description.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- searchstring“Only entities whose name or title contains this text.”
civicrm_query
“Read records of ANY CiviCRM entity with APIv4 Entity.get: choose fields, filter, sort and page.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 2 required
- entitystringrequired“APIv4 entity name, e.g.”
- selectarrayrequired“Fields to return.”
- wherearray“Filters, all of which must match.”
- order_byarray“Sort order.”
- limitinteger“Records per call, 1-100 (default 25).”
- offsetinteger“How many records to skip (default 0).”
civicrm_create_contact
“WRITE: creates ONE new contact (an individual, organization or household) and optionally its first e-mail address and phone number.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs, 1 required
- contact_typestringrequired“Individual, Organization or Household.”
- first_namestring“Individual: first name.”
- last_namestring“Individual: last name.”
- organization_namestring“Organization: its name.”
- household_namestring“Household: its name.”
- job_titlestring
- sourcestring“Where this contact came from (free text).”
- emailstring“First e-mail address (stored as the primary one).”
- phonestring“First phone number (stored as the primary one).”
civicrm_update_contact
“WRITE: changes basic fields of ONE existing contact (name, job title, source, preferred language) and/or its communication preferences (do not e-mail, do not phone, do not mail, do not SMS, opted out…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes
13 inputs, 1 required
- contact_idintegerrequired“CiviCRM contact id.”
- first_namestring
- last_namestring
- organization_namestring
- household_namestring
- job_titlestring
- sourcestring
- preferred_languagestring
- do_not_emailboolean
- do_not_phoneboolean
- do_not_mailboolean
- do_not_smsboolean
- is_opt_outboolean“Opted out of ALL bulk mailings.”
civicrm_add_contact_note
“WRITE: adds ONE note to a contact's record, written by the contact this API key belongs to.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
- contact_idintegerrequired“CiviCRM contact id the note is about.”
- notestringrequired“The note text.”
- subjectstring“Optional subject line.”
civicrm_log_activity
“WRITE: records ONE activity (a meeting, phone call, e-mail, follow-up, ...) with one or more contacts.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
8 inputs, 3 required
- activity_typestringrequired“Activity type by name, e.g.”
- subjectstringrequired“Subject line.”
- with_contact_idsarrayrequired“The contact(s) the activity is with.”
- detailsstring“Description.”
- statusstring“Status by name, e.g.”
- activity_date_timestring“When it happened or will happen (default now).”
- assignee_contact_idsarray“Contact(s) assigned to do it.”
- source_contact_idinteger“Who added it (default: the API key's own contact).”
civicrm_record_contribution
“WRITE: records ONE contribution (a donation, a payment received elsewhere) for a contact.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs, 3 required
- contact_idintegerrequired“CiviCRM contact id of the donor.”
- total_amountnumberrequired“Amount, in the site's currency unless currency is given.”
- financial_typestringrequired“Financial type by name, e.g.”
- receive_datestring“When it was received (default now).”
- statusstring“Contribution status by name: Completed (default), Pending, ...”
- payment_methodstring“Payment method by name, e.g.”
- currencystring“ISO currency code (default: the site's default).”
- sourcestring“Where it came from (free text).”
- trxn_idstring“Your own reference, e.g.”
civicrm_create_membership
“WRITE: gives ONE contact a membership of a type.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
6 inputs, 2 required
- contact_idintegerrequired“CiviCRM contact id.”
- membership_typestringrequired“Membership type by name, e.g.”
- join_datestring“Join date (default today).”
- start_datestring“Start date (default: calculated by the type).”
- end_datestring“End date (default: calculated by the type).”
- sourcestring“Where it came from (free text).”
civicrm_add_contact_to_group
“WRITE: adds ONE contact to ONE static group.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
- group_idintegerrequired“Group id (from civicrm_list_groups).”
- contact_idintegerrequired“CiviCRM contact id.”
civicrm_register_participant
“WRITE: registers ONE contact for ONE event (a participant record).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 2 required
- event_idintegerrequired“Event id (from civicrm_list_events).”
- contact_idintegerrequired“CiviCRM contact id.”
- statusstring“Participant status by name: Registered (default), Attended, Pending from pay later, ...”
- rolestring“Role by name: Attendee (default), Volunteer, Host, Speaker.”
- sourcestring“Where it came from (free text).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 90% of 122
Tools with a description: 100% of 24
Typical description length: 256 characters

The tool set

Counted from the listing

Tools: 24
Size of the list: about 7,684 tokens for an agent to load (characters ÷ 4)
Naming: 24 of 24 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 24 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://civicrm.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "civicrm": {
      "url": "https://civicrm.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "civicrm": {
      "type": "http",
      "url": "https://civicrm.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"civicrm","type":"http","url":"https://civicrm.usefulapi.io/mcp"}'

Claude Code

claude mcp add --transport http civicrm https://civicrm.usefulapi.io/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://civicrm.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint civicrm.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 409 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-24.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/civicrm

Answered from the data above

Is io.usefulapi/civicrm safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/civicrm need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/civicrm been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.usefulapi/civicrm?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
274 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 24 tools, 0 resources, 1 prompt.
975 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-24; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/civicrm: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/civicrm

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/civicrm)](https://protocolprobe.com/mcp/servers/io.usefulapi/civicrm)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology