Databuddy has no A2A message endpoint. Agents query Databuddy analytics, errors, Web Vitals, feature flags, links, funnels, and goals through its MCP server, described in the MCP manifest at this card's url.

A2A readiness

F · 37/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C, 78.5/100), which weighs availability, conformance, card completeness and speed. How the two differ

Valid Agent Card	10/10	Parseable Agent Card with the required fields.
Live JSON-RPC	5/25	Endpoint answers, but not with JSON-RPC 2.0 (363 ms).
Protocol version	0/10	No A2A protocol version declared.
JWS signature	0/10	Card is unsigned.
Uptime (30 days)	15/15	3/3 probes succeeded; final after 5 probes in 30 days.
Skill declaration	5/10	Declares 2 skill(s) with structured metadata.
Verified identity	0/10	No provider organization/url declared.
Freshness + modern flags	2/5	seen within 30 days.
Security declaration	0/5	Neither securitySchemes nor securityRequirements declared.

Responsiveness: Responsive (363 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, 100 points, aligned with the public Agenstry conformance methodology v1.1. Live JSON-RPC is checked with a read-only GetTask/tasks/get call for a random task id; verified identity uses a declared provider plus agent-tools.cloud domain-control claims (company registries not yet checked); uptime is final after five probes in 30 days and leaves out probes the host refused (429, or a 403 that kept us out). Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 6,309 reachable A2A agents in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 18% of peers; This listing 37 · peer median 54
Latency: Faster than 35% of peers; This listing 524 ms · peer median 398 ms

Where it loses the most points, and how to win them back

Live JSON-RPC −20 — Answer JSON-RPC at the URL the Agent Card declares.
Now: Endpoint answers, but not with JSON-RPC 2.0 (363 ms).
Protocol version −10 — Support the current protocol revision.
Now: No A2A protocol version declared.
JWS signature −10 — Sign the Agent Card (JWS).
Now: Card is unsigned.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

Site rank (Tranco): #351,471 of the top 1M; databuddy.cc · list of 2026-11-10

How to call

A2A endpoint (JSONRPC)

https://www.databuddy.cc/.well-known/mcp.json

Agent card

https://www.databuddy.cc/.well-known/agent-card.json

Listed in

Directories this entry was found in.

wellknown since 2026-10-30 ↗