# io.usefulapi/jobnimbus (remote · jobnimbus.usefulapi.io)

Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat.

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

## Components

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

## Channel facts

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

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: this server exposes a tool marked destructive (jobnimbus_create_contact) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4261 tokens (~213/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/jobnimbus MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-jobnimbus": {
      "type": "http",
      "url": "https://jobnimbus.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-04 (score 63, −13)

- [security regression] Authorization: pass → unverified

### 2026-10-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 75, 0)

- [functional] Server version: 1.3.0 → 1.5.1

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

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

### 2026-09-30 (score 70, +52)

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

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

First indexed and scored.

## MCP tools (20)

### `jobnimbus_get_account_settings` (~102 tokens)

Get account settings

Fetch the account's configuration: contact and job workflows with their statuses, task types, activity (note) types, file types and lead sources. Use it to find the exact record_type_name / status_name / source_name values the create and update tools need. Pass field (e.g. groups) to get just one setting. JobNimbus: GET /account/settings.

Input parameters:

- `field` (string): Return only this setting, e.g. groups.

### `jobnimbus_list_users` (~55 tokens)

List users

List the account's JobNimbus users (team members) with name, email, id and whether they are active. The id is what owners, sales_rep and owner_ids take. JobNimbus: GET /account/users.

### `jobnimbus_list_contacts` (~227 tokens)

List or search contacts

List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.

Input parameters:

- `filter` (object): ElasticSearch-style bool query object, sent as the `filter` parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{…
- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).
- `sort_direction` (string): Sort direction (API default desc).
- `sort_field` (string): Field to sort by (API default date_created), e.g. date_updated.

### `jobnimbus_get_contact` (~69 tokens)

Get one contact

Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.

Input parameters:

- `jnid` (string, required): The contact's jnid (JobNimbus record id).

### `jobnimbus_list_jobs` (~266 tokens)

List or search jobs

List jobs (projects), newest first by default, optionally filtered — e.g. by status {"must":[{"term":{"status_name":"Lead"}}]} or by the related contact via related_id. Returns {count, results}. JobNimbus: GET /jobs.

Input parameters:

- `filter` (object): ElasticSearch-style bool query object, sent as the `filter` parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{…
- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `related_id` (string): Only records related to this contact or job jnid (adds a related.id term to the filter).
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).
- `sort_direction` (string): Sort direction (API default desc).
- `sort_field` (string): Field to sort by (API default date_created), e.g. date_updated.

### `jobnimbus_get_job` (~68 tokens)

Get one job

Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.

Input parameters:

- `jnid` (string, required): The job's jnid (JobNimbus record id).

### `jobnimbus_list_tasks` (~264 tokens)

List or search tasks

List tasks and appointments, optionally for one contact or job (related_id) or filtered, e.g. open ones: {"must":[{"term":{"is_completed":false}}]}. Returns {count, results}. JobNimbus: GET /tasks.

Input parameters:

- `filter` (object): ElasticSearch-style bool query object, sent as the `filter` parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{…
- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `related_id` (string): Only records related to this contact or job jnid (adds a related.id term to the filter).
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).
- `sort_direction` (string): Sort direction (API default desc).
- `sort_field` (string): Field to sort by (API default date_created), e.g. date_updated.

### `jobnimbus_get_task` (~65 tokens)

Get one task

Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.

Input parameters:

- `jnid` (string, required): The task's jnid (JobNimbus record id).

### `jobnimbus_list_activities` (~254 tokens)

List activity and notes

List activity entries — notes plus system events such as status changes and record creation — optionally for one contact or job (related_id). Returns {count, activity}. JobNimbus: GET /activities.

Input parameters:

- `filter` (object): ElasticSearch-style bool query object, sent as the `filter` parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{…
- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `related_id` (string): Only records related to this contact or job jnid (adds a related.id term to the filter).
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).
- `sort_direction` (string): Sort direction (API default desc).
- `sort_field` (string): Field to sort by (API default date_created), e.g. date_updated.

### `jobnimbus_list_files` (~270 tokens)

List file attachments

List file attachments (photos, documents) with filename, content type, size, file type and the contact/job they belong to — optionally for one record (related_id). Metadata only; file bytes are not downloaded. Returns {count, files}. JobNimbus: GET /files.

Input parameters:

- `filter` (object): ElasticSearch-style bool query object, sent as the `filter` parameter. Examples: {"must":[{"term":{"first_name":"john"}}]}; {"must":[{"range":{"date_updated":{"gte":"now-1d"}}}]}; {"must":[{"terms":{…
- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `related_id` (string): Only records related to this contact or job jnid (adds a related.id term to the filter).
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).
- `sort_direction` (string): Sort direction (API default desc).
- `sort_field` (string): Field to sort by (API default date_created), e.g. date_updated.

### `jobnimbus_list_estimates` (~116 tokens)

List estimates

List estimates with number, status, line items, subtotal, tax, total, margin, e-sign state and related job/contact. Returns {count, results}; count is the account total. JobNimbus: GET /v2/estimates.

Input parameters:

- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).

### `jobnimbus_list_invoices` (~114 tokens)

List invoices

List invoices with number, status, line items, total, total_paid, amount due, due date and related job/contact. Returns {count, results}; count is the account total. JobNimbus: GET /v2/invoices.

Input parameters:

- `from` (integer): Zero-based offset for pagination (default 0). Next page: from + size.
- `size` (integer): Records per page, 1-1000. Defaults to 25 here (the API's own default is 1000).

### `jobnimbus_get_invoice` (~64 tokens)

Get one invoice

Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.

Input parameters:

- `jnid` (string, required): The invoice's jnid (JobNimbus record id).

### `jobnimbus_create_contact` (~449 tokens)

Create a contact

Create a contact. Give at least one of first_name, last_name, display_name or company. record_type_name (a contact workflow, e.g. Customer) and status_name (a status in that workflow, e.g. Lead) are required and must match the account settings (jobnimbus_get_account_settings). Workflow automations may fire. JobNimbus: POST /contacts.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `address_line1` (string): Street address, line 1.
- `address_line2` (string): Street address, line 2.
- `city` (string): City.
- `company` (string): Company name.
- `country_name` (string): Country, e.g. United States.
- `custom_fields` (object): Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored.
- `description` (string): Description / notes on the contact record.
- `display_name` (string): Display name.
- `email` (string): Email address.
- `fax_number` (string): Fax number.
- `first_name` (string): First name.
- `home_phone` (string): Home phone.
- `last_name` (string): Last name.
- `mobile_phone` (string): Mobile phone.
- `record_type_name` (string, required): Contact workflow name, e.g. Customer.
- `sales_rep` (string): jnid of the user who is the sales rep.
- `source_name` (string): Lead source name, e.g. Referral — must be one of the account's lead sources.
- `state_text` (string): State, e.g. UT.
- `status_name` (string, required): Status within that workflow, e.g. Lead.
- `website` (string): Website.
- `work_phone` (string): Work phone.
- `zip` (string): Postal code.

### `jobnimbus_update_contact` (~425 tokens)

Update a contact

Edit fields on an existing contact — only the fields you pass change. Changing status_name moves it along its workflow (automations may fire). Cannot delete or archive. JobNimbus: PUT /contacts/{jnid}.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `address_line1` (string): Street address, line 1.
- `address_line2` (string): Street address, line 2.
- `city` (string): City.
- `company` (string): Company name.
- `country_name` (string): Country, e.g. United States.
- `custom_fields` (object): Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored.
- `description` (string): Description / notes on the contact record.
- `display_name` (string): Display name.
- `email` (string): Email address.
- `fax_number` (string): Fax number.
- `first_name` (string): First name.
- `home_phone` (string): Home phone.
- `jnid` (string, required): The contact's jnid (JobNimbus record id).
- `last_name` (string): Last name.
- `mobile_phone` (string): Mobile phone.
- `record_type_name` (string): Move to this contact workflow.
- `sales_rep` (string): jnid of the user who is the sales rep.
- `source_name` (string): Lead source name, e.g. Referral — must be one of the account's lead sources.
- `state_text` (string): State, e.g. UT.
- `status_name` (string): New workflow status name.
- `website` (string): Website.
- `work_phone` (string): Work phone.
- `zip` (string): Postal code.

### `jobnimbus_create_job` (~385 tokens)

Create a job

Create a job (project). name, record_type_name (a job workflow, e.g. Residential) and status_name (a status in it, e.g. Lead) are required and must match the account settings. Link the homeowner with primary_contact_id. Workflow automations may fire. JobNimbus: POST /jobs.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `address_line1` (string): Street address, line 1.
- `address_line2` (string): Street address, line 2.
- `city` (string): City.
- `country_name` (string): Country, e.g. United States.
- `custom_fields` (object): Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored.
- `date_end` (integer): End date, unix seconds.
- `date_start` (integer): Start date, unix seconds.
- `description` (string): Job description.
- `name` (string, required): Job name, e.g. Smith Roof Replacement.
- `primary_contact_id` (string): jnid of the job's primary contact (sent as primary.id).
- `record_type_name` (string, required): Job workflow name.
- `sales_rep` (string): jnid of the user who is the sales rep.
- `source_name` (string): Lead source name — must be one of the account's lead sources.
- `state_text` (string): State, e.g. UT.
- `status_name` (string, required): Status within that workflow.
- `zip` (string): Postal code.

### `jobnimbus_update_job` (~402 tokens)

Update a job

Edit fields on an existing job — e.g. move it to a new status_name, change the address, sales rep or dates. Only the fields you pass change; if JobNimbus rejects a status change, pass record_type_name alongside status_name. Automations may fire. Cannot delete or archive. JobNimbus: PUT /jobs/{jnid}.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `address_line1` (string): Street address, line 1.
- `address_line2` (string): Street address, line 2.
- `city` (string): City.
- `country_name` (string): Country, e.g. United States.
- `custom_fields` (object): Custom fields by their JobNimbus name, e.g. {"Claim Number":"124523-f","Date of Loss":1550692800} or {"cf_string_1":"…"}. Dates are unix seconds. is_active / is_archived are ignored.
- `date_end` (integer): End date, unix seconds.
- `date_start` (integer): Start date, unix seconds.
- `description` (string): Job description.
- `jnid` (string, required): The job's jnid (JobNimbus record id).
- `name` (string): New job name.
- `primary_contact_id` (string): jnid of the job's primary contact (sent as primary.id).
- `record_type_name` (string): Job workflow name.
- `sales_rep` (string): jnid of the user who is the sales rep.
- `source_name` (string): Lead source name — must be one of the account's lead sources.
- `state_text` (string): State, e.g. UT.
- `status_name` (string): New workflow status name.
- `zip` (string): Postal code.

### `jobnimbus_create_task` (~260 tokens)

Create a task

Create a task or appointment on a contact or job. title, date_start (unix seconds) and record_type_name (a task type from the account settings, e.g. Task or Appointment) are required; related_id links it to the contact/job. JobNimbus: POST /tasks.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `date_end` (integer): End time, unix seconds.
- `date_start` (integer, required): Start (or due) time, unix seconds.
- `description` (string): Task details.
- `estimated_time` (integer): Estimated minutes.
- `owner_ids` (array): jnids of the users to assign (sent as owners: [{id}]).
- `priority` (integer): Priority: 0 none, 1 high, 2 medium, 3 low.
- `record_type_name` (string, required): Task type name, e.g. Task or Appointment.
- `related_id` (string, required): jnid of the contact or job this task belongs to (sent as related: [{id}]).
- `title` (string, required): Task title.

### `jobnimbus_update_task` (~253 tokens)

Update a task

Edit an existing task — reschedule it, change the title or priority, reassign it, or mark it complete with is_completed=true (reopen with false). Only the fields you pass change. Cannot delete. JobNimbus: PUT /tasks/{jnid}.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `actual_time` (integer): Minutes logged.
- `date_end` (integer): New end time, unix seconds.
- `date_start` (integer): New start time, unix seconds.
- `description` (string): New details.
- `estimated_time` (integer): Estimated minutes.
- `is_completed` (boolean): true marks the task done; false reopens it.
- `jnid` (string, required): The task's jnid (JobNimbus record id).
- `owner_ids` (array): jnids of the users to assign (sent as owners: [{id}]).
- `priority` (integer): Priority: 0 none, 1 high, 2 medium, 3 low.
- `title` (string): New title.

### `jobnimbus_create_note` (~153 tokens)

Add a note

Add a note (activity entry) to a contact or job's activity feed. record_type_name defaults to Note; use another activity type from the account settings if needed. JobNimbus: POST /activities.

Input parameters:

- `actor` (string): Optional JobNimbus user email to act as. The record is created/edited with that user's permissions and shows them as the author. Needs an admin-level API key.
- `is_private` (boolean): Mark the note private.
- `note` (string, required): The note text.
- `primary_id` (string, required): jnid of the contact or job the note belongs to (sent as primary.id).
- `record_type_name` (string): Activity type name. Defaults to Note.

## Diagnostics

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

## Score history

- 2026-10-04: 63
- 2026-10-03: 76
- 2026-10-02: 75
- 2026-10-01: 75
- 2026-09-30: 70
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/jobnimbus MCP server?

io.usefulapi/jobnimbus is an MCP server listed in the public MCP registry as io.usefulapi/jobnimbus. Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat. This page covers its hosted endpoint (https://jobnimbus.usefulapi.io/mcp).

### Is the io.usefulapi/jobnimbus MCP server safe to use?

io.usefulapi/jobnimbus 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 io.usefulapi/jobnimbus MCP server expose?

io.usefulapi/jobnimbus exposes 20 tools: jobnimbus_get_account_settings, jobnimbus_list_users, jobnimbus_list_contacts, jobnimbus_get_contact, jobnimbus_list_jobs, and 15 more. Their descriptions and schemas cost roughly 4,261 tokens of context every time the server is loaded.

### Does the io.usefulapi/jobnimbus MCP server require authentication?

No. We connected to io.usefulapi/jobnimbus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.usefulapi/jobnimbus MCP server still maintained?

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