# Borker (remote · borker.xyz)

Plan, draft and schedule social posts in your own voice, with your review before anything goes out.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `borker.xyz`: 62/100 (this document), [markdown](https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp.md), [page](https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp)

## Channel facts

- Endpoint: `https://borker.xyz/api/v1/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-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_content).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3669 tokens (~262/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**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 15 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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 Borker MCP server?

Borker is a hosted endpoint at https://borker.xyz/api/v1/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 xyz-borker-mcp 'https://borker.xyz/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-borker-mcp": {
      "url": "https://borker.xyz/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-borker-mcp": {
      "type": "http",
      "url": "https://borker.xyz/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-borker-mcp]
url = "https://borker.xyz/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-borker-mcp": {
      "type": "remote",
      "url": "https://borker.xyz/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-borker-mcp --url 'https://borker.xyz/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-borker-mcp:
    url: "https://borker.xyz/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-borker-mcp": {
      "Transport": "http",
      "Url": "https://borker.xyz/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-borker-mcp -t streamable-http -u 'https://borker.xyz/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-borker-mcp": {
      "type": "http",
      "url": "https://borker.xyz/api/v1/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-21 (score 62)

First indexed and scored.

## MCP tools (14)

### `list_channels` (~91 tokens)

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.

Input parameters:

- `platform` (string): Optional platform filter

### `get_brand` (~100 tokens)

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.

### `get_schedule` (~109 tokens)

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).

### `get_stats` (~66 tokens)

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.

Input parameters:

- `days` (integer): Window in days (default 30)

### `list_content` (~118 tokens)

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.

Input parameters:

- `channelId` (string)
- `cursor` (string): Opaque cursor from a previous page
- `limit` (integer)
- `source` (string): One of api, manual, news_reactive, redistribute, daily_generation, build_log
- `status` (string): Status filter, or 'all' (default)

### `get_content` (~46 tokens)

Fetch one content item by id, including its status, channel and its voice, topic, title (Paragraph), and full text.

Input parameters:

- `id` (string, required): Content item id (UUID)

### `create_content_draft` (~670 tokens)

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.

Input parameters:

- `body` (string, required): The post text
- `channelId` (string): The channel the draft is for, from list_channels. Required.
- `channelIds` (array): Accepted as an alternative to channelId, but a draft targets ONE channel — pass exactly one id. To post to several channels, use generate_content.
- `idempotencyKey` (string): Optional, up to 255 characters, your own choice (a UUID works). Send the same key when you retry a call that timed out or failed in transit: within 24 hours the retry returns the draft the first call…
- `media` (array): Images to attach, in publish order. Each entry is {url} (a public https image URL Borker fetches and validates: JPEG, PNG, GIF or WebP, 4.5MB at most) or {id} (an upload id from request_media_upload…
- `scheduledAt` (string): ISO timestamp in the future for when the draft should go out once approved. Omit it and the draft takes its channel's next open time.
- `title` (string): Paragraph only: the blog title, which is a separate field from the body. Set it or the essay publishes as 'Untitled'. Ignored on other platforms.
- `topic` (string)

### `supply_entry` (~800 tokens)

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.

Input parameters:

- `body` (string, required): What happened, in full: at least 40 characters, enough for a post to be written from it.
- `context` (string): Optional, up to 600 characters: what was going on, why it mattered, who it is for. Background for Borker's writer only; it is never posted verbatim.
- `destinations` (array): Optional: the channel ids from list_channels the entry goes to, each once. Name one by default, and several only when the entry plainly belongs on more than one. The night run writes one post per nam…
- `externalId` (string): Optional, up to 255 characters, your own stable id for the entry (e.g. session:7c1d#12). Send the same one when you retry.
- `happenedAt` (string, required): The date the work happened, e.g. 2026-08-23, or a full ISO timestamp. Orders the series.
- `kind` (string): Optional: what kind of beat the entry is. finding: something found out. decision: a decision made. ship: something shipped. reversal: something taken back or changed. Borker shapes the post by it.
- `media` (array): Optional: at most one image for the entry, {url} or {id} as create_content_draft takes them. Borker keeps it until the entry's day and puts it on every post written from the entry. A failing image fa…
- `skillVersion` (string): Optional, up to 20 characters: the version of the skill or agent sending the entry, e.g. 0.3.0. Borker keeps the last one on the source with when it arrived.
- `source` (string, required): The handle of the source, e.g. build-log, up to 80 characters. Send the same handle for every entry of one series.
- `title` (string, required): The entry's title, up to 200 characters.

### `generate_content` (~148 tokens)

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.

Input parameters:

- `channelIds` (array, required): The channels to write for, one post per id, from list_channels. Required: an empty or missing list is refused.
- `prompt` (string, required): What the post should be about

### `update_content` (~805 tokens)

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 credit…

Input parameters:

- `acknowledgeAiIsms` (boolean): Approve the draft even though the AI-ism scan matched. Send it only after showing the matches to the operator, or rewrite the text instead.
- `channelId` (string): Move the draft to this channel (from list_channels): connected, and on the draft's own platform
- `content` (string): Replacement post text
- `id` (string, required): Content item id (UUID)
- `linkOverride` (string|null): The link a post from a piece goes out with: another https address, '' for none, or null to let the workspace's Links in posts switch decide again. Draft or pending items with a sourceUrl only.
- `media` (array): Images to attach, in publish order. Each entry is {url} (a public https image URL Borker fetches and validates: JPEG, PNG, GIF or WebP, 4.5MB at most) or {id} (an upload id from request_media_upload…
- `rejectionReason` (string)
- `scheduledAt` (string): With status 'pending' on a draft: the ISO-8601 instant (in the future) to queue the approved post at. Leave it out and the post takes its planned instant, else the plan's next open time.
- `status` (string)

### `request_media_upload` (~230 tokens)

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.

Input parameters:

- `data` (string): Optional: the image bytes as base64, 1MB at most. Leave it out to get an upload link for a bigger file.
- `filename` (string, required): The name the upload is listed under in list_media, e.g. launch.png

### `list_media` (~67 tokens)

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.

### `schedule_content` (~317 tokens)

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.

Input parameters:

- `acknowledgeAiIsms` (boolean): Schedule the draft even though the AI-ism scan matched. Send it only after showing the matches to the operator, or rewrite the text instead.
- `id` (string, required): Content item id (UUID)
- `publishNow` (boolean)
- `scheduledAt` (string): ISO timestamp

### `delete_content` (~46 tokens)

Delete a content item (any state except published — published items are immutable). Cancels a scheduled external post best-effort first.

Input parameters:

- `id` (string, required): Content item id (UUID)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp#diagnostics

## Score history

- 2026-11-21: 62

## Common questions

### What is the Borker MCP server?

Borker is an MCP server listed in the public MCP registry as xyz.borker/mcp. Plan, draft and schedule social posts in your own voice, with your review before anything goes out. This page covers its hosted endpoint (https://borker.xyz/api/v1/mcp).

### Is the Borker MCP server safe to use?

Borker scores 62 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 Borker MCP server expose?

Borker exposes 14 tools: list_channels, get_brand, get_schedule, get_stats, list_content, and 9 more. Their descriptions and schemas cost roughly 3,613 tokens of context every time the server is loaded.

### Does the Borker MCP server require authentication?

No. We connected to Borker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Borker MCP server still maintained?

Borker is still listed as active in the MCP registry. We last reached this channel on 21 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 Borker MCP server?

VerifyMCP ran 12 checks on Borker, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about Borker: Stability. One category scores 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://borker.xyz/api/v1/mcp
- Authorisation metadata: https://borker.xyz/.well-known/oauth-protected-resource/api/v1/mcp
- Website: https://www.borker.xyz/mcp
- Changelog RSS feed: https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-borker-mcp/api-v1-mcp
