io.usefulapi/folk
REMOTE · FOLK.USEFULAPI.IO · SCANNED OCT 3
Read and write Folk CRM people, companies, groups and notes.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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
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.
remote · folk.usefulapi.io
claude mcp add --transport http io-usefulapi-folk 'https://folk.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-folk": {
"url": "https://folk.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-folk": {
"type": "http",
"url": "https://folk.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-folk] url = "https://folk.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-folk": {
"type": "remote",
"url": "https://folk.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-folk --url 'https://folk.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-folk:
url: "https://folk.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-folk": {
"Transport": "http",
"Url": "https://folk.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-folk -t streamable-http -u 'https://folk.usefulapi.io/mcp'
{
"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.
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.
- 3 Oct 26 +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.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
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 3 Oct 2026 · Probed https://folk.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 folk.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://folk.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://folk.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://folk.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://folk.usefulapi.io/mcp |
| Authorisation server | https://folk.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://folk.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://folk.usefulapi.io/mcp | HTTPS enforced | 301 | https://folk.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 →
folk_create_company Create company ~197
Create a new company. `name` is required. Folk REST: POST /v1/companies.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The company name (required). |
| phones | array | – | Phone numbers. |
| urls | array | – | URLs (website, social, etc.). |
No output schema declared.
No examples provided.
folk_create_note Create note ~115
Create a note attached to an entity (person/company). Folk REST: POST /v1/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The note content. |
| entity_id | string | yes | 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 | yes | Note visibility — 'public' (workspace) or 'private' (you). |
No output schema declared.
No examples provided.
folk_create_person Create person ~221
Create a new person (contact). All fields are optional. Folk REST: POST /v1/people.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.). |
No output schema declared.
No examples provided.
folk_get_company Get company ~38
Get a single company by id. Folk REST: GET /v1/companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The company id. |
No output schema declared.
No examples provided.
folk_get_current_user Get current user ~31
Get the user associated with the current Folk API key. Folk REST: GET /v1/users/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
folk_get_note Get note ~38
Get a single note by id. Folk REST: GET /v1/notes/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The note id. |
No output schema declared.
No examples provided.
folk_get_person Get person ~41
Get a single person (contact) by id. Folk REST: GET /v1/people/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The person id. |
No output schema declared.
No examples provided.
folk_list_companies List companies ~145
List/filter companies. Supports cursor pagination and structured filters. Folk REST: GET /v1/companies.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
folk_list_groups List groups ~77
List groups in the Folk workspace (ids needed to place people/companies). Folk REST: GET /v1/groups.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
folk_list_notes List notes ~168
List notes, optionally scoped to an entity or filtered by full text and creation date. Folk REST: GET /v1/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
folk_list_people List people ~146
List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
folk_list_users List users ~82
List users in the Folk workspace (id, name, email) — useful for resolving owner ids. Folk REST: GET /v1/users.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
folk_update_company Update company ~224
Update fields on an existing company. Only provided fields are changed; list-valued fields REPLACE the existing values. Folk REST: PATCH /v1/companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
folk_update_person Update person ~251
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.