Borker MCP server
xyz.borker/mcpborker.xyzstreamable-httpv1.0.0Scanned
Plan, draft and schedule social posts in your own voice, with your review before anything goes out.
14 tools: 1 can delete or cancel things, 1 do something that can't be undone, 5 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 4
- Can send data out · 3
- 1 finding
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Borker MCP server can do
The Borker MCP server is published by borker.xyz, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: delete_content), do things that cannot be undone, such as sending, paying or publishing (supply_entry) and create or change data (5 tools: create_content_draft, generate_content, update_content, request_media_upload and 1 more). 7 tools only read.
1 tool reads private data (list_channels); 4 tools bring in text other people can write (list_channels, get_schedule, get_stats and 1 more); 3 tools can send data out of your system (create_content_draft, supply_entry and update_content). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Last scanned Nov 21, 2026, version 1.0.0.
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 1Claude Code: deny
delete_contentDelete a content item (any state except published — published items are immutable).No findings
Why it is in this group
- The name "delete_content" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a content item (any state except published — published items are immutable). Cancels a scheduled external post best-effort first.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
Can't be undone 1Claude Code: ask
supply_entrySend one build-log entry: a piece of work the person did and confirmed is worth sharing.Can send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send one build-log entry: a piece of work the person did and confirmed is worth sharing. source is a handle such as build-log; the first entry for a handle creates that source in the workspace (shown as 'Build log' on the Sources page), and a handle already used by one of the workspace's feeds is refused with validation_error naming source. No AI runs and no generation credit is used at supply. A supply places nothing: the entry arrives not yet planned. A source paces its new entries by default: Borker's night run places each new entry, oldest day first, on the next free posting day, and the destination it lands on decides the voice. The person can switch pacing off in Settings, Sources, and then plans entries themselves. Borker writes each post on its day and holds it for review. Pass kind (finding, decision, ship or reversal) and context (background for the writer, never posted) when you have them, and skillVersion to name your version. Answers {id, position, state, kind, context, planned, notPlanned, paces, destinations}: position is the entry's place in the series by happenedAt; a new entry is not_yet_planned with planned and notPlanned null; paces is true when the night run will place it. Pass externalId so a retry is safe: an entry the source already holds under that externalId is returned unchanged, same id, with state planned and planned {date, time} once it is planned, and nothing is created.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Changes things 5Claude Code: ask
create_content_draftCreate a draft from text YOU supply, for the channel you name in channelId (from list_channels).Can send data outNo findings
Why it is in this group
- The name "create_content_draft" says "create": a word for a change.
What it can reach
- outboundThe input takes a destination (input.channelId): what the tool writes goes there.
Description, as the server wrote it Create a draft from text YOU supply, for the channel you name in channelId (from list_channels). Consumes NO generation credit (no AI runs), but the draft is still checked against the workspace's sensitivity rules and the AI-ism scan, and the returned item says what either found. A draft needs its channel: a call that names none (a platform alone included) fails with validation_error naming the connected channels and their ids, and no draft is created. The draft lands in the review pipeline with a time: pass scheduledAt (ISO, in the future) to pick it, or leave it out and the draft takes its channel's next open time under the workspace's plan; the returned item's scheduledAt says which. Autopilot approves and publishes only the posts Borker plans itself. A post an agent creates stays a draft until a person approves it or the agent schedules it through the API, within the workspace's checks: the length limit and URL credits. A draft marked sensitive comes back with its reasons and is not stopped: a key with write scope can still schedule it. Attach images with media: [{url} | {id}] (a public image URL Borker fetches and checks, or an id from request_media_upload / list_media); a failing image fails the call and no draft is created. For an X THREAD, format the body with the numbered joiner — 1/ first tweet, blank line, 2/ second tweet — each tweet 280 chars or less on a free-tier channel. Separators like --- or **Reply N:** are legacy and are refused at publish.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
generate_contentHave Borker GENERATE a post from a prompt in the workspace's brand voice, one item per channel id in channelIds (get the ids from list_channels).No findings
Why it is in this group
- The name "generate_content" says "generate": a word for a change.
Description, as the server wrote it Have Borker GENERATE a post from a prompt in the workspace's brand voice, one item per channel id in channelIds (get the ids from list_channels). Borker never picks a channel for you: a call that names none fails with validation_error naming the connected channels and their ids, and nothing is generated. Consumes one generation credit per channel against the monthly quota (free on BYOK plans). Fails with generation_limit when the quota is exhausted.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
request_media_uploadGet an image into Borker so a draft can carry it.No findings
Why it is in this group
- The name "request_media_upload" says "request": a word for a change.
Description, as the server wrote it Get an image into Borker so a draft can carry it. With filename alone it answers {mediaId, uploadUrl, expiresAt}: a signed, single-use upload link good for 15 minutes; send the file to it with an HTTP PUT (curl -T photo.png <uploadUrl>), after which mediaId is attachable as {id} in create_content_draft or update_content. With data (the image as base64, 1MB at most) it stores the image now and answers {media: {id, filename, format, size, createdAt, expiresAt}}. Either way the bytes are validated like an upload from the app: JPEG, PNG, GIF or WebP, 4.5MB at most. An upload nobody attaches is removed after 24 hours.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
schedule_contentApprove (if needed) and schedule an item for publishing.No findings
Why it is in this group
- The name "schedule_content" says "schedule": a word for a change.
Description, as the server wrote it Approve (if needed) and schedule an item for publishing. Pass scheduledAt (ISO, snapped to 5 minutes, future) for a specific time, or publishNow: true to publish on the next cron tick. Omitting both reuses the time the item is already planned for (a draft from create_content_draft has one: the time it was given at creation), and fails with 400 when it has none, in which case send scheduledAt or publishNow. An item with no channel, or on a disconnected one, fails with 400 validation_error naming the cause: give it a connected channel with update_content's channelId first. Scheduling a draft approves it, so a draft whose text trips the AI-ism scan fails with the match list until you repeat the call with acknowledgeAiIsms: true. Autopilot approves and publishes only the posts Borker plans itself. A post an agent creates stays a draft until a person approves it or the agent schedules it through the API, within the workspace's checks: the length limit and URL credits. A draft marked sensitive comes back with its reasons and is not stopped: a key with write scope can still schedule it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
update_contentEdit a draft/pending item's text, move it to another channel with channelId, and/or move it through the review lifecycle: status 'pending' approves a draft, 'draft' un-approves, 'c…Can send data out1 finding
Why it is in this group
- The name "update_content" says "update": a word for a change.
What it can reach
- outboundThe input takes a destination (input.channelId): what the tool writes goes there.
Findings
- Info
The description is 2,120 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ith its reasons and is not stopped: a key with write scope can still schedule it."
Description, as the server wrote it Edit a draft/pending item's text, move it to another channel with channelId, and/or move it through the review lifecycle: status 'pending' approves a draft, 'draft' un-approves, 'cancelled' rejects (optionally with rejectionReason). Approving queues the post: at the scheduledAt you pass (ISO-8601, in the future), else at its planned instant, else at the plan's next open time; the result's scheduledAt says the instant it took, and a scheduledAt that has gone by is refused before anything moves. On a scheduled post, status 'pending' unschedules it (the time is cleared and a held URL credit released); schedule_content moves it instead. A draft with no channel, or on a disconnected one, cannot be approved (400 validation_error naming the cause): give it a connected channel with channelId, in the same call or before. Giving an item the channel its plan slot was waiting for can approve and queue it: a draft an auto-approval voice held only for want of a channel is approved (as this key) when its text still passes auto's checks, and an approved item is queued at its planned time; the returned item's status and scheduledAt say where it landed, and plannedTimePassed: true means it stays approved and needs a new time. With status 'draft' the item is un-approved first and moves as a draft. Published items are immutable. Approving a draft whose text trips the AI-ism scan fails with the match list until you repeat the call with acknowledgeAiIsms: true. A post from a piece (one with sourceUrl) goes out with a link to it where its channel puts links (X: its own last post); linkOverride replaces that link with another https address, '' places none, null lets the workspace's Links in posts switch decide again, and the choice is this post's alone. Autopilot approves and publishes only the posts Borker plans itself. A post an agent creates stays a draft until a person approves it or the agent schedules it through the API, within the workspace's checks: the length limit and URL credits. A draft marked sensitive comes back with its reasons and is not stopped: a key with write scope can still schedule it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
Only reads 7Show 7 read-only tools
get_brandRead the workspace's voice profile: its identity prose (tagline, motto, mission, what it is), the About-you facts (the only claims that may be made about this workspace; the taglin…No findings
Why it is in this group
- The name "get_brand" says "get": a word for reading.
Description, as the server wrote it Read the workspace's voice profile: its identity prose (tagline, motto, mission, what it is), the About-you facts (the only claims that may be made about this workspace; the tagline and mission are claims too and are not repeated inside the facts), the standing rules for how the writing sounds, and the subjects to avoid. Use this to write in-character, and never assert anything about the workspace that the facts and the prose do not state.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_contentFetch one content item by id, including its status, channel and its voice, topic, title (Paragraph), and full text.No findings
Why it is in this group
- The name "get_content" says "get": a word for reading.
Description, as the server wrote it Fetch one content item by id, including its status, channel and its voice, topic, title (Paragraph), and full text.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_scheduleRead how the workspace is scheduled: config (timezone, approval mode, per-voice gate settings under voices.you and voices.brand, which apply by each channel's voice from list_chann…Reads text others writeNo findings
Why it is in this group
- The name "get_schedule" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
Description, as the server wrote it Read how the workspace is scheduled: config (timezone, approval mode, per-voice gate settings under voices.you and voices.brand, which apply by each channel's voice from list_channels, and the match threshold a source item must clear), cadence (one row per connected channel: its voice, how often it posts and whether that pulse is on) and planned (the plan items for the coming 14 days: channel, target date and time, state, and the content id once a post is written).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
get_statsWorkspace content analytics over a rolling window: per-channel post balance by status, pipeline depth, source mix, AI-ism flag rate, and generation quota usage.Reads text others writeNo findings
Why it is in this group
- The name "get_stats" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it Workspace content analytics over a rolling window: per-channel post balance by status, pipeline depth, source mix, AI-ism flag rate, and generation quota usage. Use it to spot starved channels or a thin pipeline.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_channelsList the workspace's connected social channels (X, LinkedIn, Threads, Bluesky, Farcaster, Paragraph) with their ids, handles, subscription tier and voice ('personal' speaks as the …Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_channels" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "thread": it reads messages.
- untrusted-inputThe description's first sentence says "list" and "thread": it reads messages, which other people can write.
Description, as the server wrote it List the workspace's connected social channels (X, LinkedIn, Threads, Bluesky, Farcaster, Paragraph) with their ids, handles, subscription tier and voice ('personal' speaks as the founder, 'brand' as the company; get_schedule's voices.you governs personal channels and voices.brand the brand ones). Use the channel ids when creating or generating content.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_contentList content items newest-first with cursor pagination.No findings
Why it is in this group
- The name "list_content" says "list": a word for reading.
Description, as the server wrote it List content items newest-first with cursor pagination. Filter by status (draft/pending/scheduled/publishing/published/failed/cancelled/all), channelId, or source. Returns items plus nextCursor.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
list_mediaList the workspace's uploads that no post has taken yet (id, filename, format, size, createdAt, expiresAt), newest first.Reads text others writeNo findings
Why it is in this group
- The name "list_media" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it List the workspace's uploads that no post has taken yet (id, filename, format, size, createdAt, expiresAt), newest first. Pass an id as {id} in create_content_draft or update_content to attach it. Each is removed 24 hours after upload unless attached.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
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.
12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__borker__list_channels"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
- Infoupdate_content
The description is 2,120 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ith its reasons and is not stopped: a key with write scope can still schedule it."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http borker https://borker.xyz/api/v1/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http borker https://borker.xyz/api/v1/mcp --header 'Authorization: <your-authorization>'Run 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__borker__list_channels",
"mcp__borker__get_brand",
"mcp__borker__get_schedule",
"mcp__borker__get_stats",
"mcp__borker__list_content",
"mcp__borker__get_content",
"mcp__borker__list_media"
],
"ask": [
"mcp__borker__create_content_draft",
"mcp__borker__supply_entry",
"mcp__borker__generate_content",
"mcp__borker__update_content",
"mcp__borker__request_media_upload",
"mcp__borker__schedule_content"
],
"deny": [
"mcp__borker__delete_content"
]
}
}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 borker. Review it before you use it.
Capability tags behind 7 rules
- mcp__borker__list_channels private-data, untrusted-input
- mcp__borker__get_schedule untrusted-input
- mcp__borker__get_stats untrusted-input
- mcp__borker__create_content_draft outbound
- mcp__borker__supply_entry outbound
- mcp__borker__update_content outbound
- mcp__borker__list_media untrusted-input
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/xyz.borker/mcp/verify?hash=81ae7b4e87718e3de442243721d0cd146c48b7322e423b0ad607e5c785a7c2fe" | jq -e '.changed == false'Pinned hash 81ae7b4e8771, from Nov 21, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/xyz.borker/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/xyz.borker/mcp)Source: MCP Registry. Synced Nov 21, 2026, 21:18 UTC.
Borker MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Borker MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Borker MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_content.
Can the Borker MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: supply_entry.
What tools does the Borker MCP server have?
- 14 tools: 1 destructive, 1 irreversible, 5 write, 7 read. delete_content, supply_entry, create_content_draft, generate_content, update_content, request_media_upload, schedule_content, list_channels and 6 more.
Does the Borker MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_content_draft, supply_entry and update_content.
Has the Borker MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.