Home / MCP registry index / io.usefulapi/bilflo

Bilflo MCP by usefulapi

io.usefulapi/bilflo in the official MCP registry. Endpoint https://bilflo.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read Bilflo clients, contract jobs, contractors and reports; update jobs, terminate or reopen them.

We read its 26 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "bilflo": {
      "url": "https://bilflo.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"bilflo","type":"http","url":"https://bilflo.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

bilflo_list_clients bilflo_get_client bilflo_list_client_contacts bilflo_list_client_addresses bilflo_list_client_agreements bilflo_list_client_contract_pos bilflo_list_client_invoice_groups bilflo_get_contract_job bilflo_list_job_pay_bill_items bilflo_list_job_approvers bilflo_list_job_purchase_orders bilflo_get_job_custom_fields bilflo_get_direct_hire bilflo_get_contractor bilflo_get_team_member bilflo_list_overtime_rules bilflo_get_company_setting bilflo_list_custom_fields bilflo_list_custom_field_items bilflo_run_report bilflo_create_client bilflo_update_client bilflo_update_contract_job bilflo_terminate_contract_job bilflo_reopen_contract_job bilflo_update_contractor

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 632a8b23f0c893d7. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-bilflo/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-bilflo)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.