# BlackOps Center

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

- name: io.github.BlackOpsCenter/blackops-mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 81/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.BlackOpsCenter%2Fblackops-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.BlackOpsCenter%2Fblackops-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-2d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 81/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 75 (weight 30)

- pass `tools.descriptions`: every tool has a description
- warn `tools.description_length`: 2 tools have descriptions over 1,024 characters, which crowds the context
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 28 of 28 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: upload_media (idempotentHint); get_media (idempotentHint); get_me (idempotentHint); …
- warn `tools.token_cost`: about 9,887 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`, `stability.new_links`: tool history recorded for 2 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 28, about 9,887 tokens to load them all
- tool set hash: 85b0012a57f8c4bca25e7c6e36b9128b
- tools last changed: 2026-11-12T03:07:35.389Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.BlackOpsCenter/blackops-mcp.svg)](https://protogrid.dev/servers/io.github.BlackOpsCenter/blackops-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-12 `get_account_context` changed (inputSchema)
- 2026-11-12 `update_brain` changed (inputSchema)
- 2026-11-12 `get_media` changed (inputSchema)
- 2026-11-12 `finalize_media_upload` changed (inputSchema)
- 2026-11-12 `get_media_upload_url` changed (inputSchema)
- 2026-11-12 `upload_media` changed (inputSchema)
- 2026-11-12 `get_x_accounts` changed (inputSchema)
- 2026-11-12 `post_tweets` changed (inputSchema)
- 2026-11-12 `post_posts_by_id_hero` changed (inputSchema)
- 2026-11-12 `post_posts_by_id_schedule` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/io.github.BlackOpsCenter%2Fblackops-mcp/changes

## Remotes

- https://mcp.blackopscenter.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (28)

- `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.
- `fetch`: Retrieve the full text of one BlackOps note or blog post by its search id.
- `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.
- `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).
- `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.
- `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.
- `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.
- `get_me`: Get current user profile, accessible sites, and account info. Call this first to discover which sites you can manage.
- `get_media`: Get details for a single media asset including URL, dimensions, format, and metadata.
- `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.
- `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".
- `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.
- `get_posts`: List blog posts for a site. Filter by status (draft, published) with pagination support.
- `get_recent_notes`: Get recent notes/context for the site. Recommended before creating tweets/posts.
- `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.
- `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.
- `list_skills`: List the user's stored skills (slug + description). Call this at the START of a task: if a skill matches what the user asked for, fetch it with get_skill and follow it instead of improvising.
- `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.
- `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 — richer metadata, dedup, search/list visibility, auto-vault-sync.

source_id is the idempotency key: pass it (content hash, agent-defined string, or note UUID) so repeat calls update instead of forking. Already know the note? Use patch_notes with id instead. Check response warnings — an auto-suffixed slug ("my-note-2") with code SLUG_COLLISION means an intended update forked instead.

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

BRAINS: pass a named brain's UUID as brain_id — the server derives site/target/folder from it, and this always skips auto-routing below. Never infer site_id or guess target_id from topic keywords. brain_alignment in the response confirms the compile will pick the note up.

WITHOUT brain_id, a site that has opted into brain auto-routing resolves one itself instead of leaving the note unfiled with a guess-and-ask: an Auto verdict files the note straight into that brain's Triage lane (routing: { band: "auto", filed: true, brain_id, brain_name, probability, verdict_id }); a Suggest or No-home verdict saves the note unfiled and the response carries needs_brain_choice — present its question and up to 3 options (each with a one-line reason) as ONE single-choice question, the way your host renders a question or choice card if it has one, alongside the also entries ("Leave unfiled" / "Create a new brain"), then call resolve_with (patch_notes with the chosen brain_id) with the pick. Never choose a brain from that list yourself. A site that has not opted in behaves exactly as before — the note is saved unfiled, no brain is queried. suggest_brain: true is a separate, unrelated opt-in: a keyword-based unassigned-brain match surfaced as suggested_brain, not auto-routing.

TAGS outside the vocabulary still apply and stay queryable, with an UNKNOWN_TAG warning naming it — ask the user before calling propose_note_tags.

VAULT SYNC is automatic but DEFERRED: the commit runs after the response, so sync is { status: "queued" }. The note IS saved — do NOT re-call. Confirm a landed commit with get_note, never vault_sync_queued_at; pass wait_for_sync: true only for commitSha/filePath inline. override_folder_path bypasses the workspace taxonomy, though a brain's source_folder_path still wins.

phase/priority/position are Big Board columns (High|Medium|Low for priority); phase is free text.
- `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.
- `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.
- `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.
- `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.
- `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.
- `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.
- `update_brain`: Add a new note to a brain — no target_id or file path knowledge required; the server resolves storage from the brain record (BlackOps directly 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. To create a new brain from scratch, call create_brain. A DB-backed brain recompiles immediately; a vault-backed one picks the note up on its next compile. Use post_notes_write (with brain_id) only when you need lower-level control over the filename or relative path.
- `upload_media`: Upload media to the site media library. Three modes:

1. URL mode — pass file_url + filename + content_type. Fetches server-side, one call, no human step. file_url must be https, SSRF-guarded (blocks private/loopback/link-local/metadata, re-checked on every redirect), capped at 50 MB (images/PDF) or 200 MB (video, under the 1 GB bucket limit to fit the 30s fetch timeout — bigger video needs the direct-PUT path below). Good when an agent already has a URL, 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 signs in and uploads via the quick-upload page, then clicks "Done". Use for screenshots, recordings, or local files — avoids round-tripping bytes, supports bulk. filename/alt_text/title apply to the FIRST asset only (later images auto-generate their own; videos get none).

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. Example: content/docs/features/image-upload.mdx.

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, 50 MB cap), asset_id + public URL like an image — the only document type; anything else rejected.
- `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.