Skip to content

JobNimbus MCP by usefulapi

io.usefulapi/jobnimbususefulapi.iostreamable-httpv1.41.6Scanned

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

20 tools: 7 can delete or cancel things and 13 only read.

Tools: 7 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 10
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the JobNimbus MCP by usefulapi can do

The JobNimbus MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 20 tools. It can delete or cancel things (7 tools: jobnimbus_create_contact, jobnimbus_update_contact, jobnimbus_create_job, jobnimbus_update_job and 3 more). 13 tools only read.

10 tools read private data (jobnimbus_get_account_settings, jobnimbus_list_users, jobnimbus_list_contacts and 7 more); 2 tools bring in text other people can write (jobnimbus_list_users and jobnimbus_get_contact).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.41.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

20 tools

Deletes or cancels 7Claude Code: deny
  • jobnimbus_create_contactCreate a contact.No findings

    Why it is in this group

    • The name "jobnimbus_create_contact" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a contact
    • destructiveHint: true
  • jobnimbus_create_jobCreate a job (project).No findings

    Why it is in this group

    • The name "jobnimbus_create_job" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a job
    • destructiveHint: true
  • jobnimbus_create_noteAdd a note (activity entry) to a contact or job's activity feed.No findings

    Why it is in this group

    • The name "jobnimbus_create_note" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Add a note
    • destructiveHint: true
  • jobnimbus_create_taskCreate a task or appointment on a contact or job.No findings

    Why it is in this group

    • The name "jobnimbus_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • jobnimbus_update_contactEdit fields on an existing contact — only the fields you pass change.No findings

    Why it is in this group

    • The name "jobnimbus_update_contact" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a contact
    • destructiveHint: true
  • jobnimbus_update_jobEdit fields on an existing job — e.g.No findings

    Why it is in this group

    • The name "jobnimbus_update_job" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a job
    • destructiveHint: true
  • jobnimbus_update_taskEdit an existing task — reschedule it, change the title or priority, reassign it, or mark it complete with is_completed=true (reopen with false).No findings

    Why it is in this group

    • The name "jobnimbus_update_task" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a task
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • jobnimbus_get_account_settingsFetch the account's configuration: contact and job workflows with their statuses, task types, activity (note) types, file types and lead sources.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_get_account_settings" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get account settings
    • readOnlyHint: true
  • jobnimbus_get_contactFetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "jobnimbus_get_contact" says "get": a word for reading.

    What it can reach

    • private-dataThe name "jobnimbus_get_contact" says "get" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Fetch a single contact by jnid: name, company, phones, email, address, workflow status, lead source, sales rep and custom fields. JobNimbus: GET /contacts/{jnid}.

    Annotations the server declares

    • title: Get one contact
    • readOnlyHint: true
  • jobnimbus_get_invoiceFetch a single invoice by jnid, including line items, payments applied, total, total_paid and due.No findings

    Why it is in this group

    • The name "jobnimbus_get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single invoice by jnid, including line items, payments applied, total, total_paid and due. JobNimbus: GET /v2/invoices/{jnid}.

    Annotations the server declares

    • title: Get one invoice
    • readOnlyHint: true
  • jobnimbus_get_jobFetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_get_job" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    Description, as the server wrote it
    Fetch a single job by jnid: name, number, workflow and status, address, sales rep, owners, related contacts and custom fields. JobNimbus: GET /jobs/{jnid}.

    Annotations the server declares

    • title: Get one job
    • readOnlyHint: true
  • jobnimbus_get_taskFetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records.No findings

    Why it is in this group

    • The name "jobnimbus_get_task" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single task or appointment by jnid: title, type, start/end, priority, completion, owners and related records. JobNimbus: GET /tasks/{jnid}.

    Annotations the server declares

    • title: Get one task
    • readOnlyHint: true
  • jobnimbus_list_activitiesList activity entries — notes plus system events such as status changes and record creation — optionally for one contact or job (related_id).Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_activities" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List activity and notes
    • readOnlyHint: true
  • jobnimbus_list_contactsList contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_contacts" says "list": a word for reading.

    What it can reach

    • private-dataThe name "jobnimbus_list_contacts" says "list" and "contact": it reads contacts.
    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List contacts (customers, leads, adjusters, subcontractors…), newest first by default, optionally filtered with an ElasticSearch-style query. Returns {count, results}. JobNimbus: GET /contacts.

    Annotations the server declares

    • title: List or search contacts
    • readOnlyHint: true
  • jobnimbus_list_estimatesList estimates with number, status, line items, subtotal, tax, total, margin, e-sign state and related job/contact.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_estimates" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List estimates
    • readOnlyHint: true
  • jobnimbus_list_filesList file attachments (photos, documents) with filename, content type, size, file type and the contact/job they belong to — optionally for one record (related_id).Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "jobnimbus_list_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List file attachments
    • readOnlyHint: true
  • jobnimbus_list_invoicesList invoices with number, status, line items, total, total_paid, amount due, due date and related job/contact.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_invoices" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • jobnimbus_list_jobsList jobs (projects), newest first by default, optionally filtered — e.g.No findings

    Why it is in this group

    • The name "jobnimbus_list_jobs" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List or search jobs
    • readOnlyHint: true
  • jobnimbus_list_tasksList tasks and appointments, optionally for one contact or job (related_id) or filtered, e.g.Reads private dataNo findings

    Why it is in this group

    • The name "jobnimbus_list_tasks" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List or search tasks
    • readOnlyHint: true
  • jobnimbus_list_usersList the account's JobNimbus users (team members) with name, email, id and whether they are active.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "jobnimbus_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List users
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://jobnimbus.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://jobnimbus.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://jobnimbus.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://jobnimbus.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.41.6. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jobnimbus__jobnimbus_get_account_settings",
      "mcp__jobnimbus__jobnimbus_list_users",
      "mcp__jobnimbus__jobnimbus_list_contacts",
      "mcp__jobnimbus__jobnimbus_get_contact",
      "mcp__jobnimbus__jobnimbus_list_jobs",
      "mcp__jobnimbus__jobnimbus_get_job",
      "mcp__jobnimbus__jobnimbus_list_tasks",
      "mcp__jobnimbus__jobnimbus_get_task",
      "mcp__jobnimbus__jobnimbus_list_activities",
      "mcp__jobnimbus__jobnimbus_list_files",
      "mcp__jobnimbus__jobnimbus_list_estimates",
      "mcp__jobnimbus__jobnimbus_list_invoices",
      "mcp__jobnimbus__jobnimbus_get_invoice"
    ],
    "ask": [],
    "deny": [
      "mcp__jobnimbus__jobnimbus_create_contact",
      "mcp__jobnimbus__jobnimbus_update_contact",
      "mcp__jobnimbus__jobnimbus_create_job",
      "mcp__jobnimbus__jobnimbus_update_job",
      "mcp__jobnimbus__jobnimbus_create_task",
      "mcp__jobnimbus__jobnimbus_update_task",
      "mcp__jobnimbus__jobnimbus_create_note"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jobnimbus. Review it before you use it.

Capability tags behind 10 rules
  • mcp__jobnimbus__jobnimbus_get_account_settings private-data
  • mcp__jobnimbus__jobnimbus_list_users private-data, untrusted-input
  • mcp__jobnimbus__jobnimbus_list_contacts private-data
  • mcp__jobnimbus__jobnimbus_get_contact private-data, untrusted-input
  • mcp__jobnimbus__jobnimbus_get_job private-data
  • mcp__jobnimbus__jobnimbus_list_tasks private-data
  • mcp__jobnimbus__jobnimbus_list_activities private-data
  • mcp__jobnimbus__jobnimbus_list_files private-data
  • mcp__jobnimbus__jobnimbus_list_estimates private-data
  • mcp__jobnimbus__jobnimbus_list_invoices private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/jobnimbus/verify?hash=62c5a06bb51a82c0ce5eeef0ae080491f9083753d6882b5ffa928f48efe4f322" | jq -e '.changed == false'

Pinned hash 62c5a06bb51a, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/jobnimbus/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/jobnimbus
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/jobnimbus.svg)](https://radar.anlyon.com/servers/io.usefulapi/jobnimbus)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

JobNimbus MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the JobNimbus MCP by usefulapi safe?

No scan can promise that. What its definitions show: 20 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the JobNimbus MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: jobnimbus_create_contact, jobnimbus_update_contact, jobnimbus_create_job, jobnimbus_update_job, jobnimbus_create_task, jobnimbus_update_task and 1 more.

Can the JobNimbus MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the JobNimbus MCP by usefulapi have?

20 tools: 7 destructive, 13 read. jobnimbus_create_contact, jobnimbus_update_contact, jobnimbus_create_job, jobnimbus_update_job, jobnimbus_create_task, jobnimbus_update_task, jobnimbus_create_note, jobnimbus_get_account_settings and 12 more.

Does the JobNimbus MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the JobNimbus MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the JobNimbus MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.