Should my agent depend on the MCP server com.aurelianflo/core?

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

AurelianFlo

com.aurelianflo/core

Remote MCP server for OFAC screening, EDD memos, exposure forecasts, queues, and reports.

— the operator's own registry description reported

Publisher com.aurelianflo · first seen 2026-08-12 · endpoint https://api.aurelianflo.com/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.217 (typical). 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

latency77 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools11

vs populationmid

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

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

compliance_edd_report compliance_exposure_forecast compliance_queue_optimize queue_saved_list report_docx_generate report_pdf_generate report_saved_retrieve server_capabilities wallet_ofac_batch wallet_ofac_report wallet_ofac_screen

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	11/11	✓
has a description	11/11	✓
description is substantive	11/11	✓
parameters are typed	11/11	✓
parameters are described	9/11	9/11

11 of 11 tools graded · 11 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

0/0 answers agree with the published primary source · 2 unverifiable.

claim class	key	verdict	primary source
OFAC SDN screening (vs the official list)	ISLAMIC REVOLUTIONARY GUARD CORPS	unverifiable	ofac-sdn
OFAC SDN screening (vs the official list)	MAERSK LINE	unverifiable	ofac-sdn

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.4.0

server version AurelianFlo

Capabilities: prompts 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 (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:56Z	ok_tools	200	77	2025-06-18
2026-08-12T05:33:12Z	ok_tools	200	138	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/com.aurelianflo/core.svg)](https://robinsaige.com/s/com.aurelianflo/core)

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