Skip to content
anlyon.dev

996.fm perspective graph

fm.996/perspectives996.fmstreamable-httpv1.0.0Scanned

Dated, attributed founder and investor positions — the disagreement, with timestamped receipts.

5 tools: 1 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

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.

5 tools

Changes things 1Claude Code: ask
  • trace_evolutionOne speaker's takes in order of episode publication date (optionally on one debate) — reversals and re-assertions visible, never judged.No 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.
    Description, as the server wrote it
    One speaker's takes in order of episode publication date (optionally on one debate) — reversals and re-assertions visible, never judged. Attribute and date every position (dates are episode publication dates); keep hedged claims hedged. A 2023 position is a 2023 position; if the same person later said otherwise, show both.

    Annotations the server declares

    • title: Trace one person's views over time
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • find_perspectivesRoute a founder's dilemma to the debates that genuinely bear on it.No findings

    Why it is in this group

    • The name "find_perspectives" says "find": a word for reading.
    Description, as the server wrote it
    Route a founder's dilemma to the debates that genuinely bear on it. Present the readings SEPARATELY — never merge them into one answer. Respect the question's altitude: scale-up material does not answer a pre-PMF dilemma. When coverage is thin it says so — advise from general knowledge rather than stretching a weak match. Returns ≤4 debates and ≤36 stances — a sample, not the full set; get_stances(debate_id) has a debate's complete stances, each with speaker, date, strength and a receipt.

    Annotations the server declares

    • title: Find perspectives
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • get_contextThe transcript around one claim — the moment in context, with its receipt.No findings

    Why it is in this group

    • The name "get_context" says "get": a word for reading.
    Description, as the server wrote it
    The transcript around one claim — the moment in context, with its receipt. Spoken: the episode's public transcript, windowed ±90s around the claim's timestamp. Written (an essay): the verbatim excerpt snapshotted at digest plus a link into the original; never the surrounding text, never a live fetch. Quote the receipt — episode + timestamp, or essay link + excerpt — so the founder can check the moment.

    Annotations the server declares

    • title: Get the transcript around a claim
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_stancesEvery stance on one debate, grouped by reading — raw material for your own who-would-push-back read.No findings

    Why it is in this group

    • The name "get_stances" says "get": a word for reading.
    Description, as the server wrote it
    Every stance on one debate, grouped by reading — raw material for your own who-would-push-back read. No synthesis. Attribute and date every position (dates are episode publication dates); keep hedged claims hedged. The graph never says who opposes whom — work out yourself which positions push back on the founder's leaning, and name them.

    Annotations the server declares

    • title: Get stances on a debate
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_debatesBrowse the debate registry: id, question, readings, stance count, born (earliest publication date).Reads text others writeNo findings

    Why it is in this group

    • The name "list_debates" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse the debate registry: id, question, readings, stance count, born (earliest publication date). Optional query: a debate matches when its question has every word of it, case-insensitive, word forms folded (hire/hiring, co-founder/cofounder). Browsing only — it does not rank against a question; use find_perspectives for that. Defaults to debates with 2+ stances, 120 rows a page — page with offset.

    Annotations the server declares

    • title: Browse debates
    • 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.

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

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 out0
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 Oct 22, 2026, 14:48 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
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.996.fm/.well-known/oauth-protected-resource/mcp
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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.996.fm/mcp: tools/list returned 5 tools to an anonymous client, including trace_evolution (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

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

claude mcp add --transport http perspectives https://www.996.fm/mcp
claude mcp add --transport http perspectives https://www.996.fm/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__perspectives__find_perspectives",
      "mcp__perspectives__get_stances",
      "mcp__perspectives__get_context",
      "mcp__perspectives__list_debates"
    ],
    "ask": [
      "mcp__perspectives__trace_evolution"
    ],
    "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 perspectives. Review it before you use it.

Capability tags behind 1 rule
  • mcp__perspectives__list_debates untrusted-input

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://anlyon.dev/api/v1/servers/fm.996/perspectives/verify?hash=2cdc69418576b6aa048fa45bc940dba4034515c7126adb2ccf1c5b272080c7ef" | jq -e '.changed == false'

Pinned hash 2cdc69418576, from Oct 21, 2026, 19:00 UTC.

Watch

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

https://anlyon.dev/servers/fm.996/perspectives/changes.xml

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

Badge

anlyon.dev badge for fm.996/perspectives
[![anlyon.dev](https://anlyon.dev/badge/fm.996/perspectives.svg)](https://anlyon.dev/servers/fm.996/perspectives)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.