Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bill4Time MCP by usefulapi

REMOTE · BILL4TIME.USEFULAPI.IO

Read Bill4Time clients, projects, time entries, expenses, invoices, payments, users and contacts.

62 Trust /100

Last scanned (20 minutes ago)

Scores higher than 46% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability70
  • 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 2170 tokens (~271/item across 8 items; 8 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% 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
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Changelog

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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “getting_started” functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 12 Oct 26 57

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://bill4time.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 bill4time.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 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://bill4time.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://bill4time.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://bill4time.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://bill4time.usefulapi.io/mcp
Authorisation server https://bill4time.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bill4time.usefulapi.io/mcp Redirected 302 https://usefulapi.io/bill4time/
http (plaintext) http://bill4time.usefulapi.io/mcp Inconclusive 302 http://bill4time.usefulapi.io/mcp
MCP tools · 8 exposed · ~1,955 tokens

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 →

Tool Tokens
bill4time_list_clients ~234

List clients (id, name, billing name, email, phone, city, account manager, status, billing rate type, currency). Filter by status, exact client name, id or creation date. Street addresses and tax ids are not returned. GET /clients.

NameTypeReqDescription
client_namestring–Exact client name (case rules are Bill4Time's).
created_afterstring–Clients created on or after this date.
created_beforestring–Clients created on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
statusstring––
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

bill4time_list_contacts ~188

List contacts: name, email, work and mobile phone, city, status, creation date. Filter by status, id or creation date. Street addresses, home phone and notes are not returned. GET /contacts.

NameTypeReqDescription
created_afterstring–Contacts created on or after this date.
created_beforestring–Contacts created on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
statusstring––
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

bill4time_list_expenses ~323

List expenses: client, project, user, expense date, cost and sell price, quantity, type, billing status, invoice id, public description. Filter by client, project, user, invoice, expense date range, billing status or exact expense type. Private notes are not returned unless include_private_notes is set. GET /expenses.

NameTypeReqDescription
billing_statusstring––
client_idinteger––
date_fromstring–Expenses dated on or after this date.
date_tostring–Expenses dated on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
expense_typestring–Exact expense type name.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
include_private_notesboolean–Also return the private/internal notes (default false). Only set it when the user asks for internal notes.
invoice_idinteger–Only expenses on this invoice.
project_idinteger–A project id, or -1 for expenses that belong to no project.
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
topinteger–Records to return, 1-100 (default 25).
user_idinteger––

No output schema declared.

No examples provided.

bill4time_list_invoices ~246

List invoices: client, project, invoice date, status (prebill or finalized), paid status, totals (invoice, labor, expense, late fee), terms and notes. Filter by status, paid status, client, project, id or invoice date range. GET /invoices.

NameTypeReqDescription
client_idinteger––
date_fromstring–Invoices dated on or after this date.
date_tostring–Invoices dated on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
paid_statusstring––
project_idinteger––
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
statusstring––
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

bill4time_list_payments ~233

List payments: client, project, amount, date, type, method, public note. Filter by client, project, id or payment date range. Check numbers are not returned; the private note only with include_private_notes. GET /payments.

NameTypeReqDescription
client_idinteger––
date_fromstring–Payments dated on or after this date.
date_tostring–Payments dated on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_private_notesboolean–Also return the private/internal notes (default false). Only set it when the user asks for internal notes.
project_idinteger––
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

bill4time_list_projects ~231

List projects (matters): id, name, client, status, billing method, rate overrides, assigned user, created/closed/due dates. Filter by status, billing method, client, id or creation date. GET /projects.

NameTypeReqDescription
billing_methodstring––
client_idinteger–Only projects of this client.
created_afterstring–Projects created on or after this date.
created_beforestring–Projects created on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
statusstring––
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

bill4time_list_time_entries ~320

List time entries: client, project, user, entry date, billable and labor time, billable amount, rate, activity, ABA litigation code, billing status, invoice id, public description. Filter by client, project, user, invoice, entry date range or billing status. Private notes and contractor pay rates are not returned unless include_private_notes is set. GET /timeEntries.

NameTypeReqDescription
activity_typestring–Exact activity type name.
billing_statusstring––
client_idinteger––
date_fromstring–Entries dated on or after this date.
date_tostring–Entries dated on or before this date.
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
include_private_notesboolean–Also return the private/internal notes (default false). Only set it when the user asks for internal notes.
invoice_idinteger–Only entries on this invoice.
project_idinteger––
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
topinteger–Records to return, 1-100 (default 25).
user_idinteger––

No output schema declared.

No examples provided.

bill4time_list_users ~180

List the firm's users: name, email, user type, status, department, position, billing and overtime rate. Birth dates, addresses, phone numbers and contractor pay rates are not returned. Filter by status or id. GET /users.

NameTypeReqDescription
descendingboolean–Sort descending (newest or highest first). Default ascending.
idinteger–Only the record with this id.
include_custom_fieldsboolean–Also return the custom fields (default false).
skipinteger–Records to skip (default 0). Pass the previous reply's next_skip to read the next page.
sortstring–Field to sort by (default: Bill4Time's own order).
statusstring––
topinteger–Records to return, 1-100 (default 25).

No output schema declared.

No examples provided.

Install

How do I install the Bill4Time MCP by usefulapi server?

Bill4Time MCP by usefulapi is a hosted endpoint at https://bill4time.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 · bill4time.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-bill4time 'https://bill4time.usefulapi.io/mcp'
Common questions

What is the Bill4Time MCP by usefulapi server?

Bill4Time MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bill4time. Read Bill4Time clients, projects, time entries, expenses, invoices, payments, users and contacts. This page covers its hosted endpoint (https://bill4time.usefulapi.io/mcp).

Is the Bill4Time MCP by usefulapi server safe to use?

Bill4Time MCP by usefulapi scores 62 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 Bill4Time MCP by usefulapi server expose?

Bill4Time MCP by usefulapi exposes 8 tools: bill4time_list_clients, bill4time_list_projects, bill4time_list_time_entries, bill4time_list_expenses, bill4time_list_invoices, and 3 more. Their descriptions and schemas cost roughly 1,955 tokens of context every time the server is loaded.

Does the Bill4Time MCP by usefulapi server require authentication?

Yes. Bill4Time 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 Bill4Time MCP by usefulapi server still maintained?

Bill4Time MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.