996.fm perspective graph
REMOTE · WWW.996.FM · SCANNED SEP 22
Dated, attributed founder and investor positions — the disagreement, with timestamped receipts.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · www.996.fm
claude mcp add --transport http fm-996-perspectives 'https://www.996.fm/mcp'
{
"mcpServers": {
"fm-996-perspectives": {
"url": "https://www.996.fm/mcp"
}
}
} {
"servers": {
"fm-996-perspectives": {
"type": "http",
"url": "https://www.996.fm/mcp"
}
}
} [mcp_servers.fm-996-perspectives] url = "https://www.996.fm/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fm-996-perspectives": {
"type": "remote",
"url": "https://www.996.fm/mcp",
"enabled": true
}
}
} openclaw mcp add fm-996-perspectives --url 'https://www.996.fm/mcp' --transport streamable-http
mcp_servers:
fm-996-perspectives:
url: "https://www.996.fm/mcp" {
"McpServers": {
"fm-996-perspectives": {
"Transport": "http",
"Url": "https://www.996.fm/mcp"
}
}
} assistant mcp add fm-996-perspectives -t streamable-http -u 'https://www.996.fm/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 15 Sept 26 +1
- 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 security
- Tool coverage: 56% → 100% ▲ functional
- Server version: 0.1.0 → 1.0.0 functional
- “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” cosmetic
- 14 Sept 26 +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.
- 12 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 11 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://www.996.fm/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.996.fm | CN=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f29c25bd24e9daffe980e7636d3a930d16 |
| SANs: www.996.fm | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.996.fm. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fm. | present | 26186, 60226 | 8, 8 | Verified |
| 996.fm. | present | 2371 | 13 | Verified |
| www.996.fm. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.996.fm/mcp | Verified | 200 | |
| http (plaintext) | http://www.996.fm/mcp | HTTPS enforced | 301 | https://www.996.fm/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_perspectives Find perspectives ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The founder's question or dilemma, with a line of context |
No output schema declared.
No examples provided.
get_context Get the transcript around a claim ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | string | yes | Claim id from any tool that returned a card, e.g. clm-5p0ken01 |
No output schema declared.
No examples provided.
get_stances Get stances on a debate ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| debate_id | string | yes | Debate id from find_perspectives or list_debates, e.g. deb-3f9c1a2b |
No output schema declared.
No examples provided.
list_debates Browse debates ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
trace_evolution Trace one person's views over time ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| debate_id | string | – | Optional: narrow the chronology to one debate |
| person | string | yes | A speaker's full name as the graph records it — an ambiguous surname is refused, never merged |
No output schema declared.
No examples provided.
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.