Skip to content

Blumify (public, no sign-in) MCP server

io.blumify/transcripts-publicblumify.iostreamable-httpv1.0.1Scanned

Summaries, key points and chapters of existing YouTube and podcast transcripts. No sign-in.

1 tool: 1 only read.

Tools: 0 delete, 0 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 Blumify (public, no sign-in) MCP server can do

The Blumify (public, no sign-in) MCP server is published by blumify.io, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (get_transcript); 1 tool can send data out of your system (get_transcript).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

Last scanned Nov 20, 2026, version 1.0.1.

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.

1 tool

Only reads 1Show 1 read-only tool
  • get_transcriptThe summary, key points and chapters of a YouTube video or podcast episode, with a link to its full transcript, if blumify.io already has it.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "get_transcript" says "get": a word for reading.

    What it can reach

    • 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
    The summary, key points and chapters of a YouTube video or podcast episode, with a link to its full transcript, if blumify.io already has it. Give the video or episode URL.

    Annotations the server declares

    • readOnlyHint: true
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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, 18:55 UTC, unchanged since Oct 22, 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
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://blumify.io/.well-known/oauth-protected-resource/api/media/v1/mcp/public
Authorization servers
https://blumify.io
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http transcripts-public https://blumify.io/api/media/v1/mcp/public
claude mcp add --transport http transcripts-public https://blumify.io/api/media/v1/mcp/public

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": [],
    "ask": [
      "mcp__transcripts-public__get_transcript"
    ],
    "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 transcripts-public. Review it before you use it.

Capability tags behind 1 rule
  • mcp__transcripts-public__get_transcript untrusted-input, 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/io.blumify/transcripts-public/verify?hash=d56dd280fff991f491af8481b6aee7d2132ad0d62afc1b233fd78cd771b5122d" | jq -e '.changed == false'

Pinned hash d56dd280fff9, from Nov 20, 2026, 05:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.blumify/transcripts-public/changes.xml

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

Badge

Anlyon Radar badge for io.blumify/transcripts-public
[![Anlyon Radar](https://radar.anlyon.com/badge/io.blumify/transcripts-public.svg)](https://radar.anlyon.com/servers/io.blumify/transcripts-public)

Source: MCP Registry. Synced Nov 6, 2026, 06:17 UTC.

Blumify (public, no sign-in) MCP server: questions and answers

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

Is the Blumify (public, no sign-in) MCP server safe?

No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Blumify (public, no sign-in) MCP server delete data?

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

Can the Blumify (public, no sign-in) 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 Blumify (public, no sign-in) MCP server have?

1 tool: 1 read. get_transcript.

Does the Blumify (public, no sign-in) MCP server need sign-in or OAuth?

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

Does the Blumify (public, no sign-in) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_transcript.

Has the Blumify (public, no sign-in) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.