Log inSubmit server
Aigentify logo

Aigentify

Audits directories and URLs for agent readiness, then generates AGENTS.md, server.json, offers, and agent routes.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Aigentify

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "aigentify": {
      "command": "npx",
      "args": [
        "-y",
        "aigentify"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

  • agent-readiness
  • auditing
  • artifact-generation
  • developer-tools

The aigentify MCP server audits a product directory or live URL for agent-native readiness and generates public artifacts for agents. It runs as a stdio MCP process launched with `npx aigentify-mcp`, exposing `audit` and `gen` tools. Use it when evaluating whether a product is discoverable and usable by agents or when creating supporting files such as AGENTS.md and server.json. The underlying package also provides JavaScript, TypeScript, and CLI interfaces.

Use cases

  • Audit a local product repository for agent-readiness signals
  • Check a live website for discoverability and agent access
  • Generate an AGENTS.md file for a product
  • Create server.json or other agent-facing artifacts
  • Inspect external registry discovery for a product

Key features

  • Audits directories and live URLs
  • Checks core and web agent-readiness signals
  • Generates AGENTS.md, server.json, offers, and agent routes
  • Exposes audit and gen tools over stdio MCP
  • Supports JavaScript, TypeScript, and CLI usage
  • Supports optional aigentify configuration files

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · aigentify (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads5.3kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.

How Aigentify works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Aigentify

aigentify is an MCP server that connects an MCP client to product auditing and artifact generation workflows. Its main tools are `audit`, which checks a directory or live URL for agent-native readiness, and `gen`, which creates artifacts such as AGENTS.md, server.json, offers, and agent routes.

Run `npm install aigentify` for the package, or start the MCP server directly with `npx aigentify-mcp`. The server runs over stdio and exposes the `audit` and `gen` tools to an MCP client.

Yes, aigentify can be used with Cursor as a standard stdio MCP server. Start it with `npx aigentify-mcp` and configure it through Cursor's MCP server settings.

Yes, the `audit` tool accepts a live URL as its target. URL audits include core checks and web-specific signals such as OpenAPI, agent pages, crawler access, markdown negotiation, schema, and external discovery.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAigentify AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/aigentify?style=directory)](https://allmcps.com/mcp/aigentify)
HTML Embed
<a href="https://allmcps.com/mcp/aigentify"><img src="https://allmcps.com/api/badge/aigentify?style=directory" alt="Aigentify on AllMCPs" /></a>