Agent Manifest Protocol (AMP)

Name: Agent Manifest Protocol (AMP)
Author: AMProtocol

by AMProtocolversion 0.1.5i★ –iComputer or cloud

Registry namecom.agent-manifest/amp-mcp

Install

Overview

Description from the maker (original English)

Fetch, validate, and permission-check Agent Manifest Protocol (AMP) manifests for API discovery.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 2 passedChecked from public information; code not scanned yet
UsageiVery new↓ 77/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, SSE
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 2 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: AMP_FETCH_TIMEOUT_MS

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.agent-manifest.com/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "amp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ],
      "env": {
        "AMP_FETCH_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport sse amp https://mcp.agent-manifest.com/mcp

Or run it on your computer

claude mcp add amp --env AMP_FETCH_TIMEOUT_MS=your-value -- npx -y @agentmanifest/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "amp": {
      "url": "https://mcp.agent-manifest.com/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "amp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ],
      "env": {
        "AMP_FETCH_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "amp": {
      "type": "sse",
      "url": "https://mcp.agent-manifest.com/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "amp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ],
      "env": {
        "AMP_FETCH_TIMEOUT_MS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.agent-manifest.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

AMP_FETCH_TIMEOUT_MS env
HTTP timeout (ms) when fetching manifests from API origins.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

! Caution
Maker matches the repo
The publisher (agent-manifest.com) is not the repo owner (AMProtocol); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 778 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 18584 servers in this category
Published to the registry more recently than 55% of the other 18584 servers in this category
Basic checks equal to or better than 19% of the other 18584 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Manifest Protocol (AMP) safe?

It passed 1 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.5) reached the registry 36 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, aamio rendezvous

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

aamio rendezvous

Meet an agent you have not met, exchange messages that expire, and prove it happened. No account.

by aamio.atEarlyUpdated today

Runs in the cloud✓ aamio.at

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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_updated": "2025-02-15T10:00:00Z" }

See spec/v0.3.md for complete field documentation.

For AI Agents

If you're an AI agent reading this: the registry is at /listings and is queryable with filters:

GET /listings?category=food-science

GET /listings?primary_category=reference GET /listings?pricing_model=free GET /listings?auth_required=false GET /listings?q=ingredients

For complete guidance, query GET /agents on any AgentManifest registry.

Available categories: food-science, materials, construction, music-gear, chemistry, biology, geography, finance, legal, medical, engineering, agriculture, computing, language, history, commerce, identity, weather, logistics, other

Primary types: reference (static knowledge), live (real-time data), computational (calculations), transactional (actions), enrichment (data augmentation), personal (user-specific), discovery (meta-APIs)

Getting Your API Listed

Step 1: Create Your Manifest

Add a manifest endpoint to your API that returns the JSON shown above at:

/.well-known/agent-manifest.json

Make sure:

Your description is at least 100 characters and explains what your API does for agents
Your agent_notes is at least 50 characters and includes usage guidance
All your categories are from the controlled vocabulary
Your pricing and authentication declarations are consistent
Set listing_requested: true if you want to be publicly listed

Step 2: Validate Locally

npx amp validate https://your-api.com

Fix any errors reported by the validator.

Step 3: Submit to the Registry

curl -X POST https://api.agent-manifest.com/listings/submit \

-H "Content-Type: application/json" \ -d '{"url": "https://your-api.com"}'

You'll receive a submission_id. Check its status:

curl https://api.agent-manifest.com/listings/submit/{submission_id}/status

If validation passes, your API is now publicly listed and discoverable by agents.

Project Structure

/agentmanifest

/spec v0.2.md ← Specification schema.json ← JSON Schema for validation /validator src/ index.ts ← Core validation logic (exportable library) cli.ts ← CLI tool web.ts ← Express API server /registry prisma/ schema.prisma ← Database schema seed.ts ← Seed data src/ index.ts ← Registry API server routes/ ← API routes services/ ← Business logic

Local Development

Prerequisites

Node.js 18+
PostgreSQL 15+
Docker & Docker Compose (optional but recommended)

Option 1: Docker Compose (Recommended)

# Clone and navigate to the repo

cd agentmanifest

Create .env with required secrets for local dev (not committed):

POSTGRES_PASSWORD=your-password

JWT_SECRET=$(openssl rand -hex 32)

Start everything

docker-compose up -d

Validator will be at http://localhost:3001

Registry will be at http://localhost:3002

Option 2: Manual Setup

# Install dependencies

npm install

Set up validator

cd validator npm install npm run build npm run dev # Runs on port 3001

In another terminal, set up registry

cd registry npm install

Create database

createdb agentmanifest_registry

Set environment variables

echo "DATABASE_URL=postgresql://user:password@localhost:5432/agentmanifest_registry" > .env echo "VALIDATOR_URL=http://localhost:3001" >> .env

Set up database

npm run prisma:generate npm run prisma:push npm run prisma:seed

Start registry

npm run dev # Runs on port 3002

Contributing

This is an open protocol. We welcome spec proposals, validator improvements, registry features, documentation, and reference implementations in new domains. Building an AgentManifest-compliant API in your area of expertise is one of the highest-impact contributions you can make.

See CONTRIBUTING.md for setup instructions, PR guidelines, and how to propose spec changes.

Open an issue or PR at: github.com/AMProtocol/AMP

License

Specification: CC0 1.0 Universal (public domain)
Code: MIT License

Contact

For questions, issues, or partnership inquiries: Open an issue or email brandon@agent-manifest.com

Build for agents. Build for the long run. Build in the open.

Agent Manifest Protocol (AMP)

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

aamio rendezvous

README from the maker

AgentManifest

The Problem

The Solution

1. The Spec

2. The Validator

2b. MCP Server (amp-mcp/)

3. The Registry

Quickstart: Validate an Existing API in 5 Minutes

Validate an API

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

The Manifest Format

For AI Agents

Getting Your API Listed

Step 1: Create Your Manifest

Step 2: Validate Locally

Step 3: Submit to the Registry

Project Structure

Local Development

Prerequisites

Option 1: Docker Compose (Recommended)

Create .env with required secrets for local dev (not committed):

POSTGRES_PASSWORD=your-password

JWT_SECRET=$(openssl rand -hex 32)

Start everything

Validator will be at http://localhost:3001

Registry will be at http://localhost:3002

Option 2: Manual Setup

Set up validator

In another terminal, set up registry

Create database

Set environment variables

Set up database

Start registry

Contributing

License

Contact

2b. MCP Server (`amp-mcp/`)