# aigentify [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pooriaarab/aigentify  
**GitHub Stars:** 0  
**npm Downloads (last month):** 5326  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aigentify

## Description
Audit and generate agent-native product surfaces

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "aigentify": {
    "command": "npx",
    "args": ["-y","aigentify"]
  }
}
```

## Documentation

## What aigentify MCP server does

The aigentify MCP server evaluates a product directory or live URL against signals related to agent-native readiness. It can inspect local project files, test web-facing behavior, and produce artifacts that describe or expose a product for agent use.

The audit output covers core signals such as AGENTS.md, public-safe instructions, server.json, MCP availability, offer JSON-LD, honest offers, llms.txt, and sitemaps. For URL targets, it can also assess web signals including well-known agent metadata, OpenAPI availability, agent pages, soft 404 behavior, markdown negotiation, content without JavaScript, organization schema, crawler access, and rate-limit headers. Additional checks cover authentication metadata, API catalogs, A2A agent cards, link headers, markdown alternatives, and external discovery through registries such as npm and the MCP Registry.

## How it works

The aigentify MCP server communicates through the standard MCP client connection started by `npx aigentify-mcp`. Its exposed `audit` tool accepts a `target` value, while `gen` accepts an `artifact` name and a `params` object.

Targets may be local directories or live URLs. Core checks apply to both target types, while web checks are intended for served URLs and are reported as not applicable when the target does not provide a website. The package also exposes equivalent JavaScript and TypeScript functions, including `auditTarget` and `generate`, plus a command-line interface.

## Setup and configuration

Install the npm package with `npm install aigentify`. To run the MCP server directly, use `npx aigentify-mcp`.

Optional configuration can be placed in `aigentify.config.ts`, `aigentify.config.js`, or `aigentify.config.mjs`. Export configuration created with `defineConfig`, either as the default export or as `aigentifyConfig`. Supported fields shown in the material include a product name, description, repository URL, npm package name, and offer details such as name, price, and currency.

## Tools and capabilities

The aigentify MCP server provides two tools:

- `audit`: checks a directory or URL using the available readiness signals. A target is required by the tool schema.
- `gen`: creates a selected artifact from supplied parameters. The tool accepts `artifact` and `params` fields.

Supported generated artifact types are `agents-md`, `server-json`, `offer`, and `agents-route`. The same generation features are available through the CLI, which can print artifacts or write them to a path. The `init` command can create starter AGENTS.md and server.json files without replacing existing files.

## Limitations and notes

Web-specific checks only provide meaningful results for a served URL. Directory audits can still run the core checks, but web signals are marked not applicable. External-discovery checks query third-party registries, so their results depend on the information those services expose.

The audit checks readiness signals; it does not claim to deploy, repair, or automatically publish the resulting artifacts.

_Full upstream README: https://allmcps.com/mcp/aigentify/readme_