Bilflo MCP by usefulapi
REMOTE · BILFLO.USEFULAPI.IO
Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category CRM and Sales
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability84
- 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
- Tool/resource definitions use about 2432 tokens (~93/item across 26 items; 26 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% of tool parameters carry a description.Partial
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bilflo_list_job_pay_bill_items" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 27 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
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 61
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 25 Oct 2026 · Probed https://bilflo.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 bilflo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://bilflo.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://bilflo.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://bilflo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bilflo.usefulapi.io/mcp |
| Authorisation server | https://bilflo.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bilflo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/bilflo/ |
| http (plaintext) | http://bilflo.usefulapi.io/mcp | Inconclusive | 302 | http://bilflo.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 →
bilflo_create_client Create client ~78
WRITE: creates a new client (customer) in Bilflo with the given business name and returns its id. It is visible to the whole staffing company and used for billing, so check bilflo_list_clients first to avoid a duplicate. POST /v1/Clients.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | Business name of the new client. |
No output schema declared.
No examples provided.
bilflo_get_client Get client ~46
One client with its addresses and contacts. GET /v1/Clients/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id (from bilflo_list_clients). |
No output schema declared.
No examples provided.
bilflo_get_company_setting Get company setting ~62
One of the company's lookup lists: workers_comp_codes, payment_terms, remittances, burden_settings, benefit_rules, states or pay_bill_items. GET /v1/CompanySettings/{setting}.
| Name | Type | Req | Description |
|---|---|---|---|
| setting | string | yes | Which list to read. |
No output schema declared.
No examples provided.
bilflo_get_contract_job Get contract job ~82
One contract job (a contractor placed with a client): client, contractor, title, start/end dates, status, overtime rule, timecard method, per-diem/expense/sick-time flags, workers' comp code and burden. GET /v1/ContractJobs/{jobId}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_get_contractor Get contractor ~86
One contractor: profile (name, email, phone, address, W2/1099), jobs, checks paid, work status, benefit settings and custom fields. Social security number, date of birth and bank details are removed from the reply. GET /v1/Users/contractors/{contractorId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contractor_id | integer | yes | Bilflo contractor id. |
No output schema declared.
No examples provided.
bilflo_get_direct_hire Get direct hire ~63
One direct hire (a permanent placement): header, fee/split data, contacts and custom fields as Bilflo returns them. GET /v1/DirectHires/{jobId}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo direct hire job id. |
No output schema declared.
No examples provided.
bilflo_get_job_custom_fields Get job custom fields ~48
The custom field values of one contract job. GET /v1/ContractJobs/{jobId}/customFields.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_get_team_member Get team member ~65
One back-office team member (staffing company user): profile, roles and compensation settings. Government ids and bank details are removed. GET /v1/Users/teamMember/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| team_member_id | integer | yes | Bilflo team member (user) id. |
No output schema declared.
No examples provided.
bilflo_list_client_addresses List client addresses ~48
The addresses (work sites and billing addresses) of one client. GET /v1/Clients/addresses/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
No output schema declared.
No examples provided.
bilflo_list_client_agreements List client agreements ~49
The agreements (billing terms) on file for one client. GET /v1/Clients/agreements/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
No output schema declared.
No examples provided.
bilflo_list_client_contacts List client contacts ~57
The contacts (people at the client: name, title, phone, email, active flag) of one client. GET /v1/Clients/contact/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
No output schema declared.
No examples provided.
bilflo_list_client_contract_pos List client contract POs ~54
The contract purchase orders of one client (PO numbers and amounts used for billing). GET /v1/Clients/contractPOs/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
No output schema declared.
No examples provided.
bilflo_list_client_invoice_groups List client invoice groups ~53
The contract invoice groups of one client (which jobs are invoiced together). GET /v1/Clients/contractInvoiceGroups/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | yes | Bilflo client id. |
No output schema declared.
No examples provided.
bilflo_list_clients List clients ~182
The staffing company's clients (the customers contractors are placed with): id, business name, client code, phone, active flag. Each row carries the number of addresses and contacts; set include_details for the full address and contact lists. Bilflo returns every client at once, so this tool filters and pages the list itself. GET /v1/Clients.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | Only active clients. |
| include_details | boolean | – | Include each client's addresses and contacts (large; use with a small limit). |
| limit | integer | – | Rows to return, 1-200 (default 50). |
| offset | integer | – | Rows to skip (default 0). Bilflo does not page, so the list is cut here. |
| search | string | – | Only clients whose business name or client code contains this text (case-insensitive). |
No output schema declared.
No examples provided.
bilflo_list_custom_field_items List custom field items ~82
The selectable items of one custom list field (id from bilflo_list_custom_fields). Items of a field named like personal data (SSN, date of birth, bank account, password) are not shown. GET /v1/CustomFields/items.
| Name | Type | Req | Description |
|---|---|---|---|
| custom_field_id | integer | yes | Custom field id (from bilflo_list_custom_fields). |
No output schema declared.
No examples provided.
bilflo_list_custom_fields List custom fields ~46
The company's custom fields (active and inactive) with type, requiredness per service offering and, for list fields, the selectable items. GET /v1/CustomFields.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bilflo_list_job_approvers List job approvers ~50
Who approves the timecards of one contract job. GET /v1/ContractJobs/{jobId}/approvers.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_list_job_pay_bill_items List job pay/bill items ~63
The pay and bill rates (pay/bill items such as Regular, Overtime) of one contract job. GET /v1/ContractJobs/{jobId}/payBillItems.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_list_job_purchase_orders List job purchase orders ~48
The purchase orders attached to one contract job. GET /v1/ContractJobs/{jobId}/purchaseOrders.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_list_overtime_rules List overtime rules ~42
The company's overtime rules (id, name, state). Use the ids with bilflo_update_contract_job. GET /v1/OvertimeRules.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bilflo_reopen_contract_job Reopen contract job ~127
WRITE: reopens a terminated contract job (like the Open Job button): the job becomes active again, the end date is cleared, the contractor is made active and the missing timecards from the reopen date's week are created. Fails if the job is not terminated or the company plan has no room for another active job. POST /v1/ContractJobs/{jobId}/reopen.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Bilflo contract job id. |
| reopen_date | string | yes | Date to reopen from, yyyy-mm-dd (not before the job start). |
No output schema declared.
No examples provided.
bilflo_run_report Run custom report ~99
Run one of the company's saved custom reports and return its rows. Report parameters are report specific key/value pairs, for example {"Start": "2026-01-01", "End": "2026-01-31"}. Reads data only. POST /v1/Reports/{reportId}/Execute.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | Report parameters as key/value pairs. |
| report_id | integer | yes | Bilflo custom report id. |
No output schema declared.
No examples provided.
bilflo_terminate_contract_job Terminate contract job ~103
WRITE: ends a contract job on the given date (the contractor stops being placed with the client; no more timecards are expected after it). Affects payroll and invoicing. A terminated job can be brought back with bilflo_reopen_contract_job. POST /v1/ContractJobs/terminate.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day of the job, yyyy-mm-dd. |
| job_id | integer | yes | Bilflo contract job id. |
No output schema declared.
No examples provided.
bilflo_update_client Update client ~122
WRITE: changes only the client fields you pass (business name, client code, phone, fax, active flag); the rest stay as they are. Setting is_active=false deactivates the client. PATCH /v1/Clients/{clientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | – |
| client_code | string | – | – |
| client_id | integer | yes | Bilflo client id. |
| fax | string | – | – |
| is_active | boolean | – | false deactivates the client, true reactivates it. |
| phone | string | – | – |
No output schema declared.
No examples provided.
bilflo_update_contract_job Update contract job ~225
WRITE: changes only the contract job fields you pass (title, overtime rule, workers' comp code, burden, per-diem/expenses/sick-time/meal-period flags); the rest stay as they are. Pay and bill rates change payroll and invoices, so confirm values with the user. Client, contractor, dates and status cannot be changed here. PATCH /v1/ContractJobs/{jobId}.
| Name | Type | Req | Description |
|---|---|---|---|
| burden_manual | number | – | Manual burden value. |
| is_allow_skip_lunch | boolean | – | – |
| is_expenses_enabled | boolean | – | – |
| is_per_diem_enabled | boolean | – | – |
| is_sick_time_enabled | boolean | – | – |
| is_waive_meal_period | boolean | – | – |
| job_id | integer | yes | Bilflo contract job id. |
| job_title | string | – | – |
| overtime_rule_id | integer | – | Overtime rule id (bilflo_list_overtime_rules). |
| workers_comp_code_id | integer | – | Workers' comp code id (bilflo_get_company_setting workers_comp_codes). |
No output schema declared.
No examples provided.
bilflo_update_contractor Update contractor contact details ~196
WRITE: changes only the contractor contact fields you pass (name, title, email, phone, address, company); the rest stay as they are. Tax, bank, social security number and activation are not changeable here. PATCH /v1/Users/contractors/{contractorId}.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| address2 | string | – | – |
| city | string | – | – |
| contractor_company | string | – | The contractor's own company name (1099). |
| contractor_id | integer | yes | Bilflo contractor id. |
| email_address | string | – | – |
| first_name | string | – | – |
| last_name | string | – | – |
| middle_name | string | – | – |
| phone | string | – | – |
| phone_ext | string | – | – |
| state_code | string | – | Two-letter state code. |
| title | string | – | – |
| zip_code | string | – | – |
No output schema declared.
No examples provided.
How do I install the Bilflo MCP by usefulapi server?
Bilflo MCP by usefulapi is a hosted endpoint at https://bilflo.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 · bilflo.usefulapi.io
claude mcp add --transport http io-usefulapi-bilflo 'https://bilflo.usefulapi.io/mcp'
What is the Bilflo MCP by usefulapi server?
Bilflo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bilflo. Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them. This page covers its hosted endpoint (https://bilflo.usefulapi.io/mcp).
Is the Bilflo MCP by usefulapi server safe to use?
Bilflo MCP by usefulapi scores 61 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 Bilflo MCP by usefulapi server expose?
Bilflo MCP by usefulapi exposes 26 tools: bilflo_list_clients, bilflo_get_client, bilflo_list_client_contacts, bilflo_list_client_addresses, bilflo_list_client_agreements, and 21 more. Their descriptions and schemas cost roughly 2,176 tokens of context every time the server is loaded.
Does the Bilflo MCP by usefulapi server require authentication?
Yes. Bilflo MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Bilflo MCP by usefulapi server still maintained?
Bilflo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.