Presify
io.presify/presify
Microsoft Teams presence analytics: online time, timelines, coverage, anomalies. Read-only.
— the operator's own registry description reported
Publisher io.presify · first seen 2026-08-14 · endpoint https://app.presify.io/api/mcp
Dependency rating derived
warn — alive, no tools · retrieval-public ○ · V n/a
Cluster alive-toolless · distinctiveness 0.646 (unusual). Every figure is a percentile or class within the 19,148-server census — see the whole spectrum.
🔏 Signed receipt rr_adb28fb1be3a6f5ae17cfb86 · 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.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (6 shown, 2026-08-14 → 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 (2 events)
| date | type | what changed |
|---|---|---|
| 2026-09-13 | outcome | ok (was http_error) |
| 2026-08-14 | outcome | first probe: http_error |
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 the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| retrieval-public | 1 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
Tools last seen observed
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
Capabilities: prompts 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) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-13T06:18:35Z | ok | 200 | 364 | 2025-06-18 |
| 2026-09-06T06:17:26Z | http_error | 401 | 153 | |
| 2026-08-30T06:17:13Z | http_error | 401 | 183 | |
| 2026-08-23T06:14:28Z | http_error | 401 | 293 | |
| 2026-08-16T06:13:57Z | http_error | 401 | 344 | |
| 2026-08-14T20:00:24Z | http_error | 401 | 206 |
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:
[](https://robinsaige.com/s/io.presify/presify)
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.
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 →