Agenlify MCP server

Which MCP servers are Agenlify'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-20

← Back to Agenlify

Whose server it is

Registry nameai.agenlify/catalogverified in the MCP registry

The registry name sits under agenlify.ai. 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-20

Stateanswerschecked 2026-10-20
Tools3
Server calls itselfai.agenlify/catalog
Server version1.0.0
Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.

Once connected

Parameters are untyped or undescribed in 3 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: 14, the first on 2026-10-20

INITE MCP score95 of 100answers 100 · definitions 83 · context 100 · connects 100
Answered100% of days14 of 14 daily checks
Median first answer272 ms
Space in an agent's context≈ 556 tokensthe definitions of all its tools (3), which an agent carries on every turn
Tool definitionsB · 83 of 100
Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once

Parameters without a description: in 3 of 3

What an agent can do with it

not sure · compare AI agents for customer support tasks
not sure · check pricing and setup before connecting a tool
not sure · shortlist agents for marketing or data analysis work

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-20

search_agents
Search the public Agenlify catalog by English or Chinese task, product name or official domain. Filter by pricing, setup, category, task and evidence. Returns dated catalog summaries and source links; empty results mean no documented match.
get_agent
Get a catalog product by exact slug, including inputs, outputs, setup steps, limitations, human review requirements, pricing review dates, official sources and any separately recorded case studies.
list_tasks
List Agenlify task IDs, preparation checklists, expected outputs and review requirements. Each listed task has at least three catalog candidates. Optionally filter tasks by category.

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://agenlify.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http agenlify https://agenlify.ai/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://agenlify.ai/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.