Is io.github.stoyan-stoyanov/agentzia up? Live MCP status

It is up, behind a credential. It refused a request carrying no credential with HTTP 401, which is what a server that wants a key or a sign-in does.

It refused without a credential (HTTP 401). A check by URL makes only the initialize request, so it does not walk the OAuth discovery chain; the server's WWW-Authenticate header is in `probe.wwwAuthenticate`. If the server is in the official registry, check it by `name` to learn whether a client can get a credential unattended.

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

Sign-in

Sign-in works for every client checked. Every step a client needs is in place, for every client checked.

• claude.ai: can sign in
• Claude Code: can sign in
• ChatGPT: can sign in
• VS Code: can sign in
• Cursor: can sign in

Discovery only, from the challenge this server sent the check above: no credential, no client registration. Client verdicts are emulated from each client’s published requirements. Steps, documents and redirect URIs: the full sign-in report. Watch it hourly: agentcheck's free watch checks this server every hour, follows the sign-in a new client follows with these same rules, and emails when a step breaks; no account. Nightly, with history: mcpcheck Server Pro re-runs these sign-in checks against the server every night, with 90 days of history, and emails when one fails ($49 a server a month; the first run is free).

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 wanted a credential (HTTP 401). Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

Read at https://www.agentzia.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

It is not in the 2026-10 snapshot. Snapshots record the tool list of every listing that answered a stock client with no credential in that month’s census.

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

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

Free, no key, no signup. Terms · Privacy