Robin Saige we check the tools AI agents call

particle pro

pro.particle/particle-pro

Podcast intelligence for agents: transcripts, clips, speaker diarization, mention tracking.

— the operator's own registry description reported

Publisher pro.particle · first seen 2026-08-12 · endpoint https://mcp.particle.pro

allow
verdict
mid-solo
cluster
ok_tools
answers
28
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 28 tools legible (band A) ●, no confirmed drift in 7 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

Cluster mid-solo · distinctiveness 0.322 (typical). Every figure is a percentile or class within the 19,148-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency170 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools28
vs populationmid
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_9120cbf14309cc23a9076fea · 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.

Q1Does it answer?alive & usable — 7 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (7 shown, 2026-08-12 → 2026-09-13). 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 (3 events)
datetypewhat changed
2026-09-13outcomeok_tools (was payment_required)
2026-09-06outcomepayment_required (was auth_required)
2026-08-12outcomefirst probe: auth_required

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public19serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative3creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

particle_alert_create particle_alert_delete particle_alert_get particle_alert_list particle_alert_list_matches particle_alert_preview particle_alert_update particle_call particle_catalog particle_company_get particle_company_resolve particle_entity_get particle_entity_resolve particle_person_get particle_person_resolve particle_podcast_find_mentions particle_podcast_get_episode particle_podcast_get_episode_timeseries particle_podcast_get_guest particle_podcast_get_rankings particle_podcast_list_clips particle_podcast_list_episodes particle_podcast_list_guests particle_podcast_list_related particle_podcast_list_related_episodes particle_podcast_resolve particle_podcast_search_transcripts particle_topic_browse

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 checktools passingok
name is clear & specific28/28
has a description28/28
description is substantive28/28
parameters are typed28/28
parameters are described28/28

28 of 28 tools graded · 28 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 yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version particle-pro

Capabilities: resources tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-13T06:19:12Zok_tools2001702025-06-18
2026-09-06T06:18:07Zpayment_required402321
2026-08-30T06:17:47Zauth_required401161
2026-08-23T06:14:56Zauth_required401212
2026-08-16T06:14:17Zauth_required401224
2026-08-14T20:00:39Zauth_required401292
2026-08-12T05:35:54Zauth_required401171

Watch or embed this verdict

verdict badge

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/pro.particle/particle-pro.svg)](https://robinsaige.com/s/pro.particle/particle-pro)

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

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →