996.fm perspective graph
Description
Dated, attributed founder and investor positions — the disagreement, with timestamped receipts.
What our measurements say
996.fm perspective graph is a remote MCP server published at www.996.fm. It has been probed 8 times since 9/12/2026. It answered in 8 of them (100.0%), a near-uninterrupted record. Median response time is 1,140 ms, a delay an agent will notice. It offers a narrow, focused set of 5 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are descriptive and indicate their purpose clearly.
- Tools have distinct functions with minimal overlap.
Weaknesses
- Descriptions occasionally lack clarity on usage context (e.g., 'who-would-push-back read').
- Some parameters (e.g., 'min_claims' in list_debates) lack explicit explanation of their impact.
- No explicit error handling or constraint documentation in tool descriptions.
find_perspectives— Description mentions 'never merge them into one answer' but doesn't clarify consequences of invalid input.list_debates— Parameter 'min_claims' is mentioned without defining its threshold or effect on filtering.get_stances— No guidance on handling non-existent 'debate_id' inputs.
Verdict
Event narrative
Risk: low
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test passed · last run:
- Cold-start: cold 51ms → warm 54ms (penalty 0ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
find_perspectivesRoute a founder's dilemma to the debates that genuinely bear on it. Present the readings SEPARATELY — never merge them into one answer. 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. When coverage is thin it says so — advise from general knowledge rather than stretching a weak match. Returns up to 4 debates and 36 stances — a sample, not the full set; call get_stances(debate_id) for a debate's complete stances. Each carries speaker, publication date, strength, reasoning, scope qualifiers and an episode receipt. Quote the receipt — episode + timestamp, or essay link + excerpt — so the founder can check the moment. R
topicstringrequired
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.
debate_idstringrequired
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.
personstringrequireddebate_idstring
get_contextThe scene around one claim. 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.
claim_idstringrequired
list_debatesBrowse the debate registry: id, question, readings, stance count, born (earliest publication date). Optional case-insensitive substring filter. 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.
querystringmin_claimsintegerlimitintegeroffsetinteger
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Legacy
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/fm-996-perspectives)<a href="https://mcpmetrics.io/servers/fm-996-perspectives"><img src="https://mcpmetrics.io/badge/fm.996/perspectives/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- Agent Receiptsagent-receipts.dropwatchhq.com
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
- M365 Graph MCPmcps.work
Manage Microsoft 365 email, calendar, contacts and inbox rules via the Graph API with OAuth 2.0.
- Quantified Investor Portfolio Simulatormcp.quantifiedinvestor.com
Portfolio scenarios with instrument checks, Monte Carlo analysis and interactive reports.
- Open Graph meta count, markup discardedagent-observatory-sensor.nolimit-observatory.workers.dev
Open Graph meta count, markup discarded
- PaymentOracle — Verifiable Multi-Rail Payment Receiptstooloracle.io
PaymentOracle — ES256K-signed receipts for x402 payments on USDC+EURC (Base) and XRP+RLUSD (XRPL).
- Global Logistics (AfterShip labels with your own carrier accounts)logi-global.wishpool.app
Global shipping labels for AI agents via AfterShip with your own carrier accounts.
Comments
Sign in to write a comment
No comments yet. Be the first.