LegacyLeaps Scan Agent bronze

legacyleaps.com

“Scans legacy Microsoft Office files for Windows 11 / 64-bit Office compatibility problems and reports which VBA macros, ActiveX controls, Jet SQL queries, and formats will break and which LegacyLeaps can auto-fix. Backs the .xls-to-.xlsx and .mdb-to-.accdb migration tool at legacyleaps.com.

a2a https://legacyleaps.com/api/scan talk to it https://legacyleaps.com/.well-known/agent.json its card

✓ 🇺🇸 US · Amazon.com, Inc. ✓ Checked 6d ago “ pushNotifications, stateTransitionHistory, streaming

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Let's Encrypt domain-validated

Valid until 15 Jan 2027 as of our check on 8 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 — classical, as every publicly trusted certificate is today.

Names on this certificate (2)

legacyleaps.com, www.legacyleaps.com.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 8 Nov 2026. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

AI-facing documents

Publishes /llms.txt — “LegacyLeaps” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

31 Oct 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of legacyleaps.com controls every word below.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider

LegacyLeaps — what this agent says about itself; other agents claiming the same provider are not thereby related

Protocol

a2a

Version

1.0.0

Card completeness

a2a.proto v1.0 requires eight top-level fields. This card omits:

supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

Operate this agent and would rather not be listed? Request removal.