# Famly MCP by usefulapi (remote · famly.usefulapi.io)

Review Famly sites, staff, invoices and payments through its public API.

- Trust score: 18/100 (low)
- Change this week: −41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `famly.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-famly/famly.md), [page](https://verifymcp.io/servers/io-usefulapi-famly/famly)

## Channel facts

- Endpoint: `https://famly.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Famly MCP by usefulapi server?

Famly MCP by usefulapi is a hosted endpoint at https://famly.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-famly 'https://famly.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-famly": {
      "url": "https://famly.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-famly": {
      "type": "http",
      "url": "https://famly.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-famly]
url = "https://famly.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-famly": {
      "type": "remote",
      "url": "https://famly.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-famly --url 'https://famly.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-famly:
    url: "https://famly.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-famly": {
      "Transport": "http",
      "Url": "https://famly.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-famly -t streamable-http -u 'https://famly.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-famly": {
      "type": "http",
      "url": "https://famly.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 62, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “compare_staff_hours”
- [functional] New prompt “inspect_staff_check_in_records”
- [functional] New prompt “review_invoice_totals_and_due_dates”
- [functional] New prompt “review_payment_activity”
- [functional] New prompt “review_room_staffing_ratios”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.2.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.2 → 1.1.0

### 2026-10-30 (score 59)

First indexed and scored.

## MCP tools (12)

### `famly_list_sites` (~59 tokens)

List sites

Site IDs and titles accessible to this API token. Sites are currently not paginated by Famly. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `organizationId` (string)
- `siteIds` (array)

### `famly_list_groups` (~49 tokens)

List groups

Room/group IDs, titles, institution IDs and staffing ratios for the requested site sets. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `siteSetIds` (array, required)

### `famly_list_employees` (~115 tokens)

List employees

Staff directory and employment dates. No home address, birth date, gender, telephone or photographs. Continue using next, including after an empty page. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `employeeIds` (array)
- `includeFuture` (boolean)
- `includePast` (boolean)
- `next` (string): Opaque next cursor from the previous page. Omit for the first page.
- `pageSize` (integer)
- `siteIds` (array, required)

### `famly_list_invoices` (~97 tokens)

List invoices

Invoice IDs, numbers, totals and dates, excluding line descriptions, child records and PDF links. One page per call. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `createdDateRange` (object)
- `invoiceDateRange` (object)
- `nextToken` (string): Opaque next cursor from the previous page. Omit for the first page.
- `siteIds` (array, required)

### `famly_get_invoices` (~49 tokens)

Get invoices by ID

Invoice summaries for known invoice IDs: numbers, totals, dates and bill payer IDs. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `invoiceIds` (array, required)

### `famly_list_payments` (~119 tokens)

List payments

Payment amounts, dates, method, currency and transaction status. Excludes notes, bank details, child records and payment metadata. One page per call. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `createdDateRange` (object)
- `includeDeleted` (boolean)
- `nextToken` (string): Opaque next cursor from the previous page. Omit for the first page.
- `pageSize` (integer)
- `paymentDateRange` (object)
- `siteIds` (array, required)

### `famly_list_purchases` (~108 tokens)

List purchases

Ad-hoc purchase IDs, status, totals and invoice IDs, excluding child records and booking details. With a date range request one site at a time. One page per call. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `nextToken` (string): Opaque next cursor from the previous page. Omit for the first page.
- `pageSize` (integer)
- `purchaseDateRange` (object)
- `siteIds` (array, required)

### `famly_list_account_codes` (~52 tokens)

List account codes

Accounting code IDs, titles and references for the requested sites. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `includeDeleted` (boolean)
- `siteIds` (array, required)

### `famly_list_bill_payers` (~96 tokens)

List bill payers

Billing identities, names, balances and billing references. Excludes bank accounts, social security numbers, contact details, notes and child records. One page per call. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `includeDeleted` (boolean)
- `nextToken` (string): Opaque next cursor from the previous page. Omit for the first page.
- `siteIds` (array, required)

### `famly_list_work_tags` (~49 tokens)

List work tags

Staff work-tag IDs, names, colour and payroll codes for a site set. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `siteSetId` (string, required)

### `famly_get_staff_hours_totals` (~123 tokens)

Get staff hours totals

Staff contracted, attended, scheduled and break minutes plus differences. Excludes leave categories, health information and notes. Date range maximum 365 days; one page per call. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `dateRange` (object, required)
- `employeeIds` (array)
- `groupIds` (array)
- `next` (string): Opaque next cursor from the previous page. Omit for the first page.
- `pageSize` (integer)
- `siteSetId` (string, required)

### `famly_list_employee_checkins` (~113 tokens)

List employee check-ins

Staff check-in/out timestamps and work-tag IDs. Excludes manager notes and all child check-ins. Famly may return the full date range when nextToken is omitted: narrow the range. If next is returned, pass it as nextToken. Uses the Famly Public API; results depend on token permissions.

Input parameters:

- `SiteSetId` (string, required)
- `nextToken` (string): Opaque next cursor from the previous page. Omit for the first page.
- `range` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-famly/famly#diagnostics

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 59

## Common questions

### What is the Famly MCP by usefulapi server?

Famly MCP by usefulapi is listed in the public MCP registry as io.usefulapi/famly. Review Famly sites, staff, invoices and payments through its public API. This page covers its hosted endpoint (https://famly.usefulapi.io/mcp).

### Is the Famly MCP by usefulapi server safe to use?

Famly MCP by usefulapi scores 18 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 Famly MCP by usefulapi server expose?

Famly MCP by usefulapi exposes 12 tools: famly_list_sites, famly_list_groups, famly_list_employees, famly_list_invoices, famly_get_invoices, and 7 more. Their descriptions and schemas cost roughly 1,029 tokens of context every time the server is loaded.

### Does the Famly MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Famly MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Famly MCP by usefulapi server still maintained?

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

### What did VerifyMCP test on the Famly MCP by usefulapi server?

VerifyMCP ran 4 checks on Famly MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Famly MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://famly.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/famly/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-famly/famly.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-famly/famly/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-famly/famly.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-famly/famly