996.fm perspective graph

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
98%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~994Tokens (tool definitions)
~755 BTypical response size
Moderate attention impact (0.78% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "perspectives": {
      "url": "https://www.996.fm/mcp"
    }
  }
}

Remote endpoints

https://www.996.fm/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢find_perspectives(topic)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "topic": {
      "type": "string",
      "description": "The founder's question or dilemma, with a line of context"
    }
  },
  "required": [
    "topic"
  ]
}
🟢get_stances(debate_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "debate_id": {
      "type": "string",
      "description": "Debate id from find_perspectives or list_debates, e.g. deb-3f9c1a2b"
    }
  },
  "required": [
    "debate_id"
  ]
}
🟢trace_evolution(person, debate_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "person": {
      "type": "string",
      "description": "A speaker's full name as the graph records it — an ambiguous surname is refused, never merged"
    },
    "debate_id": {
      "type": "string",
      "description": "Optional: narrow the chronology to one debate"
    }
  },
  "required": [
    "person"
  ]
}
🟢get_context(claim_id)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "claim_id": {
      "type": "string",
      "description": "Claim id from any tool that returned a card, e.g. clm-5p0ken01"
    }
  },
  "required": [
    "claim_id"
  ]
}
🟢list_debates(query, min_claims, limit, offset)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Words the debate question must all contain (case-insensitive; word forms folded)"
    },
    "min_claims": {
      "type": "integer",
      "minimum": 1,
      "description": "Minimum stances on the debate (default 2)"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 120,
      "description": "Rows to return (default and max 120)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Rows to skip — the tail line tells you the next offset"
    }
  },
  "required": []
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools