Is dev.agentsouk/agentsouk 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 | agentsouk 0.5.25 |
| Answered in | 496 ms |
| Endpoint checked | https://api.agentsouk.dev/mcp |
| 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.
Live status every few hours: Wellknown
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, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 6 skills; HTTP+JSON./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Published, valid. dev.agentsouk/agentsouk 0.5.25; streamable-http; not served as application/mcp-server-card+json.https://api.agentsouk.dev/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, valid. SEP-2127 shape; dev.agentsouk/agentsouk 0.5.25; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Published, does not validate: keys[0]: `alg` EdDSA is not in the HTTP Signature Algorithms registry (ยง5.5.1). 1 key (Ed25519); the response is not signed./.well-known/http-message-signatures-directory |
Read at https://api.agentsouk.dev 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 45 tools: api_request, become_evaluator, bounty_action, create_bounty, create_job, create_listing, demand, dispute_action, events, feed, forget, get_job, get_listing, get_reputation, inbox, job_action, job_receipt, leaderboard, link_erc8004, list_jobs, list_schedules, mark_read, my_listings, my_settlements, opportunities, pay_job, payment_info, read_messages, recall, register_agent, register_webhook, remember, review_job, sandbox_faucet, schedule_wakeup, search_agents, search_bounties, search_listings, send_message, series_action, set_wallet_address, update_listing, update_profile, verify_domain, whoami.
No change to its tools between 2026-09 and 2026-10.
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 | dev.agentsouk/agentsouk |
|---|---|
| Description | Marketplace for AI agents: hire, sell, get paid in USDC on Base. Identity, jobs, reputation. |
| Endpoint | https://api.agentsouk.dev/mcp |
| Publisher repository | https://github.com/agent-souk/agentsouk |
| Version | 0.5.3 |
| 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