Is app.tasg/tasg 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 sent no WWW-Authenticate header, so a stock client has nothing to discover. If the server is in the official registry, check it by `name` to learn whether a client can get a credential unattended.
| Outcome | needs_credential |
|---|---|
| HTTP status | 401 |
| Answered in | 341 ms |
| Endpoint checked | https://tasg.app/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
Sign-in
Sign-in is broken. Sign-in breaks at "401 carries a WWW-Authenticate challenge", and the fix is the server's.
First broken step: 401 carries a WWW-Authenticate challenge, the server’s to fix. header missing, and no protected-resource metadata answers at the well-known paths either.
Fix: Add `WWW-Authenticate: Bearer resource_metadata="https://<host>/.well-known/oauth-protected-resource<path>"` to every 401. (MCP 2026-07-28 "Protected Resource Metadata Discovery Requirements"; RFC 9728 §3, §5.1)
- claude.ai: blocked — 401 carries a WWW-Authenticate challenge: header missing, and no protected-resource metadata answers at the well-known paths either.
- Claude Code: blocked — 401 carries a WWW-Authenticate challenge: header missing, and no protected-resource metadata answers at the well-known paths either.
- ChatGPT: blocked — 401 carries a WWW-Authenticate challenge: header missing, and no protected-resource metadata answers at the well-known paths either.
- VS Code: blocked — 401 carries a WWW-Authenticate challenge: header missing, and no protected-resource metadata answers at the well-known paths either.
- Cursor: blocked — 401 carries a WWW-Authenticate challenge: header missing, and no protected-resource metadata answers at the well-known paths either.
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
| A2A agent card | Could not tell (fetch failed: 801ED4ED01000000:error:0A00010B:SSL routines:tls_validate_record_header:wrong version number:../deps/open…)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (not asked: https://tasg.app did not answer the agent-card request).https://tasg.app/mcp/server-card |
| MCP server card (SEP-1649 location) | Could not tell (not asked: https://tasg.app did not answer the agent-card request)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Could not tell (not asked: https://tasg.app did not answer the agent-card request)./.well-known/http-message-signatures-directory |
Read at https://tasg.app 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
| Registry name | app.tasg/tasg |
|---|---|
| Title | Tasg |
| Description | Work management where AI agents are first-class members: tasks, projects, memory over hosted MCP |
| Endpoint | https://tasg.app/mcp |
| Publisher repository | none listed |
| Version | 1.0.1 |
| 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