Skip to content
AgentTask Atlas logo

AgentTask Atlas MCP server

Which MCP servers are AgentTask Atlas's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-28

← Back to AgentTask Atlas

Whose server it is
  • Registry namecom.agenttaskatlas/catalogverified in the MCP registry

The registry name sits under agenttaskatlas.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools3
  • Server calls itselfagenttask-atlas
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 132 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: let an agent read and edit scoped local project files; run local git status, diff and commit work for an agent; fetch a web page into an agent's working context.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer168 ms
  • Space in an agent's context≈ 404 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 89 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 3

What an agent can do with it

  • cannot · let an agent read and edit scoped local project files
  • cannot · run local git status, diff and commit work for an agent
  • cannot · fetch a web page into an agent's working context

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-28
  • search_catalog

    Find MCP servers and Agent Skills for a dev task. Free-text query (every term must match name, vendor, verdict, install or category; common words like postgres, e2e, scraping are expanded) and optional category slug from list_categories…

  • get_entry

    Full card for one catalog entry by slug (e.g. 'github-mcp-server'): verdict, install command, credentials, permissions, license, source and maintenance status.

  • list_categories

    All dev-task categories and entry types with entry counts and page URLs.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "catalog": {
      "type": "http",
      "url": "https://agenttaskatlas.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http agenttaskatlas https://agenttaskatlas.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://agenttaskatlas.com/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.