Folk MCP by usefulapi
io.usefulapi/folkusefulapi.iostreamable-httpv1.40.4Scanned
Read and write Folk CRM people, companies, groups and notes.
14 tools: 5 can delete or cancel things and 9 only read.
- Reads private data · 5
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Folk MCP by usefulapi can do
The Folk MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (5 tools: folk_create_person, folk_update_person, folk_create_company, folk_update_company and 1 more). 9 tools only read.
5 tools read private data (folk_list_users, folk_list_people, folk_get_person and 2 more); 1 tool brings in text other people can write (folk_list_users).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Deletes or cancels 5Claude Code: deny
folk_create_companyCreate a new company.No findings
Why it is in this group
- The name "folk_create_company" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new company. `name` is required. Folk REST: POST /v1/companies.
Annotations the server declares
- title: Create company
- destructiveHint: true
folk_create_noteCreate a note attached to an entity (person/company).No findings
Why it is in this group
- The name "folk_create_note" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a note attached to an entity (person/company). Folk REST: POST /v1/notes.
Annotations the server declares
- title: Create note
- destructiveHint: true
folk_create_personCreate a new person (contact).No findings
Why it is in this group
- The name "folk_create_person" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Create a new person (contact). All fields are optional. Folk REST: POST /v1/people.
Annotations the server declares
- title: Create person
- destructiveHint: true
folk_update_companyUpdate fields on an existing company.No findings
Why it is in this group
- The name "folk_update_company" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Update fields on an existing company. Only provided fields are changed; list-valued fields REPLACE the existing values. Folk REST: PATCH /v1/companies/{id}.
Annotations the server declares
- title: Update company
- destructiveHint: true
folk_update_personUpdate fields on an existing person.No findings
Why it is in this group
- The name "folk_update_person" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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}.
Annotations the server declares
- title: Update person
- destructiveHint: true
Only reads 9Show 9 read-only tools
folk_get_companyGet a single company by id.No findings
Why it is in this group
- The name "folk_get_company" says "get": a word for reading.
Description, as the server wrote it Get a single company by id. Folk REST: GET /v1/companies/{id}.
Annotations the server declares
- title: Get company
- readOnlyHint: true
folk_get_current_userGet the user associated with the current Folk API key.No findings
Why it is in this group
- The name "folk_get_current_user" says "get": a word for reading.
Description, as the server wrote it Get the user associated with the current Folk API key. Folk REST: GET /v1/users/me.
Annotations the server declares
- title: Get current user
- readOnlyHint: true
folk_get_noteGet a single note by id.Reads private dataNo findings
Why it is in this group
- The name "folk_get_note" says "get": a word for reading.
What it can reach
- private-dataThe name "folk_get_note" says "get" and "note": it reads notes.
- private-dataThe description's first sentence says "get" and "note": it reads notes.
Description, as the server wrote it Get a single note by id. Folk REST: GET /v1/notes/{id}.
Annotations the server declares
- title: Get note
- readOnlyHint: true
folk_get_personGet a single person (contact) by id.Reads private dataNo findings
Why it is in this group
- The name "folk_get_person" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "contact": it reads contacts.
Description, as the server wrote it Get a single person (contact) by id. Folk REST: GET /v1/people/{id}.
Annotations the server declares
- title: Get person
- readOnlyHint: true
folk_list_companiesList/filter companies.No findings
Why it is in this group
- The name "folk_list_companies" says "list": a word for reading.
Description, as the server wrote it List/filter companies. Supports cursor pagination and structured filters. Folk REST: GET /v1/companies.
Annotations the server declares
- title: List companies
- readOnlyHint: true
folk_list_groupsList groups in the Folk workspace (ids needed to place people/companies).No findings
Why it is in this group
- The name "folk_list_groups" says "list": a word for reading.
Description, as the server wrote it List groups in the Folk workspace (ids needed to place people/companies). Folk REST: GET /v1/groups.
Annotations the server declares
- title: List groups
- readOnlyHint: true
folk_list_notesList notes, optionally scoped to an entity or filtered by full text and creation date.Reads private dataNo findings
Why it is in this group
- The name "folk_list_notes" says "list": a word for reading.
What it can reach
- private-dataThe name "folk_list_notes" says "list" and "note": it reads notes.
- private-dataThe description's first sentence says "list" and "note": it reads notes.
Description, as the server wrote it List notes, optionally scoped to an entity or filtered by full text and creation date. Folk REST: GET /v1/notes.
Annotations the server declares
- title: List notes
- readOnlyHint: true
folk_list_peopleList/filter people (contacts).Reads private dataNo findings
Why it is in this group
- The name "folk_list_people" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "contact": it reads contacts.
Description, as the server wrote it List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people.
Annotations the server declares
- title: List people
- readOnlyHint: true
folk_list_usersList users in the Folk workspace (id, name, email) — useful for resolving owner ids.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "folk_list_users" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List users in the Folk workspace (id, name, email) — useful for resolving owner ids. Folk REST: GET /v1/users.
Annotations the server declares
- title: List users
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data5
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://folk.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://folk.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://folk.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://folk.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http folk https://folk.usefulapi.io/mcpclaude mcp add --transport http folk https://folk.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__folk__folk_get_current_user",
"mcp__folk__folk_list_users",
"mcp__folk__folk_list_people",
"mcp__folk__folk_get_person",
"mcp__folk__folk_list_companies",
"mcp__folk__folk_get_company",
"mcp__folk__folk_list_groups",
"mcp__folk__folk_list_notes",
"mcp__folk__folk_get_note"
],
"ask": [],
"deny": [
"mcp__folk__folk_create_person",
"mcp__folk__folk_update_person",
"mcp__folk__folk_create_company",
"mcp__folk__folk_update_company",
"mcp__folk__folk_create_note"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as folk. Review it before you use it.
Capability tags behind 5 rules
- mcp__folk__folk_list_users private-data, untrusted-input
- mcp__folk__folk_list_people private-data
- mcp__folk__folk_get_person private-data
- mcp__folk__folk_list_notes private-data
- mcp__folk__folk_get_note private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/folk/verify?hash=7dc10f35fb6579dce91152ef51c44b544ff7bc657995f4d9c408d73deb72e0bc" | jq -e '.changed == false'Pinned hash 7dc10f35fb65, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/folk/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/folk)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Folk MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Folk MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 14 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Folk MCP by usefulapi delete data?
- Yes. 5 tools can delete, cancel or revoke something: folk_create_person, folk_update_person, folk_create_company, folk_update_company and folk_create_note.
Can the Folk MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Folk MCP by usefulapi have?
- 14 tools: 5 destructive, 9 read. folk_create_person, folk_update_person, folk_create_company, folk_update_company, folk_create_note, folk_get_current_user, folk_list_users, folk_list_people and 6 more.
Does the Folk MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Folk MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Folk MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.