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.

CentralStationCRM MCP by usefulapi

REMOTE · CENTRALSTATIONCRM.USEFULAPI.IO

Read CentralStationCRM people, companies, deals, tasks; create and update people, companies, deals.

63 Trust /100

Last scanned (1 hour ago)

Scores higher than 47% of remote servers

Reachable. Last reached 25 Oct 2026.

Category CRM and Sales

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 Security78
Transport & Reachability0
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4041 tokens (~122/item across 33 items; 33 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 Management3
  • Stability observed for 1 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
  • 99% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 34 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
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.

  • 25 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.1.0 → 1.1.1 functional
  • 24 Oct 26 62

    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 25 Oct 2026 · Probed https://centralstationcrm.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 centralstationcrm.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 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 302

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

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

Protected resource metadata

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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://centralstationcrm.usefulapi.io/mcp Redirected 302 https://usefulapi.io/centralstationcrm/
http (plaintext) http://centralstationcrm.usefulapi.io/mcp Inconclusive 302 http://centralstationcrm.usefulapi.io/mcp
MCP tools · 33 exposed · ~3,765 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
centralstationcrm_count_records ~61

Total number of people, companies, deals or projects (optionally only those with a tag). GET /<resource>/count.

NameTypeReqDescription
resourcestringyesWhich records to count.
tag_namestring–Only records with this tag.

No output schema declared.

No examples provided.

centralstationcrm_create_company ~70

WRITE: create a company. Nothing is sent to the contact. POST /companies.

NameTypeReqDescription
backgroundstring–Background notes about the company.
namestringyesCompany name (max 120).
user_idinteger–Responsible user id (default: the API user).

No output schema declared.

No examples provided.

centralstationcrm_create_deal ~225

WRITE: create a deal (sales opportunity). Use list_deal_types for pipeline and stage ids. Pipelines with a monetary value or target date need value and target_date (value_type defaults to total); the vendor says what is missing. Nothing is sent to the contact. POST /deals.

NameTypeReqDescription
backgroundstring–Details about the deal.
company_idinteger–Company the deal belongs to.
currencystring–Currency (account default if omitted).
deal_type_idinteger–Pipeline id (see list_deal_types).
deal_type_stage_idinteger–Stage id within the pipeline.
namestringyesDeal name (max 120).
probabilityinteger–Probability of winning, percent.
target_datestring–Date the deal shall be won.
user_idinteger–Responsible user id.
valuenumber–Monetary value (with value_type total: the full amount).
value_typestring–How the value is billed (default total).

No output schema declared.

No examples provided.

centralstationcrm_create_note ~144

WRITE: add a note to the history of one or more people, companies, deals or projects. Nothing is sent to the contact. POST /protocols.

NameTypeReqDescription
company_idsarray–Companies the note belongs to.
confidentialboolean–true = visible only to users with at least power-user rights (not only to you).
contentstringyesNote text (markdown).
deal_idsarray–Deals the note belongs to.
namestringyesNote title (max 100 characters).
person_idsarray–People the note belongs to.
project_idsarray–Projects the note belongs to.

No output schema declared.

No examples provided.

centralstationcrm_create_person ~183

WRITE: create a contact person (last name required), optionally with email addresses and phone numbers. Nothing is sent to the contact. POST /people.

NameTypeReqDescription
backgroundstring–Background notes about the person.
country_codestring–Language of the person as a 2-letter ISO 639-1 code, e.g. de or en (the vendor field is called country_code).
emailsarray––
first_namestring–First name (max 80).
namestringyesLast name (max 80).
phonesarray––
salutationstring–Free-text salutation (max 80).
titlestring–Title, e.g. Dr. (max 80).
user_idinteger–Responsible user id (default: the API user).

No output schema declared.

No examples provided.

centralstationcrm_create_task ~173

WRITE: create a task (to-do, call, email, visit...) optionally attached to a person, company or deal and assigned to a user. Nothing is sent to the contact. POST /tasks.

NameTypeReqDescription
attachable_idinteger–Id of that record (required with attachable_type).
attachable_typestring–Kind of record the task belongs to (omit for a general task).
badgestring–Kind of task (default task).
fuzzyboolean–true = only the day of precise_time matters, not the hour.
namestringyesWhat has to be done.
precise_timestring–When it is due.
user_idinteger–User the task is assigned to (default: the user behind the API key).

No output schema declared.

No examples provided.

centralstationcrm_get_company ~73

One company by id, optionally with related records (people, deals, tags, tasks, contact details, addresses). GET /companies/{id}.

NameTypeReqDescription
company_idintegeryesCentralStationCRM company id.
includesarray–Related records to embed (an extra call is not needed for them).

No output schema declared.

No examples provided.

centralstationcrm_get_current_user ~58

The CentralStationCRM user this API key belongs to: id, name, login email, the account (subdomain) it is signed in to, timezone. Use the user id to assign records or tasks. GET /user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

centralstationcrm_get_deal ~71

One deal by id, optionally with its tags, people, company, tasks and calendar events. GET /deals/{id}.

NameTypeReqDescription
deal_idintegeryesCentralStationCRM deal id.
includesarray–Related records to embed (an extra call is not needed for them).

No output schema declared.

No examples provided.

centralstationcrm_get_deal_stats ~54

Number and total value of all deals (optionally only those with a tag), with the account currency. GET /deals/stats.

NameTypeReqDescription
tag_namestring–Only deals with this tag.

No output schema declared.

No examples provided.

centralstationcrm_get_note ~42

One note / history entry by id. GET /protocols/{id}.

NameTypeReqDescription
note_idintegeryesCentralStationCRM protocol (note) id.

No output schema declared.

No examples provided.

centralstationcrm_get_person ~76

One person by id, optionally with related records (companies, deals, tags, tasks, email addresses, phone numbers, addresses). GET /people/{id}.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
person_idintegeryesCentralStationCRM person id.

No output schema declared.

No examples provided.

centralstationcrm_get_project ~69

One project by id, optionally with its tags, people, company, tasks and calendar events. GET /projects/{id}.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
project_idintegeryesCentralStationCRM project id.

No output schema declared.

No examples provided.

centralstationcrm_get_task ~35

One task by id. GET /tasks/{id}.

NameTypeReqDescription
task_idintegeryesCentralStationCRM task id.

No output schema declared.

No examples provided.

centralstationcrm_list_calendar_events ~130

List calendar events (appointments, meetings) of the account. Filter by upcoming/old and date range. GET /cal_events.

NameTypeReqDescription
afterstring–Only events after this date.
beforestring–Only events before this date.
orderstring–Ordering by id.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
statestring–Only upcoming or only past events.

No output schema declared.

No examples provided.

centralstationcrm_list_companies ~145

List companies. Optionally filter by tag and order by name, creation or last update. Use search_companies to find one by name. GET /companies.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
orderstring–Ordering (abc = by name, new = creation date, update = last change).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
tag_namestring–Only companies with this tag.

No output schema declared.

No examples provided.

centralstationcrm_list_deal_types ~48

List the deal types (pipelines) with their stages. Use the ids (and stage ids) to create deals and to move them between stages. GET /deal_types.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

centralstationcrm_list_deals ~217

List deals (sales opportunities) with value, state (open_0/25/50/75, won, lost), pipeline and stage ids, target date. Filter by company, responsible user, pipeline or state; order by date, value, state or name. GET /deals.

NameTypeReqDescription
company_idinteger–Only deals of this company.
current_statestring–Only deals in this state.
deal_type_idinteger–Only deals in this pipeline (see list_deal_types).
includesarray–Related records to embed (an extra call is not needed for them).
orderstring–Ordering.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
tag_namestring–Only deals with this tag.
user_idinteger–Only deals of this responsible user.

No output schema declared.

No examples provided.

centralstationcrm_list_notes ~155

List protocols: notes, logged emails and other history entries. Filter by the person, company, deal or project they belong to. GET /protocols.

NameTypeReqDescription
company_idinteger–Only entries of this company.
deal_idinteger–Only entries of this deal.
orderstring–Ordering by id (id-desc = newest first).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
person_idinteger–Only entries of this person.
project_idinteger–Only entries of this project.

No output schema declared.

No examples provided.

centralstationcrm_list_people ~149

List contact people. Optionally filter by tag and order by name, creation or last update. Use search_people to find a person by name, email or phone. GET /people.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
orderstring–Ordering (abc = by name, new = creation date, update = last change).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
tag_namestring–Only people with this tag.

No output schema declared.

No examples provided.

centralstationcrm_list_projects ~123

List projects with state, target date and company. Filter by tag; order by date, state or name. GET /projects.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
orderstring–Ordering.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
tag_namestring–Only projects with this tag.

No output schema declared.

No examples provided.

centralstationcrm_list_tags ~70

List all tag names used in the account. GET /tags/list.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

centralstationcrm_list_tasks ~151

List tasks (to-dos, calls, emails, visits) of the account. Filter by open/closed state, due-date range and responsible user. GET /tasks.

NameTypeReqDescription
afterstring–Only tasks after this date.
beforestring–Only tasks before this date.
orderstring–Ordering by id.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
statestring–Only open or only closed tasks.
user_idinteger–Only tasks of this user.

No output schema declared.

No examples provided.

centralstationcrm_list_users ~99

List the users of the CentralStationCRM account (id, name, email). Use the ids for responsible-user filters and for assigning records. GET /users.

NameTypeReqDescription
activeboolean–Only currently active users.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

centralstationcrm_search_all ~39

Full-text search across people, companies, deals and projects for a term. GET /search.

NameTypeReqDescription
termstringyesSearch term.

No output schema declared.

No examples provided.

centralstationcrm_search_companies ~101

Find companies by name. GET /companies/search.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
namestringyesCompany name (or part of it).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

centralstationcrm_search_deals ~102

Find deals by name. GET /deals/search.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
namestringyesDeal name (or part of it).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

centralstationcrm_search_people ~162

Find people by last name, first name, email address or phone number (email and phone cannot be combined). Give at least one criterion. GET /people/search.

NameTypeReqDescription
emailstring–Email address (not combinable with phone).
first_namestring–First name (max 80).
includesarray–Related records to embed (an extra call is not needed for them).
namestring–Last name.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).
phonestring–Phone number (not combinable with email).

No output schema declared.

No examples provided.

centralstationcrm_search_projects ~100

Find projects by name. GET /projects/search.

NameTypeReqDescription
includesarray–Related records to embed (an extra call is not needed for them).
namestringyesProject name (or part of it).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
perpageinteger–Results per page, 1-250 (default 50).

No output schema declared.

No examples provided.

centralstationcrm_update_company ~88

WRITE: change fields of a company. Only the fields you give are sent. PUT /companies/{id}.

NameTypeReqDescription
backgroundstring–New background notes (replaces the old text).
company_idintegeryesCentralStationCRM company id.
namestring–New company name (max 120).
user_idinteger–New responsible user id.

No output schema declared.

No examples provided.

centralstationcrm_update_deal ~242

WRITE: change fields of a deal, for example move it to another stage or set its state to won or lost. Only the fields you give are sent. PUT /deals/{id}.

NameTypeReqDescription
backgroundstring–Details about the deal.
company_idinteger–Company the deal belongs to.
currencystring–Currency (account default if omitted).
current_statestring–New state: open_0/25/50/75, won or lost.
deal_idintegeryesCentralStationCRM deal id.
deal_type_idinteger–Pipeline id (see list_deal_types).
deal_type_stage_idinteger–Stage id within the pipeline.
namestring–New deal name (max 120).
probabilityinteger–Probability of winning, percent.
target_datestring–Date the deal shall be won.
user_idinteger–Responsible user id.
valuenumber–Monetary value (with value_type total: the full amount).
value_typestring–How the value is billed (default total).

No output schema declared.

No examples provided.

centralstationcrm_update_person ~174

WRITE: change fields of a person. Only the fields you give are sent; the rest stays. PUT /people/{id}.

NameTypeReqDescription
backgroundstring–New background notes (replaces the old text).
country_codestring–New language of the person as a 2-letter ISO 639-1 code, e.g. de or en (the vendor field is called country_code).
first_namestring–New first name (max 80).
namestring–New last name (max 80).
person_idintegeryesCentralStationCRM person id.
salutationstring–New salutation (max 80).
titlestring–New title (max 80).
user_idinteger–New responsible user id.

No output schema declared.

No examples provided.

centralstationcrm_update_task ~136

WRITE: change a task, for example mark it done (finished = true), rename it or reschedule it. Only the fields you give are sent. PUT /tasks/{id}.

NameTypeReqDescription
badgestring–New kind of task.
finishedboolean–true = mark done, false = reopen.
fuzzyboolean–true = only the day of precise_time matters.
namestring–New task text.
precise_timestring–New due date-time.
task_idintegeryesCentralStationCRM task id.
user_idinteger–New assignee.

No output schema declared.

No examples provided.

Install

How do I install the CentralStationCRM MCP by usefulapi server?

CentralStationCRM MCP by usefulapi is a hosted endpoint at https://centralstationcrm.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 · centralstationcrm.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-centralstationcrm 'https://centralstationcrm.usefulapi.io/mcp'
Common questions

What is the CentralStationCRM MCP by usefulapi server?

CentralStationCRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/centralstationcrm. Read CentralStationCRM people, companies, deals, tasks; create and update people, companies, deals. This page covers its hosted endpoint (https://centralstationcrm.usefulapi.io/mcp).

Is the CentralStationCRM MCP by usefulapi server safe to use?

CentralStationCRM MCP by usefulapi scores 63 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 CentralStationCRM MCP by usefulapi server expose?

CentralStationCRM MCP by usefulapi exposes 33 tools: centralstationcrm_get_current_user, centralstationcrm_list_users, centralstationcrm_list_people, centralstationcrm_search_people, centralstationcrm_get_person, and 28 more. Their descriptions and schemas cost roughly 3,765 tokens of context every time the server is loaded.

Does the CentralStationCRM MCP by usefulapi server require authentication?

Yes. CentralStationCRM MCP by usefulapi 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 CentralStationCRM MCP by usefulapi server still maintained?

CentralStationCRM MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.