io.usefulapi/jobnimbus
REMOTE · JOBNIMBUS.USEFULAPI.IO · SCANNED OCT 4
Manage JobNimbus contacts, jobs, tasks, estimates and invoices from chat.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
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.
remote · jobnimbus.usefulapi.io
claude mcp add --transport http io-usefulapi-jobnimbus 'https://jobnimbus.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-jobnimbus": {
"url": "https://jobnimbus.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-jobnimbus": {
"type": "http",
"url": "https://jobnimbus.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-jobnimbus] url = "https://jobnimbus.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-jobnimbus": {
"type": "remote",
"url": "https://jobnimbus.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-jobnimbus --url 'https://jobnimbus.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-jobnimbus:
url: "https://jobnimbus.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-jobnimbus": {
"Transport": "http",
"Url": "https://jobnimbus.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-jobnimbus -t streamable-http -u 'https://jobnimbus.usefulapi.io/mcp'
{
"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.
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.
- 4 Oct 26 −13
- Authorization: pass → unverified ▼ security
- 3 Oct 26 +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.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
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 4 Oct 2026 · Probed https://jobnimbus.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 jobnimbus.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobnimbus.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://jobnimbus.usefulapi.io/mcp | HTTPS enforced | 301 | https://jobnimbus.usefulapi.io/mcp |
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 →
jobnimbus_create_contact Create a contact ~449
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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 | yes | 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 | yes | Status within that workflow, e.g. Lead. |
| website | string | – | Website. |
| work_phone | string | – | Work phone. |
| zip | string | – | Postal code. |
No output schema declared.
No examples provided.
jobnimbus_create_job Create a job ~385
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | Status within that workflow. |
| zip | string | – | Postal code. |
No output schema declared.
No examples provided.
jobnimbus_create_note Add a note ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The note text. |
| primary_id | string | yes | jnid of the contact or job the note belongs to (sent as primary.id). |
| record_type_name | string | – | Activity type name. Defaults to Note. |
No output schema declared.
No examples provided.
jobnimbus_create_task Create a task ~260
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Task type name, e.g. Task or Appointment. |
| related_id | string | yes | jnid of the contact or job this task belongs to (sent as related: [{id}]). |
| title | string | yes | Task title. |
No output schema declared.
No examples provided.
jobnimbus_get_account_settings Get account settings ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Return only this setting, e.g. groups. |
No output schema declared.
No examples provided.
jobnimbus_get_contact Get one contact ~69
Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.
| Name | Type | Req | Description |
|---|---|---|---|
| jnid | string | yes | The contact's jnid (JobNimbus record id). |
No output schema declared.
No examples provided.
jobnimbus_get_invoice Get one invoice ~64
Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.
| Name | Type | Req | Description |
|---|---|---|---|
| jnid | string | yes | The invoice's jnid (JobNimbus record id). |
No output schema declared.
No examples provided.
jobnimbus_get_job Get one job ~68
Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.
| Name | Type | Req | Description |
|---|---|---|---|
| jnid | string | yes | The job's jnid (JobNimbus record id). |
No output schema declared.
No examples provided.
jobnimbus_get_task Get one task ~65
Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.
| Name | Type | Req | Description |
|---|---|---|---|
| jnid | string | yes | The task's jnid (JobNimbus record id). |
No output schema declared.
No examples provided.
jobnimbus_list_activities List activity and notes ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jobnimbus_list_contacts List or search contacts ~227
List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jobnimbus_list_estimates List estimates ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jobnimbus_list_files List file attachments ~270
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jobnimbus_list_invoices List invoices ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
jobnimbus_list_jobs List or search jobs ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jobnimbus_list_tasks List or search tasks ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
jobnimbus_list_users List users ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
jobnimbus_update_contact Update a contact ~425
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| string | – | Email address. | |
| fax_number | string | – | Fax number. |
| first_name | string | – | First name. |
| home_phone | string | – | Home phone. |
| jnid | string | yes | 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. |
No output schema declared.
No examples provided.
jobnimbus_update_job Update a job ~402
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
jobnimbus_update_task Update a task ~253
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.