# noCRM.io MCP by usefulapi (remote · nocrm-io.usefulapi.io)

Read noCRM.io leads, pipeline steps, comments and client folders; create, update and assign leads.

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

## Components

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

## Channel facts

- Endpoint: `https://nocrm-io.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

## 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-25.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2555 tokens (~106/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 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 noCRM.io MCP by usefulapi server?

noCRM.io MCP by usefulapi is a hosted endpoint at https://nocrm-io.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-nocrm-io 'https://nocrm-io.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-nocrm-io": {
      "type": "http",
      "url": "https://nocrm-io.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-25 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.0 → 1.2.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (24)

### `nocrm_list_leads` (~382 tokens)

List leads

List or search sales leads (noCRM.io's opportunities), newest first by default, with title, pipeline step, status, amount, probability, tags, owner, next reminder and the contact details in the description. Filter by status, step (names or ids, not mixed), owner, tags, email, starred or a date range. Unassigned leads are excluded unless include_unassigned is true. GET /leads.

Input parameters:

- `date_range_type` (string): Which date start_date/end_date apply to (default creation).
- `direction` (string): Sort direction (default desc).
- `email` (string): Only leads whose description or comments contain this email address.
- `end_date` (string): Until this date (yyyy-mm-dd), by date_range_type.
- `include_unassigned` (boolean): Also return leads that have no owner (default false).
- `limit` (integer): Results per call, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `order` (string): Sort attribute (default id).
- `starred` (boolean): true = only starred leads.
- `start_date` (string): From this date (yyyy-mm-dd), by date_range_type.
- `status` (array): Only leads in these statuses (todo = to do, standby = waiting for a reminder date).
- `steps`: Only leads in these pipeline steps: exact step names OR step ids (not mixed). See nocrm_list_steps.
- `tags` (array): Only leads carrying ALL of these tags.
- `updated_after` (string): Only leads updated on or after this date (yyyy-mm-dd). Do not combine with date_range_type.
- `user_id`: Only leads owned by this user (id or email).

### `nocrm_list_unassigned_leads` (~62 tokens)

List unassigned leads

Leads that have no owner yet (for example web-form or API leads waiting to be handed to a salesperson). GET /leads/unassigned.

Input parameters:

- `limit` (integer): Results per call, 1-100 (default 25).

### `nocrm_get_lead` (~68 tokens)

Get lead

One lead by id: title, step, status, amount, probability, tags, owner, client folder, team, reminder, and the full description with the contact's details. GET /leads/{id}.

Input parameters:

- `lead_id` (integer, required): noCRM.io lead id.

### `nocrm_list_lead_comments` (~70 tokens)

List lead comments

The comments (notes, logged calls/meetings/emails) on a lead, newest first by default. GET /leads/{id}/comments.

Input parameters:

- `direction` (string): Sort by date (default desc).
- `lead_id` (integer, required): noCRM.io lead id.

### `nocrm_list_lead_history` (~173 tokens)

List lead history

The timeline of a lead: creation, assignments, step and status changes, amount changes, comments and emails sent, with who did it and when. Filter by date range, action type or user. GET /leads/{id}/action_histories.

Input parameters:

- `action_type` (string): Only this kind of action.
- `direction` (string): Sort by id (default asc).
- `from` (string): From this date (yyyy-mm-dd).
- `lead_id` (integer, required): noCRM.io lead id.
- `limit` (integer): Results per call, 1-100 (default 25).
- `offset` (integer): Skip this many results (default 0). Pass the previous reply's next_offset.
- `to` (string): Until this date (yyyy-mm-dd).

### `nocrm_get_lead_duplicates` (~54 tokens)

Find duplicate leads

Leads that noCRM.io detects as possible duplicates of this lead (same email or key field). GET /leads/{id}/duplicates.

Input parameters:

- `lead_id` (integer, required): noCRM.io lead id.

### `nocrm_list_lead_attachments` (~50 tokens)

List lead attachments

File attachments on a lead (names, ids, sizes, links). GET /leads/{id}/attachments.

Input parameters:

- `lead_id` (integer, required): noCRM.io lead id.

### `nocrm_list_follow_ups` (~98 tokens)

List post-sales follow-ups

Post-sales processes (task checklists created from a template) of one lead OR of one user. Needs lead_id or user_id. Post-sales is a higher-edition feature (HTTP 403 otherwise). GET /follow_ups.

Input parameters:

- `lead_id` (integer): Follow-ups of this lead.
- `status` (array): Only these statuses.
- `user_id`: Follow-ups of this user (id or email).

### `nocrm_list_pipelines` (~34 tokens)

List pipelines

The sales pipelines of the account (one unless the multiple-pipelines feature is on). GET /pipelines.

### `nocrm_list_steps` (~62 tokens)

List pipeline steps

The steps (stages) of the sales pipeline in order, with ids, positions and their pipeline. Use the ids or names when filtering leads or moving a lead. GET /steps.

Input parameters:

- `direction` (string): Order by position (default asc).

### `nocrm_list_users` (~116 tokens)

List users

The users (salespeople) of the account with name, email, phone, role (admin or not) and whether they are active or deactivated. Deleted users are included, flagged is_disabled. GET /users.

Input parameters:

- `email` (string): Only the user with this email.
- `firstname` (string)
- `lastname` (string)
- `role` (string): Default all.
- `status` (string): Default all.
- `teams` (array): Only users in these teams (ids or names).

### `nocrm_get_user` (~45 tokens)

Get user

One user by id or email address. GET /users/{id}.

Input parameters:

- `user` (required): A user id or the user's email address (see nocrm_list_users).

### `nocrm_list_teams` (~41 tokens)

List teams

Sales teams with their members and who manages each. The Teams feature must be on in the account (HTTP 403 otherwise). GET /teams.

### `nocrm_list_client_folders` (~56 tokens)

List client folders

Client folders (accounts that group several leads), ordered by name by default. GET /clients.

Input parameters:

- `direction` (string): Default asc.
- `order` (string): Order by name (default) or id.

### `nocrm_get_client_folder` (~42 tokens)

Get client folder

One client folder by id, with its contact fields and owner. GET /clients/{id}.

Input parameters:

- `client_id` (integer, required): Client folder id.

### `nocrm_list_activities` (~39 tokens)

List activity types

The activity types (call, email, meeting and their outcomes) that can be set on a comment or reminder. GET /activities.

### `nocrm_list_predefined_tags` (~42 tokens)

List predefined tags

The account's predefined tags (admin keys only; an HTTP 401 unauthorized_non_admin means the key lacks rights). GET /predefined_tags.

### `nocrm_list_fields` (~37 tokens)

List custom fields

The custom fields defined for leads or client folders. GET /fields.

Input parameters:

- `type` (string): Only fields of this type.

### `nocrm_create_lead` (~181 tokens)

Create lead

WRITE: create a new lead. The description holds the contact's details, one 'Label: value' per line (for example 'Firstname: Ada', 'Email: ada@example.com', 'Phone: ...'); noCRM.io reads those lines. Without user_id the lead is created unassigned; a pipeline step can only be set when the lead is assigned. Not idempotent: calling twice creates two leads. POST /leads.

Input parameters:

- `description` (string, required): Contact details and notes, one 'Label: value' per line.
- `step`: Pipeline step id or exact name. Needs user_id.
- `tags` (array): Tags (created if new).
- `title` (string, required): Lead title, usually the company name.
- `user_id`: Owner (id or email). Omit for an unassigned lead.

### `nocrm_update_lead` (~291 tokens)

Update lead

WRITE: change a lead: title, status (won, lost, cancelled, todo or standby), pipeline step, amount, probability, star, estimated closing date, tags (replaces the lead's tag list), or append text to the description (existing description text is never replaced). Moving to standby needs remind_date. Only the fields you pass change. PUT /leads/{id}.

Input parameters:

- `amount` (number): Deal amount in the account currency.
- `append_description` (string): Text added at the end of the description.
- `estimated_closing_date` (string): yyyy-mm-dd, in the account's time zone.
- `lead_id` (integer, required): noCRM.io lead id.
- `probability` (integer): Win probability, percent.
- `remind_date` (string): Reminder date yyyy-mm-dd (required for standby).
- `remind_time` (string): Reminder time HH:MM, 24 h, in 15-minute steps.
- `reminder_note` (string): Note stored with the reminder.
- `starred` (boolean)
- `status` (string): New status. standby needs remind_date.
- `step`: Move to this step (id or exact name; prefer the id when pipelines share names).
- `tags` (array): The lead's tags after the update (replaces the current list; new tags are created).
- `title` (string)

### `nocrm_assign_lead` (~76 tokens)

Assign lead

WRITE: assign a lead to a user (id or email), replacing its current owner. The owner may get a notification from noCRM.io. POST /leads/{id}/assign.

Input parameters:

- `lead_id` (integer, required): noCRM.io lead id.
- `user_id` (required): The new owner (id or email).

### `nocrm_add_lead_comment` (~122 tokens)

Add lead comment

WRITE: add a comment (an internal note) to a lead, optionally typed as an activity such as a call or meeting. It is visible to the lead's team in noCRM.io and sends nothing to the customer. Not idempotent. POST /leads/{id}/comments.

Input parameters:

- `activity_id` (integer): Activity type id (see nocrm_list_activities), for example the id of 'Call'.
- `content` (string, required): The comment text.
- `lead_id` (integer, required): noCRM.io lead id.

### `nocrm_create_client_folder` (~69 tokens)

Create client folder

WRITE: create a client folder (an account that groups leads). Not idempotent. POST /clients.

Input parameters:

- `description` (string): For example the address.
- `name` (string, required): Folder name, usually the company.
- `user_id`: Owner (id or email).

### `nocrm_add_lead_to_client_folder` (~69 tokens)

Add lead to client folder

WRITE: file a lead under a client folder. POST /leads/{id}/add_to_client.

Input parameters:

- `client_id` (integer, required): Client folder id (see nocrm_list_client_folders).
- `lead_id` (integer, required): noCRM.io lead id.

## Diagnostics

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

## Score history

- 2026-10-25: 63
- 2026-10-24: 62

## Common questions

### What is the noCRM.io MCP by usefulapi server?

noCRM.io MCP by usefulapi is listed in the public MCP registry as io.usefulapi/nocrm-io. Read noCRM.io leads, pipeline steps, comments and client folders; create, update and assign leads. This page covers its hosted endpoint (https://nocrm-io.usefulapi.io/mcp).

### Is the noCRM.io MCP by usefulapi server safe to use?

noCRM.io 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 noCRM.io MCP by usefulapi server expose?

noCRM.io MCP by usefulapi exposes 24 tools: nocrm_list_leads, nocrm_list_unassigned_leads, nocrm_get_lead, nocrm_list_lead_comments, nocrm_list_lead_history, and 19 more. Their descriptions and schemas cost roughly 2,279 tokens of context every time the server is loaded.

### Does the noCRM.io MCP by usefulapi server require authentication?

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

noCRM.io 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.

## Links

- Remote endpoint: https://nocrm-io.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/nocrm-io/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-nocrm-io/nocrm-io.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-nocrm-io/nocrm-io.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-nocrm-io/nocrm-io