# 996.fm perspective graph (remote · www.996.fm)

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

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `www.996.fm`: 81/100 (this document), [markdown](https://verifymcp.io/servers/fm-996-perspectives/www.md), [page](https://verifymcp.io/servers/fm-996-perspectives/www)

## Channel facts

- Endpoint: `https://www.996.fm/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 923 tokens (~153/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the 996.fm perspective graph MCP server?

996.fm perspective graph is a hosted endpoint at https://www.996.fm/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http fm-996-perspectives 'https://www.996.fm/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "fm-996-perspectives": {
      "type": "http",
      "url": "https://www.996.fm/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fm-996-perspectives]
url = "https://www.996.fm/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fm-996-perspectives": {
      "type": "remote",
      "url": "https://www.996.fm/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fm-996-perspectives --url 'https://www.996.fm/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fm-996-perspectives:
    url: "https://www.996.fm/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fm-996-perspectives": {
      "Transport": "http",
      "Url": "https://www.996.fm/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fm-996-perspectives -t streamable-http -u 'https://www.996.fm/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fm-996-perspectives": {
      "type": "http",
      "url": "https://www.996.fm/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 77, +1)

- [security] Tool “get_context” rewrote its description, which is the text the model reads
- [security] Tool “find_perspectives” rewrote its description, which is the text the model reads
- [security] Tool “get_stances” rewrote its description, which is the text the model reads
- [security] Tool “list_debates” rewrote its description, which is the text the model reads
- [functional improvement] Tool coverage: 56% → 100%
- [functional] Server version: 0.1.0 → 1.0.0
- [cosmetic] “get_context” reworded the description of “claim_id”
- [cosmetic] “get_stances” reworded the description of “debate_id”
- [cosmetic] “trace_evolution” reworded the description of “debate_id”
- [cosmetic] “trace_evolution” reworded the description of “person”
- [cosmetic] “list_debates” reworded the description of “query”

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +2)

- [security improvement] DNSSEC: fail → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-09-11 (score 73)

First indexed and scored.

## MCP tools (5)

### `find_perspectives` (~139 tokens)

Find perspectives

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 parameters:

- `topic` (string, required): The founder's question or dilemma, with a line of context

### `get_stances` (~114 tokens)

Get stances on a debate

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 parameters:

- `debate_id` (string, required): Debate id from find_perspectives or list_debates, e.g. deb-3f9c1a2b

### `trace_evolution` (~123 tokens)

Trace one person's views over time

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 parameters:

- `debate_id` (string): Optional: narrow the chronology to one debate
- `person` (string, required): A speaker's full name as the graph records it — an ambiguous surname is refused, never merged

### `get_context` (~124 tokens)

Get the transcript around a claim

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 parameters:

- `claim_id` (string, required): Claim id from any tool that returned a card, e.g. clm-5p0ken01

### `list_debates` (~180 tokens)

Browse debates

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 parameters:

- `limit` (integer): Rows to return (default and max 120)
- `min_claims` (integer): Minimum stances on the debate (default 2)
- `offset` (integer): Rows to skip — the tail line tells you the next offset
- `query` (string): Words the debate question must all contain (case-insensitive; word forms folded)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fm-996-perspectives/www#diagnostics

## Score history

- 2026-09-22: 81
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 79
- 2026-09-18: 79
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 73

## Common questions

### What is the 996.fm perspective graph MCP server?

996.fm perspective graph is an MCP server listed in the public MCP registry as fm.996/perspectives. Dated, attributed founder and investor positions, the disagreement, with timestamped receipts. This page covers its hosted endpoint (https://www.996.fm/mcp).

### Is the 996.fm perspective graph MCP server safe to use?

996.fm perspective graph scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 996.fm perspective graph MCP server expose?

996.fm perspective graph exposes 5 tools: find_perspectives, get_stances, trace_evolution, get_context, list_debates. Their descriptions and schemas cost roughly 680 tokens of context every time the server is loaded.

### Does the 996.fm perspective graph MCP server require authentication?

No. We connected to 996.fm perspective graph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 996.fm perspective graph MCP server still maintained?

996.fm perspective graph is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.996.fm/mcp
- Website: https://www.996.fm/
- Changelog RSS feed: https://verifymcp.io/servers/fm-996-perspectives/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/fm-996-perspectives/www.json
- HTML version of this page: https://verifymcp.io/servers/fm-996-perspectives/www