996.fm perspective graph
fm.996/perspectives · 1.0.0
Dated, attributed founder and investor positions — the disagreement, with timestamped receipts.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://www.996.fm/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 5 tools.
- Protocol
- 2025-06-18
- Calls itself
- 996fm-perspectives 1.0.0
- Handshake time
- 412 ms
- HTTP status
- 200
The tools it lists (5, as of 2 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
find_perspectivesRoute 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.
get_stancesEvery 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.
trace_evolutionOne 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.
get_contextThe 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.
list_debatesBrowse 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
fm.996/perspectives, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 23 days ago. The registry entry · www.996.fm