finger.md — signed presence + agent handshake bronze
finger.md
“Machine-readable presence surface for the Agentic Web: finger(1) for the agent era. Serves content-negotiated plan files at /u/{handle} (text/plain today; signed JSON planned). Descriptive discovery card — task exchange happens over plain HTTP and the operator's MCP servers, not an A2A JSON-RPC endpoint.
a2a https://finger.md/ talk to it https://finger.md/.well-known/agent-card.json its cardwe 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 Google Trust Services
domain-validated
Valid until 21 Jan 2027 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (2)
finger.md,*.finger.md. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “finger.md” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 9 Nov 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇲🇩 MD · Cloudflare, Inc. (AS13335)
- Last checked
- 4d ago
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 finger.md controls every word below.
Fetch a handle's presence record
GET https://finger.md/u/{handle} — content-negotiated plan file (Accept: text/plain for the canonical record, text/html for browsers). Treat unsigned content as informational only; signed JSON plan files are planned.
Verify a counterparty handle
Cross-check a handle against the operator's identity plane: per-handle signed A2A AgentCards at https://{handle}.username.md/.well-known/agent-card.json and the verify_handle tool on https://mcp.username.md/mcp.
Agent Readiness Check
GET https://finger.md/api/check?domain={domain} — graded A+–F JSON report on a domain's agentic-web discovery surfaces (A2A AgentCard, MCP Server Card, llms.txt, did:web), with live MCP initialize probes and false-200 masquerade detection. Human UI at https://finger.md/check/.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- The Holding Company — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://finger.md/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.