27of 100

Agent profile

jvagent.com

● Declared

jvagent.com describes itself with an Agent Card, but nothing is signed — the claims cannot be independently verified yet.

Re-check now JSON report

Identity

DNSid identity record

No DNSid record at _dnsid.jvagent.com. Publish a TXT record starting with v=DNSid1 to anchor identity in DNS.

0/10

–

Accountable-entity signature

Skipped — no DNSid record.

0/15

Trust

–

Lifecycle status is ACTIVE

Skipped — no DNSid status URL.

0/10

–

Entity and operational keys are distinct

Skipped — no DNSid key references.

0/5

–

Lifecycle log reference

Skipped — no DNSid log reference.

0/5

Capability

✓

Agent Card published

ecorp-smart-entity/2.0 Agent Card found for “JVAgent.com” with 6 skill(s).

10/10

Agent Card signature

Agent Card is unsigned. Sign it (JWS over the JCS-canonical card) so counterparties can detect tampering.

0/10

✓

MCP endpoint responds

MCP server answered initialize at https://jvagent.com/api/mcp (jvagent).

5/5

Transport

✓

Serves over valid HTTPS

TLS handshake and certificate validated; HTTP 200.

10/10

DNSSEC-validated answers

Domain resolves, but answers are not DNSSEC-signed. DNSid and DNS-AID are stronger with DNSSEC.

2/5

Discovery

DNS-AID discovery records

No DNS-AID records (_index._agents.jvagent.com TXT or agent SVCB). Other agents cannot discover this endpoint from DNS alone.

0/5

Authentication

Web Bot Auth key directory

No /.well-known/http-message-signatures-directory. Without it, sites cannot verify this agent's signed requests.

0/5

Commerce

x402 payment manifest

No x402 manifest (/.well-known/x402-manifest.json or /.well-known/x402).

0/5

Registry

Agent Name Service (ANS)

ANS (Linux Foundation, announced June 2026) resolves through federated registries and is pre-1.0. ProfileAgent reports ANS registration once registries expose a public lookup; a DNSid-anchored profile is ready to register.

info