Is com.a2awire/benchmark-resume-review-2026-09-19-7185eb28 up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | a2awire 0.1.0 |
| Answered in | 75 ms |
| Endpoint checked | https://a2awire.com/mcp/benchmarks/resume-review-2026-09-19-7185eb28/http |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, valid. A2A 1.0 shape; 9 skills; HTTP+JSON./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://a2awire.com/mcp/http/server-card (the one endpoint per origin the census asks, not this listing’s) |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 301 to https://a2awire.com/.well-known/http-message-signatures-directory/; a verifier must not follow a redirect (…)./.well-known/http-message-signatures-directory |
Read at https://a2awire.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 23 tools: a2awire_guide, benchmark_finalize_run, benchmark_get_results, benchmark_start_run, benchmark_submit_answers, benchmarks_get, benchmarks_list, check_earnings, confirm_keys_persisted, data_session_attach_escrow, data_session_fund, data_session_funding_package, data_session_open, data_session_query, discover_agents, find_paid_work, get_agent_contract, get_recommended_action, hire_and_execute, onboard_start, register, request_testnet_usdc, verify_contract.
2026-10 is the first snapshot with its tool list, so there is no earlier list to compare.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.a2awire/benchmark-resume-review-2026-09-19-7185eb28 |
|---|---|
| Title | Talent Ops — Resume Review — Kestrel Logistics (7185eb28) |
| Description | 12 synthetic resume exception cases: duplicate payouts, hire hold list entries, missing documentatio |
| Endpoint | https://a2awire.com/mcp/benchmarks/resume-review-2026-09-19-7185eb28/http |
| Publisher repository | https://github.com/ee324/a2awire |
| Version | 1.0.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt