Contractor Foreman by Cotlet
REMOTE · COTLET.DEV · 2 COMPONENTS
Projects, estimates, daily logs and invoices in Contractor Foreman.
Available components
Last scanned (4 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Project Management
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cotlet_browser_click). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 14600 tokens (~136/item across 107 items; 106 tools + 1 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 Management0
- Stability check failed: schema churn in the 1 day we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 66% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 108 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 24 Oct 26 0
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “cotlet_balance” was removed ▼ security
- Tool “cotlet_browser_connect” was removed ▼ security
- Tool “cotlet_browser_sessions” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_change_order_items” rewrote its description, which is the text the model reads security
- Tool “add_estimate_items” rewrote its description, which is the text the model reads security
- Tool “add_invoice_items” rewrote its description, which is the text the model reads security
- Tool “add_project_note” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_click” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_close” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_navigate” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_open” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_press” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_read” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_screenshot” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_scroll” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_select” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_type” rewrote its description, which is the text the model reads security
- Tool “cotlet_browser_upload” rewrote its description, which is the text the model reads security
- Tool “create_bill” rewrote its description, which is the text the model reads security
- Tool “create_change_order” rewrote its description, which is the text the model reads security
- Tool “create_contact” rewrote its description, which is the text the model reads security
- Tool “create_daily_log” rewrote its description, which is the text the model reads security
- Tool “create_estimate” rewrote its description, which is the text the model reads security
- Tool “create_expense” rewrote its description, which is the text the model reads security
- Tool “create_inspection” rewrote its description, which is the text the model reads security
- Tool “create_invoice” rewrote its description, which is the text the model reads security
- Tool “create_lead” rewrote its description, which is the text the model reads security
- Tool “create_opportunity” rewrote its description, which is the text the model reads security
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “create_punchlist” rewrote its description, which is the text the model reads security
- Tool “create_purchase_order” rewrote its description, which is the text the model reads security
- Tool “create_rfi” rewrote its description, which is the text the model reads security
- Tool “create_service_ticket” rewrote its description, which is the text the model reads security
- Tool “create_share_link” rewrote its description, which is the text the model reads security
- Tool “create_sub_contract” rewrote its description, which is the text the model reads security
- Tool “create_todo” rewrote its description, which is the text the model reads security
- Tool “create_work_order” rewrote its description, which is the text the model reads security
- Tool “delete_change_order” rewrote its description, which is the text the model reads security
- Tool “delete_estimate” rewrote its description, which is the text the model reads security
- Tool “delete_invoice” rewrote its description, which is the text the model reads security
- Tool “get_bill” rewrote its description, which is the text the model reads security
- Tool “get_change_order” rewrote its description, which is the text the model reads security
- Tool “get_clock_status” rewrote its description, which is the text the model reads security
- Tool “get_contact” rewrote its description, which is the text the model reads security
- Tool “get_daily_log” rewrote its description, which is the text the model reads security
- Tool “get_estimate” rewrote its description, which is the text the model reads security
- Tool “get_expense” rewrote its description, which is the text the model reads security
- Tool “get_inspection” rewrote its description, which is the text the model reads security
- Tool “get_invoice” rewrote its description, which is the text the model reads security
- Tool “get_job_costing” rewrote its description, which is the text the model reads security
- Tool “get_opportunity” rewrote its description, which is the text the model reads security
- Tool “get_project” rewrote its description, which is the text the model reads security
- Tool “get_punchlist” rewrote its description, which is the text the model reads security
- Tool “get_purchase_order” rewrote its description, which is the text the model reads security
- Tool “get_rfi” rewrote its description, which is the text the model reads security
- Tool “get_service_ticket” rewrote its description, which is the text the model reads security
- Tool “get_sub_contract” rewrote its description, which is the text the model reads security
- Tool “get_submittal” rewrote its description, which is the text the model reads security
- Tool “get_time_card” rewrote its description, which is the text the model reads security
- Tool “get_todo” rewrote its description, which is the text the model reads security
- Tool “get_work_order” rewrote its description, which is the text the model reads security
- Tool “list_bills” rewrote its description, which is the text the model reads security
- Tool “list_change_orders” rewrote its description, which is the text the model reads security
- Tool “list_contacts” rewrote its description, which is the text the model reads security
- Tool “list_cost_codes” rewrote its description, which is the text the model reads security
- Tool “list_cost_items” rewrote its description, which is the text the model reads security
- Tool “list_daily_logs” rewrote its description, which is the text the model reads security
- Tool “list_estimates” rewrote its description, which is the text the model reads security
- Tool “list_expenses” rewrote its description, which is the text the model reads security
- Tool “list_inspections” rewrote its description, which is the text the model reads security
- Tool “list_invoices” rewrote its description, which is the text the model reads security
- Tool “list_leads” rewrote its description, which is the text the model reads security
- Tool “list_opportunities” rewrote its description, which is the text the model reads security
- Tool “list_payments” rewrote its description, which is the text the model reads security
- Tool “list_project_crew_hours” rewrote its description, which is the text the model reads security
- Tool “list_project_files” rewrote its description, which is the text the model reads security
- Tool “list_project_notes” rewrote its description, which is the text the model reads security
- Tool “list_projects” rewrote its description, which is the text the model reads security
- Tool “list_punchlists” rewrote its description, which is the text the model reads security
- Tool “list_purchase_orders” rewrote its description, which is the text the model reads security
- Tool “list_rfis” rewrote its description, which is the text the model reads security
- Tool “list_schedule_tasks” rewrote its description, which is the text the model reads security
- Tool “list_service_tickets” rewrote its description, which is the text the model reads security
- Tool “list_sub_contracts” rewrote its description, which is the text the model reads security
- Tool “list_submittals” rewrote its description, which is the text the model reads security
- Tool “list_time_cards” rewrote its description, which is the text the model reads security
- Tool “list_todos” rewrote its description, which is the text the model reads security
- Tool “list_work_orders” rewrote its description, which is the text the model reads security
- Tool “record_inspection_result” rewrote its description, which is the text the model reads security
- Tool “record_payment” rewrote its description, which is the text the model reads security
- Tool “remove_estimate_items” rewrote its description, which is the text the model reads security
- Tool “send_change_order” rewrote its description, which is the text the model reads security
- Tool “send_estimate” rewrote its description, which is the text the model reads security
- Tool “send_invoice” rewrote its description, which is the text the model reads security
- Tool “update_change_order” rewrote its description, which is the text the model reads security
- Tool “update_daily_log” rewrote its description, which is the text the model reads security
- Tool “update_estimate” rewrote its description, which is the text the model reads security
- Tool “update_invoice” rewrote its description, which is the text the model reads security
- Tool “update_project” rewrote its description, which is the text the model reads security
- Tool “update_schedule_task” rewrote its description, which is the text the model reads security
- Tool “update_service_ticket_status” rewrote its description, which is the text the model reads security
- Tool “update_todo” rewrote its description, which is the text the model reads security
- Tool “update_work_order_status” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 68
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 24 Oct 2026 · Probed https://cotlet.dev/mcp/v1/contractor-foreman
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cotlet.dev | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6afd7585ee8e24a40f5683c10835ec990a8 |
| SANs: *.cotlet.dev, cotlet.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of cotlet.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| cotlet.dev. | present | 2371 | 13 | Verified |
| cotlet.dev. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cotlet.dev/mcp/v1/contractor-foreman | Verified | 200 | |
| http (plaintext) | http://cotlet.dev/mcp/v1/contractor-foreman | HTTPS enforced | 301 | https://cotlet.dev/mcp/v1/contractor-foreman |
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 →
update_invoice Update invoice ~131
Changes an invoice's status, invoice date, due date or description. Sets only the fields you pass. Statuses: draft, submitted (sent to the customer, payments can be recorded), on_hold, paid, denied, write_off. Contractor Foreman needs a due date on every change, so an invoice without one needs due_date in the same call. Nobody is emailed. send_invoice does that.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| due_date | string | – | – |
| invoice_date | string | – | – |
| invoice_id | string | yes | From list_invoices. |
| status | string | – | – |
No output schema declared.
No examples provided.
update_project Update project ~177
Change a project's name, stage, type, address, dates or description. Changes only the fields you pass and returns the project as get_project shows it. A completed project drops out of list_projects unless include_completed is true. Editing the schedule can move the project dates again. Nothing reaches the customer, so this tool runs without asking.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| description | string | – | – |
| end_date | string | – | – |
| name | string | – | – |
| project_id | string | yes | project_id from list_projects. |
| start_date | string | – | – |
| state | string | – | – |
| status | string | – | New stage, e.g. started or completed. |
| street | string | – | – |
| street2 | string | – | – |
| type | string | – | – |
| zip | string | – | – |
No output schema declared.
No examples provided.
update_schedule_task Update schedule task ~205
Change the name, dates, length or percent complete of a task on the project schedule. Changes one task and returns it as the schedule shows it afterwards. start_date alone moves the task and keeps its length; end_date or duration_days change the length. Tasks that depend on it are not moved: check depends_on in list_schedule_tasks and move them too. The project's start and end dates follow the schedule. A schedule edit reaches nobody outside your company and one more call undoes it, so this tool runs without asking.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_days | integer | – | New length in days, from the start. |
| end_date | string | – | New last day. |
| name | string | – | – |
| percent_complete | number | – | – |
| project_id | string | yes | project_id from list_projects. |
| start_date | string | – | New first day. Alone, it moves the task and keeps its length. |
| task_id | string | yes | task_id from list_schedule_tasks. |
No output schema declared.
No examples provided.
update_service_ticket_status Update service ticket status ~133
Moves a service ticket to scheduled, en route, checked in, completed, closed and so on. Sets the status of a Contractor Foreman service ticket as the status field on its page does: unscheduled, scheduled, en_route, checked_in, requires_followup, canceled, completed or closed. The app's own en-route and completion emails to the customer are separate buttons and are not sent. Completed moves the service date to today, as the app does. Returns the ticket as saved.
| Name | Type | Req | Description |
|---|---|---|---|
| service_ticket_id | integer | yes | service_ticket_id from list_service_tickets. |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_todo Update to-do ~159
Change a to-do's name, description, due date, priority or status, e.g. mark it complete. Changes only the fields you pass and returns the to-do as get_todo shows it. status complete closes it, open reopens it. Assignees and checklist items are not changed. Nothing is sent to anyone, so this tool runs without asking.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| due_date | string | – | – |
| due_time | string | – | e.g. 09:00 or 2:30 PM. |
| name | string | – | – |
| priority | string | – | – |
| status | string | – | complete closes the to-do. |
| todo_id | string | yes | todo_id from list_todos. |
No output schema declared.
No examples provided.
update_work_order_status Update work order status ~94
Moves a work order to open, estimating, submitted, approved, canceled or completed. Sets the status of a Contractor Foreman work order as the status field on its page does. The status in the answer is the label the company uses for it. Nobody is emailed. Returns the work order as saved.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | yes | – |
| work_order_id | integer | yes | work_order_id from list_work_orders. |
No output schema declared.
No examples provided.
How do I install the Contractor Foreman by Cotlet MCP server?
Contractor Foreman by Cotlet is a hosted endpoint at https://cotlet.dev/mcp/v1/contractor-foreman, 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 · cotlet.dev
claude mcp add --transport http dev-cotlet-contractor-foreman 'https://cotlet.dev/mcp/v1/contractor-foreman'
What is the Contractor Foreman by Cotlet MCP server?
Contractor Foreman by Cotlet is an MCP server listed in the public MCP registry as dev.cotlet/contractor-foreman. Projects, estimates, daily logs and invoices in Contractor Foreman. This page covers its hosted endpoint (https://cotlet.dev/mcp/v1/contractor-foreman).
Is the Contractor Foreman by Cotlet MCP server safe to use?
Contractor Foreman by Cotlet scores 68 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 Contractor Foreman by Cotlet MCP server expose?
Contractor Foreman by Cotlet exposes 106 tools: cotlet_whoami, cotlet_apps, cotlet_request_apps, cotlet_get_call, cotlet_upload_file, and 101 more. Their descriptions and schemas cost roughly 14,404 tokens of context every time the server is loaded.
Does the Contractor Foreman by Cotlet MCP server require authentication?
No. We connected to Contractor Foreman by Cotlet without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Contractor Foreman by Cotlet MCP server still maintained?
Contractor Foreman by Cotlet is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.