Skip to content

BOZOS MCP server

si.bozos/bozosbozos.sistreamable-httpv1.10.0Scanned

Exact source text, not summaries: check citations and quotes in one call; read pages and PDFs.

9 tools: 3 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 3 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 5
  • Can send data out · 5
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 BOZOS MCP server can do

The BOZOS MCP server is published by bozos.si, a domain the MCP Registry verified. It has 9 tools. It can create or change data (3 tools: checkQuote, checkCitations and submitFeedback), but cannot delete data. 6 tools only read.

2 tools read private data (search and fetch); 5 tools bring in text other people can write (readSource, checkQuote, checkCitations and 2 more); 5 tools can send data out of your system (readSource, checkQuote, checkCitations and 2 more). 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 3 findings (credentials-mention and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.10.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.

9 tools

Changes things 3Claude Code: ask
  • checkCitationsCheck cited links or quotations in supplied source text, without AI.Reads text others writeCan send data out1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.urls): a request to a URL can carry data to whoever runs it.

    Findings

    • Info

      The description is 2,902 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...still labeled supplied_text. Same as POST https://bozos.si/api/v1/citation-check."

      What this check looks for
    Description, as the server wrote it
    Check cited links or quotations in supplied source text, without AI. Use this to check 1-10 cited public HTTPS links before relying on them, in one call. Send urls to check links, or citations to also check a quotation per link: each quote is matched against the same retrieval with Quote Checker's literal rules (case, punctuation, and word boundaries preserved; whitespace normalized) and returns up to three original passages with offsets and, for PDFs, page numbers. Returns, per link, the final URL, redirects, HTTP status, content type, title, content hash, and a specific failure reason. Readable means the reader got extractable text; it does not show the page is accurate or supports a claim. A quote match means the words appear, not that they support the claim. Failed means this reader could not read it, which can mean a dead link or a site that refuses automated requests, needs JavaScript or a login, or disallows BOZOSReader in robots.txt; its quotation is then unchecked (quote_check null). Uses the guarded Source Reader. Content is not retained. Repeat a URL for multiple quotations: each distinct requested URL is read once per batch (fragments ignored, query strings preserved, redirect aliases kept separate). Sources are retrieved again in later requests. Optional unique citation ids are echoed on success and failure. Results explain offsets, matching rules, checked text representation and lengths, and distinguish matches_truncated from source_truncated. Inspect individual results even when HTTP or MCP reports a successful batch. For text your agent already has, send sources [{id,source_text,source_truncated?}] and citations [{source_id,quote,id?}]. Several citations can share a source_id. These checks make no source-fetch requests and return status supplied_text, null URL/HTTP/retrieval metadata, and a checked_text_sha256; they do not verify origin or authenticity. Mixed URL and supplied-text batches are allowed. summary.supplied counts supplied-text entries separately from readable URLs. Set source_truncated true for excerpts or incomplete input so missing quotations remain inconclusive. All supplied text is checked literally, including markup. Use POST or MCP for text; encoded GET bodies are also supported. Entire requests, including JSON/MCP overhead, are limited to 64 KiB. Failed URL entries carry upstream metadata (including robots-versus-source stage and Retry-After seconds) and a recovery hint. Delays belong to individual entries; a mixed batch never sets a whole-response Retry-After or retries sources automatically. To read a page before choosing quotations, call readSource with include_quote_source:true, then supply its quote_source.source_text and source_truncated without refetching. Retain the original reader response for URL provenance; submitted text is still labeled supplied_text. Same as POST https://bozos.si/api/v1/citation-check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • checkQuoteCheck a quotation against its source without AI.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Check a quotation against its source without AI. Use this to locate a quotation in supplied text or one public HTTPS source. Returns original passages, ranges, context, hashes, and URL provenance. Supply exactly one of source_text or url. Only whitespace may be normalized; case, punctuation, and word boundaries are preserved. Does not judge truth, paraphrases, or author intent. Source content is not retained. Source URL failures return non-2xx and source_unavailable; absent quotes in partial sources remain inconclusive. Source failures include recovery and upstream. For upstream_error, robots_unavailable, and retry_after_redirect, upstream contains stage (robots or source), HTTP status, and parsed Retry-After seconds; other failures set upstream to null. No automatic retries or waiting. Redirects requesting a future delay stop with retry_after_redirect. For retry_later failures with a valid upstream delay, the response exposes a Retry-After header; MCP preserves it in si.bozos/retry-after metadata. Upstream failures continue to use HTTP 424. To read a page before choosing quotations, call readSource with include_quote_source:true, then supply its quote_source.source_text and source_truncated without refetching. Retain the original reader response for URL provenance; submitted text is still labeled supplied_text. Same as POST https://bozos.si/api/v1/quote-check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • submitFeedbackSubmit public feedback directly to the private BOZOS inbox.Can send data outNo findings

    Why it is in this group

    • The name "submitFeedback" says "submit": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Submit public feedback directly to the private BOZOS inbox. WRITE OPERATION. Saves a private report and may queue a server-side notification only to bozos@bozos.si. No sender email account, login, browser, or API key is required. Use only within your principal's permissions. Sender names are unverified. Corrections require quoted_claim and evidence; source suggestions require evidence. No arbitrary recipients or attachments. Identical normalized reports return the original receipt. A receipt confirms storage, not email delivery or acceptance of a correction. GET and HEAD return 405 and never write. Limits: 16 KiB per request, 5 new reports/minute and 50 per rolling day globally. Instructions: https://bozos.si/tools/contact-submit.md. Same as POST https://bozos.si/api/v1/contact-submit.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 6Show 6 read-only tools
  • fetchReturn the full text of a BOZOS resource by id (from `search`, or from https://bozos.si/content-index.json): the Markdown version of a guide or note, or a JSON dataset.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "return" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Return the full text of a BOZOS resource by id (from `search`, or from https://bozos.si/content-index.json): the Markdown version of a guide or note, or a JSON dataset. Pass agent-recipes#check-existing-text for one executable recipe, a record permalink (https://bozos.si/ai-crawlers.json#gptbot) or <dataset id>#<record id> to get one record. Cite the returned url.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • inspectAgentAccessInspect how a public URL looks to AI agents, without AI.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "inspectAgentAccess" says "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "inspect" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    Inspect how a public URL looks to AI agents, without AI. Use this to see what an agent would encounter at a public HTTPS URL. Reports robots.txt status and, for BOZOSReader and five named AI crawlers plus *, whether the path is allowed; the page's redirects, status, content type, selected headers (cache, Link, X-Robots-Tag, Content-Signal), title, description, canonical, meta robots, alternate and service-desc link relations, JSON-LD and anchor counts; whether the URL serves text/markdown when asked; and whether llms.txt, llms-full.txt, the API catalog, openapi.json, the MCP server card, and the sitemap exist (JSON entry points are checked for valid JSON). Respects robots.txt for BOZOSReader: a disallowed or unreadable robots.txt means the page is not fetched. At most 20 requests, 20 seconds; no scripts run; nothing is retained or scored. An allowed value is what robots.txt says, not what an operator does. Same as POST https://bozos.si/api/v1/access-inspect.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • readSourceRead a public HTTPS page or PDF as text with source and citation metadata.Reads text others writeCan send data out2 findings

    Why it is in this group

    • The name "readSource" says "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "http": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Findings

    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "...HTTPS URL on the default port, without credentials. Private addresses and IP literals are..."

      What this check looks for
    • Info

      The description is 2,042 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ly bounded by max_characters. Same as POST https://bozos.si/api/v1/source-reader."

      What this check looks for
    Description, as the server wrote it
    Read a public HTTPS page or PDF as text with source and citation metadata. Returns the page text itself, not a model-written summary, so you can quote and cite it. No AI model. Checks robots.txt for BOZOSReader, does not execute scripts, stores no content in the application, and makes outbound public HTTPS requests. Supports HTML, Markdown, plain text, and the text layer of PDFs (pages gives each page's code-point range); no OCR or JavaScript rendering. Limits: 15 seconds, 3 page redirects, 2 MiB source (10 MiB and 300 pages for PDFs), 100000 output code points. GET also accepts url, max_characters and format directly, or a JSON body in ?json= / ?b64=. Declared canonical URL and author/date fields are publisher-supplied and unverified. Cite final_url. Errors always return JSON. gzip, deflate, and Brotli response bodies are decoded before the size limit and source hash are computed. Headless instructions: https://bozos.si/tools/source-reader.md. Source failures include recovery and upstream. For upstream_error, robots_unavailable, and retry_after_redirect, upstream contains stage (robots or source), HTTP status, and parsed Retry-After seconds; other failures set upstream to null. No automatic retries or waiting. Redirects requesting a future delay stop with retry_after_redirect. For retry_later failures with a valid upstream delay, the response exposes a Retry-After header; MCP preserves it in si.bozos/retry-after metadata. Upstream failures continue to use HTTP 424. Set include_quote_source:true with JSON output to also receive the exact matching text from this retrieval, with its own hash and truncation flag. HTML text excludes generated titles and link destinations; Markdown/plain text keep literal syntax (outer whitespace trimmed); PDFs use the text layer. Reuse quote_source.source_text and source_truncated in supplied-text checks. Keep original retrieval metadata yourself. The second representation is opt-in and independently bounded by max_characters. Same as POST https://bozos.si/api/v1/source-reader.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • structuredDiffCompare two JSON values or two texts without AI.No findings

    Why it is in this group

    • The name "structuredDiff" says "diff": a word for reading.
    Description, as the server wrote it
    Compare two JSON values or two texts without AI. Use this to see exactly what changed between two supplied versions. format json (default): returns added, removed, and changed paths as JSON Pointers; objects compare by key (order ignored), arrays by index (no move detection), and a different type counts as a change. format text: returns line hunks with one-based line numbers, comparing exactly including whitespace and case. Returns canonical SHA-256 hashes (json) or text hashes. Up to 500 changes are returned; counts cover all. Limits: 64 KiB body, 2000 lines per text, 64 nesting levels. Nothing is fetched or retained. A difference is not a judgment of meaning. Same as POST https://bozos.si/api/v1/diff.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validateJsonSchemaValidate JSON against a JSON Schema without AI.No findings

    Why it is in this group

    • The name "validateJsonSchema" says "validate": a word for reading.
    Description, as the server wrote it
    Validate JSON against a JSON Schema without AI. Use this to check supplied data against a supplied JSON Schema before relying on it. Returns valid, and each failure with the JSON Pointer of the failing value, the schema path, the keyword, and the reason. Nothing is repaired or coerced. Drafts 2020-12 (default), 2019-09, 7, and 4. References resolve only inside the supplied schema; nothing is fetched. The pattern and patternProperties keywords are refused with unsupported_keyword because user-supplied regular expressions can hang a server. Limits: 64 KiB total, 100 errors returned (error_count covers all), 64 nesting levels. Nothing is retained. Valid means this instance satisfies this schema, not that the data is correct. Same as POST https://bozos.si/api/v1/schema-validate.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: 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.

50 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__bozos__fetch",
      "mcp__bozos__search"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bozos.si/api/mcp: tools/list returned 9 tools to an anonymous client, including checkQuote (write), checkCitations (write), submitFeedback (write)

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 12 to 3

Findings

Matches of fixed checks, with the text they matched.

3 info
  • The input schema at properties.url.description mentions "credentials".

    Matched text

    inputSchema.properties.url.description: "...HTTPS URL on the default port, without credentials. Private addresses and IP literals are..."

    What this check looks for
  • The description is 2,042 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ly bounded by max_characters. Same as POST https://bozos.si/api/v1/source-reader."

    What this check looks for
  • The description is 2,902 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...still labeled supplied_text. Same as POST https://bozos.si/api/v1/citation-check."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 12 -> 3.View diff
    • Tools that change things, listed without credentials: 12 to 3
  2. Tools1 changed.~1 changedView diff
    • Changed:fetchOnly readsdescription
  3. Tools7 added, 16 removed.+7 added−16 removedView diff
    • Added:checkCitationsChanges things
    • Added:checkQuoteChanges things
    • Added:inspectAgentAccessOnly reads
    • Added:readSourceOnly reads
    • Added:structuredDiffOnly reads
    • Added:submitFeedbackChanges things
    • Added:validateJsonSchemaOnly reads
    • Removed:actionPreflight
    • Removed:auditAgentDiscovery
    • Removed:buildRobotsTxt
    • Removed:canonicalizeJson
    • Removed:checkRobotsTxt
    • Removed:countText
    • Removed:datasetChanges
    • Removed:dateMath
    • Removed:draftContactMessage
    • Removed:exactCalc
    • Removed:identifyUserAgent
    • Removed:planAgentRetrieval
    • Removed:textStats
    • Removed:timeInZones
    • Removed:utcNow
    • Removed:verifyApprovedAction

Install

Pinned to version 1.10.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http bozos https://bozos.si/api/mcp
claude mcp add --transport http bozos https://bozos.si/api/mcp

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__bozos__structuredDiff",
      "mcp__bozos__validateJsonSchema",
      "mcp__bozos__search",
      "mcp__bozos__fetch"
    ],
    "ask": [
      "mcp__bozos__readSource",
      "mcp__bozos__checkQuote",
      "mcp__bozos__checkCitations",
      "mcp__bozos__inspectAgentAccess",
      "mcp__bozos__submitFeedback"
    ],
    "deny": []
  }
}

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 bozos. Review it before you use it.

Capability tags behind 7 rules
  • mcp__bozos__readSource untrusted-input, outbound
  • mcp__bozos__checkQuote untrusted-input, outbound
  • mcp__bozos__checkCitations untrusted-input, outbound
  • mcp__bozos__inspectAgentAccess untrusted-input, outbound
  • mcp__bozos__search private-data
  • mcp__bozos__fetch private-data, untrusted-input
  • mcp__bozos__submitFeedback outbound

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/si.bozos/bozos/verify?hash=c69c0a53f00dc76c035033bd628e4f9c862f79e40e9e938eff0ca4bef4cd8919" | jq -e '.changed == false'

Pinned hash c69c0a53f00d, from Nov 9, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/si.bozos/bozos/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for si.bozos/bozos
[![Anlyon Radar](https://radar.anlyon.com/badge/si.bozos/bozos.svg)](https://radar.anlyon.com/servers/si.bozos/bozos)

Source: MCP Registry. Synced Oct 26, 2026, 07:18 UTC.

BOZOS MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BOZOS MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BOZOS MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BOZOS MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BOZOS MCP server have?

9 tools: 3 write, 6 read. checkQuote, checkCitations, submitFeedback, readSource, structuredDiff, validateJsonSchema, inspectAgentAccess, search and 1 more.

Does the BOZOS MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BOZOS MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): readSource, checkQuote, checkCitations, inspectAgentAccess and submitFeedback.

Has the BOZOS MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Oct 25, 2026. Every change is on this page and in its Atom feed.