# BlackOps Center (remote · mcp.blackopscenter.com)

Ask your BlackOps brain, capture notes, draft posts, and run your Sorties from any MCP client.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.blackopscenter.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp.md), [page](https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.blackopscenter.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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**: 94/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 8787 tokens (~313/item across 28 items; 28 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the BlackOps Center MCP server?

BlackOps Center is a hosted endpoint at https://mcp.blackopscenter.com/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 blackopscenter-blackops-mcp 'https://mcp.blackopscenter.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "blackopscenter-blackops-mcp": {
      "url": "https://mcp.blackopscenter.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "blackopscenter-blackops-mcp": {
      "type": "http",
      "url": "https://mcp.blackopscenter.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.blackopscenter-blackops-mcp]
url = "https://mcp.blackopscenter.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "blackopscenter-blackops-mcp": {
      "type": "remote",
      "url": "https://mcp.blackopscenter.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add blackopscenter-blackops-mcp --url 'https://mcp.blackopscenter.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  blackopscenter-blackops-mcp:
    url: "https://mcp.blackopscenter.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "blackopscenter-blackops-mcp": {
      "Transport": "http",
      "Url": "https://mcp.blackopscenter.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add blackopscenter-blackops-mcp -t streamable-http -u 'https://mcp.blackopscenter.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "blackopscenter-blackops-mcp": {
      "type": "http",
      "url": "https://mcp.blackopscenter.com/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 81, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-20 (score 81, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-19 (score 80, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-18 (score 80, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-17 (score 79, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-16 (score 79, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-15 (score 78, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-14 (score 78, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (28)

### `get_me` (~31 tokens)

Get Me

Get current user profile, accessible sites, and account info. Call this first to discover which sites you can manage.

### `get_brand_voice` (~123 tokens)

Get Brand Voice

Get canonical brand voice for the site. Pass domain or site_id to target a specific site; omit to use the auth default. Always pass the same domain/site_id used with patch_brand_voice so both tools operate on the same record. Also returns pronoun_mode and approved_facts when set, empty otherwise — the account-aware check_brand_voice guidance.

Input parameters:

- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `get_recent_notes` (~90 tokens)

Get Recent Notes

Get recent notes/context for the site. Recommended before creating tweets/posts.

Input parameters:

- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `limit` (integer): How many recent notes to return. Defaults to 5, capped at 20.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `get_note` (~136 tokens)

Get Note

Get a single note by UUID, slug, or title. Use this to read the full content of individual notes, including brain source notes referenced in a brain manifest. VAULT SYNC STATUS: the response carries a sync block — status is "queued" (commit in flight), "synced" (landed; see file_path + commit_sha), "failed" (see last_error; the sweeper retries), or "none" (no vault target). This is how you confirm a deferred post_notes commit landed; post_notes itself can only report "queued".

Input parameters:

- `id` (string, required): Note UUID, slug, or title

### `get_ai_context` (~131 tokens)

Get AI Context

Get AI context pack for content generation. Recommended before creating tweets/posts. Also returns default_site (id, domain, and the rule "unless the user names another site, writes go to <domain>") when the account has one.

Input parameters:

- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `query` (string): Optional topic hint for the content you are about to write. Accepted for compatibility; the context pack is not filtered by it.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `post_notes` (~1110 tokens)

Post Notes

Create a BlackOps note, or update one in place when source_id resolves to a known note. Requires content_markdown (or transcript/conversation). Prefer this over post_notes_write.

source_id is the idempotency key (content hash, your own string, or note UUID): repeat calls update instead of forking. Know the note? Use patch_notes. A SLUG_COLLISION warning ("my-note-2") means an intended update forked.

Site is OPTIONAL (explicit → account default intake → only site); pass domain/site_id only for a note tied to one site.

BRAINS: pass a brain's UUID as brain_id; the server derives site/target/folder and skips auto-routing. Never infer site_id or guess target_id from topic. brain_alignment confirms the compile picks it up.

WITHOUT brain_id, a site opted into auto-routing either files the note into a brain's Triage lane (routing.band "auto", filed: true) or saves it unfiled with needs_brain_choice: show its question, up to 3 options (one-line reason each) and the also entries as ONE single-choice question, then call resolve_with with their pick. Never pick a brain yourself. Sites not opted in save unfiled. suggest_brain: true is a separate keyword match (suggested_brain).

Unknown TAGS still apply with an UNKNOWN_TAG warning; ask the user before propose_note_tags.

VAULT SYNC is deferred: sync is { status: "queued" } and the note IS saved, so do NOT re-call. Confirm a commit with get_note; wait_for_sync: true returns commitSha/filePath inline. override_folder_path bypasses the taxonomy; a brain's source_folder_path still wins.

phase/priority/position are Big Board columns (priority High|Medium|Low).

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `allow_secrets` (boolean): Set true to store content that looks like a credential (API key, token, private key), which is otherwise refused with SECRET_DETECTED. Only when the user asked to store that exact value.
- `assign_target` (boolean): Default true: when target_id is omitted, pick the best-matching vault target for the note. False leaves the note without one (or keeps its existing target).
- `auto_sync` (boolean): Default true: commit the note to its vault target after saving. False saves it without syncing.
- `brain_id` (string): UUID of the brain this note belongs to. The server derives the site, vault target and folder from it.
- `confirm` (boolean): Pass true to confirm this action once the user has approved it.
- `content_markdown` (string): Note body in Markdown. Required unless transcript or conversation is given.
- `conversation` (object): A chat conversation to save as the note: { id?, title?, messages[] }. Used when content_markdown is not given.
- `conversation_id` (string): Id of the chat conversation this note came from, stored on the note.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `excerpt` (string|null): Short summary shown in note lists and search. null clears it.
- `metadata` (object): Free-form key/value data stored with the note.
- `note_type` (string): Note type: general, project, initiative, daily, reference, task or skill. Also steers which vault folder it syncs to.
- `override_folder_path` (string): Vault folder to write the note into, bypassing the workspace folder rules. A brain's own source folder still wins.
- `phase` (string): Big Board phase column for the note, free text (max 100 characters).
- `position` (string): Big Board rank within its column. Usually left unset; a board sets it on drag.
- `priority` (string): Big Board priority: High, Medium or Low.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `source_id` (string): Idempotency key. A repeat call with the same source_id updates that note instead of creating a new one. A content hash, your own string, or a note UUID.
- `status` (string): Note status: active (default), draft or archived.
- `suggest_brain` (boolean): Default false. True checks whether the note matches a brain and returns it as suggested_brain, without filing it.
- `tags` (array): Tags for the note. Tags outside the site vocabulary still apply, with an UNKNOWN_TAG warning.
- `target_id` (string|null): UUID of the vault target to sync the note to. Omit to let the server pick one (see assign_target).
- `title` (string): Note title, up to 200 characters.
- `transcript` (string): Raw transcript text to save as the note when there is no Markdown body.
- `triage_state` (string): Set to 'pending' to file this note into a brain's Triage lane (unreviewed) instead of committing it to the vault right away. Leave unset for an ordinary note.
- `wait_for_sync` (boolean): Default false. True holds the response until the vault commit lands, so it returns commit_sha and file_path.

### `get_posts` (~144 tokens)

Get Posts

List blog posts for a site. Filter by status (draft, published) with pagination support.

Input parameters:

- `cursor` (string): Accepted for compatibility; results are not paginated by cursor, so use limit.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `limit` (integer): Max posts to return. Defaults to 50, capped at 200.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `status` (string): Only posts with this status, e.g. "draft", "published" or "scheduled". Omit for all.

### `post_posts` (~556 tokens)

Post Posts

Create a blog draft. Before calling, fetch get_me + get_brand_voice (+ get_ai_context/get_recent_notes). Site scope is automatic for a single-site account; pass domain or site_id to target one, and an account with several sites is asked to choose rather than guessed at. Do NOT repeat the title in the content body — no leading "# Title" and no first line restating it, or it renders twice, since the title field prints above the content. Start with the intro paragraph or the first ## heading. The response carries links.review_url: that is where a person previews and edits the draft, so hand the user that link, never the admin editor URL or a raw preview URL.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `confirm` (boolean): Pass true to confirm this action once the user has approved it.
- `content` (string, required): Blog post body in Markdown. Do NOT pass a fully HTML-formatted document — block-level HTML tags (e.g. <p>, <h2>) appear as literal text. Custom styled HTML (cards, tables, CSS callouts) must go in a…
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `excerpt` (string): Short summary used as the post description in listings and link previews. Defaults to the title.
- `featured` (boolean): Mark the post as featured on the site. Defaults to false.
- `seo_description` (string): Meta description for search results and link previews.
- `seo_title` (string): Title for search results and link previews, if different from the post title.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `slug` (string): URL slug for the post. Generated from the title when omitted.
- `source` (string): Optional label for where the post came from, stored on the post. "bookmark" files it as a bookmark (tagged bookmark, never featured).
- `status` (string): Post status: "draft" or "published". Publishing needs confirm: true.
- `subtitle` (string): Subtitle/deck shown beneath the title. Populate it whenever the post has a natural subheadline or clarifying phrase.
- `tags` (array): Tags for the post, e.g. ["ai", "nextjs"].
- `title` (string, required): Post title. Printed above the content, so do not repeat it in the body.

### `get_post` (~97 tokens)

Get Post

Fetch a single blog post by slug or UUID, including full content, metadata, and SEO fields. One call — no need to list posts first to resolve a slug.

Input parameters:

- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `id` (string, required): Post UUID or slug.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `patch_posts_by_id` (~527 tokens)

Patch Posts by ID

EDIT ONLY — modifies a post in-place. NEVER call for reading; use post_posts to create. Published edits go live immediately. Always pass base_updated_at (from get_post.updated_at); without it a concurrent edit is silently overwritten. Custom styled HTML needs a richembed fenced block; bare block HTML is escaped. Do NOT include the title in the content body. Response has links.review_url for drafts — give that link to the user.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `base_updated_at` (string): ISO from preceding get_post.updated_at. Server returns 409 CONFLICT with current_updated_at + current_content if post was edited since read; re-read, merge, retry.
- `content` (string): New post body in Markdown. Replaces the whole body. Do not include the title.
- `description` (string): The post's PUBLIC meta description shown in search results and link previews. Overwrites any stored value immediately. THIS IS NOT an edit-comment or reason-for-change field — omit this key entirely…
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `featured` (boolean): Mark or unmark the post as featured.
- `featured_image` (string): URL of the post's hero image.
- `hero_prompt_edited` (string): Custom prompt that will be used on the next hero image generation for this post.
- `id` (string, required): Post UUID or slug to edit.
- `published_at` (string): Publish date, ISO 8601 (e.g. 2026-11-11T09:00:00Z).
- `seo_description` (string): New meta description for search results and link previews.
- `seo_title` (string): New title for search results and link previews.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `slug` (string): New URL slug.
- `status` (string): New status, e.g. "draft" or "published". Setting a scheduled post back to "draft" unschedules it.
- `subtitle` (string): New subtitle shown beneath the title.
- `tags` (array): Replacement tag list.
- `title` (string): New post title.
- `x_discussion_url` (string|null): X post permalink for the post's "Discuss on X" block. null removes it.

### `post_posts_by_id_publish` (~229 tokens)

Post Posts by ID Publish

Publish a draft blog post, making it live on the site. Requires confirm: true. On a 2026-07-28 connection whose client declares form elicitation you may omit it and the user confirms in a dialog; anywhere else, omitting it fails. Publishing a scheduled post publishes it immediately and clears the schedule. Pass override_brand_voice: true to bypass the brand-voice gate when a publish fails that check.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `confirm` (boolean): Pass true to confirm this action once the user has approved it.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `id` (string, required): UUID of the draft post to publish.
- `override_brand_voice` (boolean): Set true to publish even though the post fails the brand-voice check. Recorded on the post.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `post_posts_by_id_schedule` (~248 tokens)

Post Posts by ID Schedule

Schedule a draft blog post for future publishing. Provide a datetime via scheduledFor; the platform publishes the post automatically at that time (checked every 5 minutes). Unschedule by patching status back to "draft"; publish immediately with post_posts_by_id_publish. Requires confirm: true.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `confirm` (boolean, required): Pass true to confirm this action once the user has approved it.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `id` (string, required): UUID of the draft post to schedule.
- `schedule_at` (string): Alias of scheduledFor.
- `scheduledFor` (string): When to publish, ISO 8601 with offset (e.g. 2026-11-12T14:00:00-05:00). One of scheduledFor, scheduled_for or schedule_at is required.
- `scheduled_for` (string): Alias of scheduledFor.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.

### `post_posts_by_id_hero` (~777 tokens)

Post Posts by ID Hero

Generate (or regenerate) a blog post's hero image, or its OG social card — works the same before and after the post exists. Returns the image inline plus its public URL. The fields below cover prompts, references, style, and the commit:false review flow. Rules that span fields: only the title and subtitle may ever appear on an OG card, because given anything else the generator invents its own tagline; an OG card takes NO references unless you name them, since auto-matching used to put a real face on social cards nobody asked to be in; for target:"og" prompt is the VISUAL DIRECTION and still gets OG framing; to anchor a face, mark the photo as a "headshot" via mark_reference_image first.

Input parameters:

- `accept_asset_id` (string): ACCEPT mode, no generation: promote a candidate and attach it. Sets og_image for an OG candidate (og-candidate kind), or featured_image + hero_asset_id for a hero candidate. The field_set key in the…
- `accept_image_url` (string): ACCEPT fallback when only the URL is known — sets featured_image (or og_image when target: "og" is also passed) without asset promotion.
- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `alt_text` (string): ACCEPT mode: override the auto-generated alt text on the accepted asset. Applies to accept_asset_id; ignored on accept_image_url.
- `caller_name` (string): Optional self-reported label for who/what is generating (e.g. an agent name). Shows up in get_hero_history as caller_name — a label you provide, not a verified identity. Omit to default to your accou…
- `commit` (boolean): Default true: apply the image to the post immediately. False generates a review CANDIDATE (kind hero-candidate) and leaves the post untouched.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `id` (string, required): Post UUID
- `include_subtitle` (boolean): OG only. Default true. False renders a title-only card even when the post has a subtitle.
- `include_title_text` (boolean): OG only. Default true: render the title as text on the card. False produces a purely visual card.
- `iteration_prompt` (string): Edit instruction for iterating on a previous hero (e.g. "make the background darker"). Requires source_image_url, which anchors composition.
- `latest_candidate` (boolean): READ mode, no generation: returns the newest un-accepted hero candidate for the post.
- `prompt` (string): Image prompt, auto-generated from the post if omitted. For target:"og", layered on the site share_card_style.
- `reference_image_ids` (array): Curated reference IDs and/or media-library asset IDs (upload_media / list_media). Omitted: reuses the first hero's references, else auto-matches from the prompt. [] uses none.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `source_image_url` (string): URL of the hero to iterate on (a prior result's image_url). Used with iteration_prompt.
- `style` (string): Visual style. Defaults to "modern".
- `subtitle` (string): OG only. Secondary line rendered verbatim beneath the title. Defaults to the post's own subtitle; nothing appears unless passed or stored.
- `target` (string): "hero" (default) sets featured_image; "og" makes the 1200x630 Open Graph card and sets og_image, leaving the hero untouched.

### `post_tweets` (~459 tokens)

Post Tweets

Create a tweet draft. Before calling, fetch get_me + get_brand_voice (+ get_ai_context/get_recent_notes) AND call get_x_accounts for the posting account's max_tweet_length — never assume 280, since Premium/verified accounts go up to 25,000. If max_tweet_length is null the limit is unknown: ask the user rather than defaulting to 280. Site scope is automatic for a single-site account; pass domain or site_id to target one, and an account with several sites is asked to choose rather than guessed at. Requires text or thread. To attach an image, upload with upload_media then call attach_media_to_tweet with the asset_id and this tweet's id. Links to user-owned domains get UTM parameters appended at draft time so the traffic shows up in GA4 instead of as Direct; pass your own if you want explicit campaign slugs. When the tweet distributes a known blog post, pass its post_id (UUID, from get_posts) so the /admin/posts Distribution column links the two automatically — no manual backfill.

Input parameters:

- `account_id` (string): Id of the connected X account to post from. Alternative to account_username.
- `account_username` (string): Username of the connected X account to post from, without @. Alternative to account_id.
- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `description` (string): Internal note about the draft in BlackOps. Not posted.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `post_id` (string): UUID of the blog post this tweet distributes (from get_posts), so the two are linked.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `text` (string): Tweet text for a single tweet. Pass text or thread, not both.
- `thread` (array): A thread, in order: [{ text }, ...]. Pass text or thread, not both.
- `title` (string): Internal title for the draft in BlackOps. Defaults to the start of the first tweet.

### `get_x_accounts` (~193 tokens)

Get X Accounts

List connected X (Twitter) accounts. Search by username or filter by site. Each account record includes premium (boolean) and max_tweet_length (integer) — ALWAYS read these before drafting tweet content. Premium accounts allow up to 25,000 chars; non-premium are limited to 280. If max_tweet_length is null, treat the limit as unknown and ask the user rather than assuming 280.

Input parameters:

- `account_name` (string): Alias of username.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `query` (string): Alias of username.
- `site_id` (string): Site UUID to scope this call to. Alternative to domain.
- `username` (string): Filter accounts by text in the username, display name, account id or site. Case-insensitive. Applies when domain and site_id are omitted.

### `upload_media` (~600 tokens)

Upload Media

Upload media to the site media library. Three modes:

1\. URL mode — pass file_url + filename + content_type. Fetched server-side in one call, no human step. https only, SSRF-guarded on every redirect, capped at 50 MB (images/PDF) or 200 MB (video; bigger video uses the direct-PUT path below). Good for a URL you already have, e.g. from a generation call.

2\. Interactive mode — pass nothing (or just domain/label). Returns { url, token, expires_at }: show the URL; the user uploads on the quick-upload page and clicks "Done". For screenshots, recordings or local files, bulk too. filename/alt_text/title apply to the FIRST asset only.

3\. Claim mode — pass token (from interactive mode). Returns status="completed" with an assets[] array once the user clicks Done, or "pending" while they are still uploading — poll again.

No public URL but your own HTTP client? get_media_upload_url({ domain, filename, content_type }) → { asset_id, upload_url }, PUT your bytes, then finalize_media_upload({ asset_id, domain }). Token only, no browser.

Supported: jpeg, png, webp, gif, mp4, webm, quicktime, application/pdf (quick-upload: video to 1 GB, else 50 MB). Video → media_type "video", no thumbnail. PDF → "document" (thumbnail = page one), the only document type; anything else is rejected.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `alt_text` (string): Alt text for the image. Generated automatically when omitted.
- `content_type` (string): MIME type of the file, e.g. image/png, video/mp4 or application/pdf. URL mode requires it.
- `domain` (string): Site domain to scope this call to (e.g. example.com). Alternative to site_id.
- `file_url` (string): https URL the server downloads the file from (URL mode).
- `filename` (string): File name to store, with extension (e.g. launch-diagram.png). URL mode requires it.
- `kind` (string): Library category for the asset. Defaults to "mcp-upload".
- `label` (string): Interactive mode: a label shown on the upload page, up to 200 characters.
- `size_bytes` (integer): File size in bytes, if known.
- `title` (string): Title for the asset in the media library.
- `token` (string): Token returned by interactive mode. Pass it alone to claim the finished upload (claim mode).
- `ttl_ms` (integer): Interactive mode: how long the upload link stays valid, in milliseconds. Default 15 minutes, min 1 minute, max 1 hour.

### `get_media_upload_url` (~302 tokens)

Get Media Upload URL

Agent-direct upload, no human step. 1: get_media_upload_url({ domain, filename, content_type, size_bytes? }) returns { asset_id, upload_url, public_url, expires_in }. 2: HTTP PUT the raw bytes to upload_url with a matching Content-Type. 3: finalize_media_upload({ asset_id, domain }). For bytes with no public URL, or too big for upload_media URL mode (e.g. video over 200 MB). If the PUT fails with a network error (sandboxed or proxied agent), use upload_media interactive mode instead. Allowed: images, mp4/webm/quicktime, pdf, mp3/wav. Max 20 MB images, 50 MB PDF, 1 GB video. URL expires after expires_in seconds.

Input parameters:

- `alt_text` (string): Alt text for the asset.
- `content_type` (string, required): MIME type you will PUT the bytes with, e.g. video/mp4. Must match the upload.
- `domain` (string, required): Site domain whose media library receives the file (e.g. example.com).
- `filename` (string, required): File name to store, with extension (e.g. demo.mp4).
- `kind` (string): Library category for the asset. Defaults to "mcp-upload".
- `size_bytes` (integer): File size in bytes, if known.
- `title` (string): Title for the asset in the media library.

### `finalize_media_upload` (~182 tokens)

Finalize Media Upload

Finalize a presigned URL media upload. Call after uploading to the upload_url from upload_media, or after PUTting bytes directly to an upload_url minted by get_media_upload_url. Needs only { asset_id, domain } plus the same MCP/API token already on this session — no browser or cookie. Validates the file and processes dimensions/thumbnails — for a PDF that means rasterizing page one into a badged thumbnail. Bytes that are not really a PDF are rejected; a genuine PDF that will not rasterize still finalizes, just without a preview.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `asset_id` (string, required): asset_id returned by get_media_upload_url.
- `domain` (string, required): The same site domain passed to get_media_upload_url.

### `get_media` (~61 tokens)

Get Media

Get details for a single media asset including URL, dimensions, format, and metadata.

Input parameters:

- `domain` (string, required): Site domain that owns the asset (e.g. example.com).
- `id` (string, required): Media asset UUID (from upload_media or list_media).

### `list_brains` (~117 tokens)

List Brains

List all brains accessible to the authenticated user. Returns each brain's id, name, description, aliases, status, note count, last compiled timestamp, and visibility. Match description and aliases to resolve natural-language references (e.g. "restaurant brain"). Brains are site-agnostic — no domain or site_id needed.

Cross-brain retrieval: returns every brain in the account, so an answer about one can draw on another — say so when it does. Private brains are omitted here but stay readable via get_brain by name.

### `get_brain` (~235 tokens)

Get Brain

Get the compiled knowledge map for a brain: a manifest of source notes with IDs and summaries — call get_note for a note's full content. Site-agnostic. Accepts a UUID, slug, name, or alias; no list_brains lookup needed first (call list_brains for a brain not named in your instructions). status: "pending" means it has never compiled — call update_brain to add the first note. To create a new brain, call create_brain. The response's pending_triage_count is how many items are held out of this compile awaiting a list_triage / promote_triage_item / dismiss_triage_item decision.

AMBIGUITY: when a reference matches more than one brain the response is error "ambiguous_brain_ref" with a candidate list and NO brain. Present the candidates to the user and ask which they mean. Do not infer from context, and do not re-call this tool until they answer.

Input parameters:

- `brain_id` (string): Brain UUID
- `brain_name` (string): Brain slug, name, or alias — how the user referred to it

### `update_brain` (~375 tokens)

Update Brain

Add a new note to a brain; the server resolves storage from the brain record (BlackOps for DB-backed brains, a GitHub commit for vault-backed ones). Use this whenever the user says "update the brain", "add this to the brain", or "log this in the brain". Call list_brains first for the brain_id if you do not have it; create_brain makes a new brain. A DB-backed brain recompiles immediately; a vault-backed one on its next compile. Use post_notes_write (with brain_id) only for control over the filename or path. A brain's sanitize rules may hold a write: follow details.sanitize_hold.

Input parameters:

- `agent` (string): Your name, on every write: Duet/<channel name> or Grok Bot/<bot name>.
- `allow_secrets` (boolean): Set true to store content that looks like a credential (API key, token, private key), which is otherwise refused with SECRET_DETECTED. Only when the user asked to store that exact value.
- `brain_id` (string, required): Brain UUID (from list_brains)
- `commit_message` (string): Git commit message.
- `markdown_content` (string, required): Markdown content for the new note to add to the brain
- `note_filename` (string): Filename without .md. Defaults from section_title or the date.
- `sanitize_answer` (object): Only after a SANITIZE_ANSWER_REQUIRED hold: repeat the same call with { hold_id, decisions: { <rule>: "allow" | "block" } } for each rule the hold lists, as the owner answered. Send "block" for every…
- `section_title` (string): Title for this note — used as the filename slug (e.g. "Threads Integration")

### `get_account_context` (~72 tokens)

Get Account Context

Get account context including defaults and publishing context for a domain. The default site (the site writes go to when the user names none) is stated by get_account_settings and get_ai_context (default_site).

Input parameters:

- `domain` (string, required): Site domain to read account and publishing context for (e.g. example.com).

### `list_skills` (~115 tokens)

List Skills

List the account's and built-in skills (slug + description). Call at the START of a task: if one matches the ask, fetch it with get_skill and follow it instead of improvising.

Input parameters:

- `brain_id` (string): Restrict to skills stored in one brain.
- `platform` (string): Only skills that support this host (e.g. "claude", "cursor", "grok"). Skills that declare no platforms always match.
- `tags` (array): Only skills carrying every one of these tags.

### `search` (~144 tokens)

Search

Search BlackOps notes and blog posts. Returns id, title, and url per match; pass an id to fetch for the full text. Generated daily notes (note_type "daily", titled "YYYY-MM-DD · {Name}") do not contain the word "daily" in their title — queries containing "daily" automatically include them via a supplementary typed lookup, but for reliable lookup by context name use list_notes with note_type: "daily" and search: "{name}", or list_daily_note_configs to see which contexts exist.

Input parameters:

- `domain` (string): Site domain. Defaults to the account default site.
- `query` (string, required): Search terms, matched against titles and bodies.

### `fetch` (~44 tokens)

Fetch

Retrieve the full text of one BlackOps note or blog post by its search id.

Input parameters:

- `id` (string, required): Record id from search, e.g. "note:<uuid>".

### `describe_tools` (~154 tokens)

Describe Tools

Discover the rest of the BlackOps tool catalog. This connector surfaces a small default tool set; every other BlackOps capability (pages, video, brains and brain watches, hunts, sorties, LinkedIn/Threads/Medium, GA4/Search Console analytics, and more) is one lookup away. Call with no arguments for the full index of tool names, with query to search, or with names for complete definitions including input_schema. Then invoke any of them with use_tool.

Input parameters:

- `limit` (integer): Max full definitions returned for a query (default 5).
- `names` (array): Exact tool names to fetch full definitions for.
- `query` (string): Keyword search over tool names and descriptions (case-insensitive).

### `use_tool` (~104 tokens)

Use Tool

Invoke any BlackOps catalog tool that is not on the default surface, by name. Arguments are validated against the same schema the tool has natively, and the call runs the identical handler with identical permissions — this is dispatch, not a bypass. Look up names and input schemas with describe_tools first.

Input parameters:

- `args` (object): The tool's arguments, matching the input_schema from describe_tools.
- `name` (string, required): Catalog tool name, exactly as returned by describe_tools.

## Diagnostics

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

## Score history

- 2026-11-21: 81
- 2026-11-20: 81
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 78
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 73

## Common questions

### What is the BlackOps Center MCP server?

BlackOps Center is an MCP server listed in the public MCP registry as io.github.BlackOpsCenter/blackops-mcp. Ask your BlackOps brain, capture notes, draft posts, and run your Sorties from any MCP client. This page covers its hosted endpoint (https://mcp.blackopscenter.com/mcp).

### Is the BlackOps Center MCP server safe to use?

BlackOps Center scores 81 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 BlackOps Center MCP server expose?

BlackOps Center exposes 28 tools: get_me, get_brand_voice, get_recent_notes, get_note, get_ai_context, and 23 more. Their descriptions and schemas cost roughly 7,356 tokens of context every time the server is loaded.

### Does the BlackOps Center MCP server require authentication?

Yes. BlackOps Center 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 BlackOps Center MCP server still maintained?

BlackOps Center 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 BlackOps Center MCP server?

VerifyMCP ran 13 checks on BlackOps Center, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://mcp.blackopscenter.com/mcp
- Repository: https://github.com/BlackOpsCenter/blackops-mcp
- Website: https://www.blackopscenter.com/
- Changelog RSS feed: https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/blackopscenter-blackops-mcp/mcp
