# io.usefulapi/folk (remote · folk.usefulapi.io)

Read and write Folk CRM people, companies, groups and notes.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

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

## Channel facts

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

## 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-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1774 tokens (~126/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/folk MCP server?

io.usefulapi/folk is a hosted endpoint at https://folk.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-folk 'https://folk.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-folk": {
      "type": "http",
      "url": "https://folk.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-10-03 (score 77, +1)

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

### 2026-10-02 (score 76, 0)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 76, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 71, +53)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (14)

### `folk_get_current_user` (~31 tokens)

Get current user

Get the user associated with the current Folk API key. Folk REST: GET /v1/users/me.

### `folk_list_users` (~82 tokens)

List users

List users in the Folk workspace (id, name, email) — useful for resolving owner ids. Folk REST: GET /v1/users.

Input parameters:

- `cursor` (string): Pagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
- `limit` (integer): Results per page (1-100, default 20).

### `folk_list_people` (~146 tokens)

List people

List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people.

Input parameters:

- `combinator` (string): How to combine multiple filters — 'and' (all must match) or 'or' (any). Default 'and'.
- `cursor` (string): Pagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
- `filter` (object): Structured filter: attribute → operator → value, expanded to filter[attribute][operator]=value query keys. Example: {"firstName":{"eq":"John"}}.
- `limit` (integer): Results per page (1-100, default 20).

### `folk_get_person` (~41 tokens)

Get person

Get a single person (contact) by id. Folk REST: GET /v1/people/{id}.

Input parameters:

- `id` (string, required): The person id.

### `folk_list_companies` (~145 tokens)

List companies

List/filter companies. Supports cursor pagination and structured filters. Folk REST: GET /v1/companies.

Input parameters:

- `combinator` (string): How to combine multiple filters — 'and' (all must match) or 'or' (any). Default 'and'.
- `cursor` (string): Pagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
- `filter` (object): Structured filter: attribute → operator → value, expanded to filter[attribute][operator]=value query keys. Example: {"firstName":{"eq":"John"}}.
- `limit` (integer): Results per page (1-100, default 20).

### `folk_get_company` (~38 tokens)

Get company

Get a single company by id. Folk REST: GET /v1/companies/{id}.

Input parameters:

- `id` (string, required): The company id.

### `folk_list_groups` (~77 tokens)

List groups

List groups in the Folk workspace (ids needed to place people/companies). Folk REST: GET /v1/groups.

Input parameters:

- `cursor` (string): Pagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
- `limit` (integer): Results per page (1-100, default 20).

### `folk_list_notes` (~168 tokens)

List notes

List notes, optionally scoped to an entity or filtered by full text and creation date. Folk REST: GET /v1/notes.

Input parameters:

- `created_after` (string): Only notes created after this ISO 8601 timestamp — maps to query createdAfter.
- `created_before` (string): Only notes created before this ISO 8601 timestamp — maps to query createdBefore.
- `cursor` (string): Pagination cursor — pass the value from a previous page's pagination.nextLink to fetch the next page.
- `entity_id` (string): Restrict to notes on this entity (person/company) id — maps to query key entity.id.
- `limit` (integer): Results per page (1-100, default 20).
- `query` (string): Full-text search over note content.

### `folk_get_note` (~38 tokens)

Get note

Get a single note by id. Folk REST: GET /v1/notes/{id}.

Input parameters:

- `id` (string, required): The note id.

### `folk_create_person` (~221 tokens)

Create person

Create a new person (contact). All fields are optional. Folk REST: POST /v1/people.

Input parameters:

- `addresses` (array): Postal addresses.
- `birthday` (string): Birthday, formatted YYYY-MM-DD.
- `companies` (array): Companies this person is linked to (array of {id} or {name}).
- `customFieldValues` (object): Custom field values, keyed by field.
- `description` (string): Freeform description / notes.
- `emails` (array): Email addresses.
- `firstName` (string): First name.
- `fullName` (string): Full name (if not split into first/last).
- `gender` (string): Gender — one of Male, Female, Unknown, Other.
- `groups` (array): Groups to add this person to (array of {id}).
- `jobTitle` (string): Job title.
- `lastName` (string): Last name.
- `phones` (array): Phone numbers.
- `urls` (array): URLs (website, social, etc.).

### `folk_update_person` (~251 tokens)

Update person

Update fields on an existing person. Only provided fields are changed; list-valued fields (emails, phones, groups, companies, etc.) REPLACE the existing values. Folk REST: PATCH /v1/people/{id}.

Input parameters:

- `addresses` (array): Replace the person's addresses.
- `birthday` (string): Birthday, formatted YYYY-MM-DD.
- `companies` (array): Replace the person's linked companies (array of {id} or {name}).
- `customFieldValues` (object): Custom field values, keyed by field.
- `description` (string): Freeform description / notes.
- `emails` (array): Replace the person's email addresses.
- `firstName` (string): First name.
- `fullName` (string): Full name.
- `gender` (string): Gender — one of Male, Female, Unknown, Other.
- `groups` (array): Replace the person's groups (array of {id}).
- `id` (string, required): The person id to update.
- `jobTitle` (string): Job title.
- `lastName` (string): Last name.
- `phones` (array): Replace the person's phone numbers.
- `urls` (array): Replace the person's URLs.

### `folk_create_company` (~197 tokens)

Create company

Create a new company. `name` is required. Folk REST: POST /v1/companies.

Input parameters:

- `addresses` (array): Postal addresses.
- `customFieldValues` (object): Custom field values, keyed by field.
- `description` (string): Freeform description / notes.
- `emails` (array): Email addresses.
- `employeeRange` (string): Employee-count range bucket.
- `foundationYear` (string|number): Year the company was founded.
- `fundingRaised` (string|number): Total funding raised.
- `groups` (array): Groups to add this company to (array of {id}).
- `industry` (string): Industry.
- `lastFundingDate` (string): Date of last funding round, formatted YYYY-MM-DD.
- `name` (string, required): The company name (required).
- `phones` (array): Phone numbers.
- `urls` (array): URLs (website, social, etc.).

### `folk_update_company` (~224 tokens)

Update company

Update fields on an existing company. Only provided fields are changed; list-valued fields REPLACE the existing values. Folk REST: PATCH /v1/companies/{id}.

Input parameters:

- `addresses` (array): Replace the company's addresses.
- `customFieldValues` (object): Custom field values, keyed by field.
- `description` (string): Freeform description / notes.
- `emails` (array): Replace the company's email addresses.
- `employeeRange` (string): Employee-count range bucket.
- `foundationYear` (string|number): Year the company was founded.
- `fundingRaised` (string|number): Total funding raised.
- `groups` (array): Replace the company's groups (array of {id}).
- `id` (string, required): The company id to update.
- `industry` (string): Industry.
- `lastFundingDate` (string): Date of last funding round, formatted YYYY-MM-DD.
- `name` (string): The company name.
- `phones` (array): Replace the company's phone numbers.
- `urls` (array): Replace the company's URLs.

### `folk_create_note` (~115 tokens)

Create note

Create a note attached to an entity (person/company). Folk REST: POST /v1/notes.

Input parameters:

- `content` (string, required): The note content.
- `entity_id` (string, required): Id of the entity (person/company) to attach the note to — maps to body entity:{id}.
- `parent_note_id` (string): Id of a parent note to reply under — maps to body parentNote:{id}.
- `visibility` (string, required): Note visibility — 'public' (workspace) or 'private' (you).

## Diagnostics

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

## Score history

- 2026-10-03: 77
- 2026-10-02: 76
- 2026-10-01: 76
- 2026-09-30: 71
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/folk MCP server?

io.usefulapi/folk is an MCP server listed in the public MCP registry as io.usefulapi/folk. Read and write Folk CRM people, companies, groups and notes. This page covers its hosted endpoint (https://folk.usefulapi.io/mcp).

### Is the io.usefulapi/folk MCP server safe to use?

io.usefulapi/folk scores 77 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 io.usefulapi/folk MCP server expose?

io.usefulapi/folk exposes 14 tools: folk_get_current_user, folk_list_users, folk_list_people, folk_get_person, folk_list_companies, and 9 more. Their descriptions and schemas cost roughly 1,774 tokens of context every time the server is loaded.

### Does the io.usefulapi/folk MCP server require authentication?

Yes. io.usefulapi/folk 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 io.usefulapi/folk MCP server still maintained?

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

## Links

- Remote endpoint: https://folk.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-folk/folk.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-folk/folk.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-folk/folk