Should my agent depend on the MCP server io.github.Alisammour/storyflo-mcp?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Storyflo

io.github.Alisammour/storyflo-mcp

Curated audio news, daily briefings, the Declassified library + market-linked signals.

— the operator's own registry description reported

Publisher io.github.Alisammour · first seen 2026-08-12 · endpoint https://api.storyflo.com/mcp/v1

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.385 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency63 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools33

vs populationhigh

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_9bdae466a5be94f81fb045b8 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

digest digest_declassified get_article get_audio_url get_crypto_market_link get_declassified_case get_divergence_index get_embedder_manifest get_embedder_network_manifest get_market_linked_stories get_mcp_usage_self get_my_private_feed get_personas get_trending_topics get_vertical_briefing get_vertical_landscape list_podcasts list_subscriptions publisher_attach_audio publisher_connect_folder publisher_episodes publisher_folder_status publisher_stats publisher_status publisher_upload_audio quote_partnership register_embedder search_articles search_declassified search_unified stream_briefing_render_events subscribe_declassified_topic subscribe_topic

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	33/33	✓
has a description	33/33	✓
description is substantive	33/33	✓
parameters are typed	33/33	✓
parameters are described	22/33	22/33

33 of 33 tools graded · 33 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.3.0

server version Storyflo

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	inventory	tools 25 → 33
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:54Z	ok_tools	200	63	2025-06-18
2026-08-12T05:34:08Z	ok_tools	200	41	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.Alisammour/storyflo-mcp.svg)](https://robinsaige.com/s/io.github.Alisammour/storyflo-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview