Agent Manifest Protocol (AMP) MCP server

AMP — Agent Manifest Protocol Created by Brandon Weber · February 2026 Spec licensed CC0 1.0 · Code licensed MIT

AgentManifest

Open protocol and registry for the AI agent data economy

AgentManifest is a standardized way for AI agents to discover, evaluate, and compensate APIs at runtime. It's json.org meets npm meets Stripe for agent-accessible data sources.

The Problem

AI agents need data to do useful work in the world. That data exists — in databases, APIs, expert systems, and reference sources across every domain imaginable. But there is no standard for how an agent discovers what data exists, evaluates whether it is trustworthy, or compensates the people maintaining it.

The result is a three-way deadlock:

• Providers can't be found or paid
• Developers hardcode a handful of known APIs
• Agents hallucinate the gaps

The Solution

AgentManifest provides three components that solve this:

1. The Spec

An open standard defining what a compliant agent-ready API must declare about itself. Every API serves a manifest at /.well-known/agent-manifest.json that describes:

• What it knows and what problems it solves
• Its endpoints and how agents should use them
• Pricing, authentication, and reliability information
• Guidance specifically written for AI agents

2. The Validator

A tool that checks APIs against the spec and issues verification tokens. Available as:

• An npm library for programmatic validation
• A CLI tool for local development
• A web API for automated registry checks

2b. MCP Server (amp-mcp/)

Official Model Context Protocol server for AMP — tools to fetch manifests, validate JSON Schema, and check actions against declared constraints. Stdio for Cursor/Claude; SSE HTTP for a hosted hub. See amp-mcp/README.md.

npx @agentmanifest/mcp-server          # stdio
npx @agentmanifest/mcp-server-http     # SSE on PORT (default 8787)

3. The Registry

A public, queryable index of verified APIs that agents can use to discover data sources at runtime. Think of it as the npm registry, but for agent-accessible data APIs.

Quickstart: Validate an Existing API in 5 Minutes

# Install the validator
npm install -g @agentmanifest/cli

# Validate an API
amp validate https://bakebase.agent-manifest.com

# If your API passes validation, it can be listed in the registry

That's it. If your API serves a valid manifest at /.well-known/agent-manifest.json, you're AgentManifest-compliant.

The Manifest Format

Every compliant API must serve this at /.well-known/agent-manifest.json:

{
  "spec_version": "agentmanifest-0.2",
  "name": "Your API Name",
  "version": "1.0.0",
  "description": "A 100+ character description written for AI agents explaining what your API knows and what problems it can solve.",
  "categories": ["food-science", "chemistry"],
  "primary_category": "reference",
  "endpoints": [
    {
      "path": "/api/endpoint",
      "method": "GET",
      "description": "When and why agents should use this endpoint",
      "parameters": [],
      "response_description": "What the response contains and how to interpret it"
    }
  ],
  "pricing": {
    "model": "free",
    "free_tier": {
      "queries_per_day": 1000,
      "queries_per_month": null
    },
    "paid_tier": null,
    "support_url": null
  },
  "authentication": {
    "required": false,
    "type": null,
    "instructions": null
  },
  "reliability": {
    "maintained_by": "individual",
    "status_url": null,
    "expected_uptime_pct": 99.5
  },
  "agent_notes": "Freeform guidance for AI agents. Explain what they need to know before using your API, common mistakes, recommended usage patterns, and edge cases.",
  "contact": "your-email@example.com",
  "listing_requested": true,
  "last_u

Shortened. The full README is on GitHub.