# Agent Manifest Protocol (AMP) (npm · @agentmanifest/mcp-server)

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

- Trust score: 80/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.agent-manifest.com`: 73/100, [markdown](https://verifymcp.io/servers/com-agent-manifest-amp-mcp/mcp.md), [page](https://verifymcp.io/servers/com-agent-manifest-amp-mcp/mcp)
- npm · `@agentmanifest/mcp-server`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server.md), [page](https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@agentmanifest/mcp-server`
- Version: `0.1.5`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 80/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 40 of 122 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 33 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 584 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Agent Manifest Protocol (AMP) MCP server?

Agent Manifest Protocol (AMP) runs locally as an npm package, launched with npx -y @agentmanifest/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-agent-manifest-amp-mcp -- npx -y @agentmanifest/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "com-agent-manifest-amp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-agent-manifest-amp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-agent-manifest-amp-mcp -- npx -y @agentmanifest/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-agent-manifest-amp-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentmanifest/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-agent-manifest-amp-mcp --command npx --arg -y --arg @agentmanifest/mcp-server
```

### Hermes

```yaml
mcp_servers:
  com-agent-manifest-amp-mcp:
    command: "npx"
    args: ["-y", "@agentmanifest/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-agent-manifest-amp-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@agentmanifest/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-agent-manifest-amp-mcp -t stdio -c npx -a -y @agentmanifest/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "com-agent-manifest-amp-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@agentmanifest/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-29 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.

### 2026-10-27 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 75, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

## MCP tools (5)

### `fetch_manifest_by_domain` (~83 tokens)

Fetch AMP manifest by domain

Resolve an API origin from a domain (e.g. "bakebase.agent-manifest.com"), try standard AMP discovery URLs, and return parsed manifest JSON plus metadata.

Input parameters:

- `domain` (string, required): API hostname or URL origin without a path, e.g. "example.com", "api.example.com", or "https://bakebase.agent-manifest.com".

Output parameters:

- `domain` (string)
- `manifest` (object): Parsed AMP manifest object (agentmanifest-0.2 or agentmanifest-0.3).
- `manifest_url` (string)
- `origin` (string)
- `tried_urls` (array)

### `validate_manifest_syntax` (~76 tokens)

Validate AMP manifest JSON Schema

Validate a manifest JSON string or object against the official AMP JSON Schema for its spec_version (agentmanifest-0.2 or agentmanifest-0.3). Returns errors or a success_token.

Input parameters:

- `manifest` (required): Either a JSON string of the manifest, or a parsed manifest object with spec_version, name, endpoints, etc.

Output parameters:

- `errors` (array)
- `schema_checked` (string|null)
- `spec_version` (string|null)
- `success_token` (string|null)
- `valid` (boolean)

### `check_agent_permissions` (~158 tokens)

Check action against AMP manifest constraints

Given an intended HTTP action (method + path or full URL) and a manifest, determine whether the action aligns with declared endpoints, authentication, payment onboarding, rate limits, and language in agent_notes.

Input parameters:

- `action` (string, required): Intended operation, e.g. "POST /baking/validate-mix", "GET /health", or "POST https://api.example.com/v1/search".
- `intends_unauthenticated` (boolean): Set true if the agent plans to call the API without credentials.
- `manifest` (object, required): Parsed AMP manifest object (agentmanifest-0.2 or agentmanifest-0.3).
- `payment_onboarded` (boolean): Set true if AMP payment onboarding is already complete for this API.

Output parameters:

- `action` (object)
- `compliant` (boolean)
- `findings` (array)
- `matched_endpoint`
- `verdict` (string)

### `submit_api_to_amp_registry` (~83 tokens)

Submit API to AMP registry

Submit an HTTPS API origin for AMP registry listing after the manifest is live at /.well-known/agent-manifest.json. Returns a submission_id; poll with check_amp_submission_status.

Input parameters:

- `api_url` (string, required): HTTPS API origin where /.well-known/agent-manifest.json is served, e.g. "https://bakebase.agent-manifest.com".

Output parameters:

- `message` (string)
- `status` (string)
- `status_poll_url` (string)
- `status_url` (string)
- `submission_id` (string)

### `check_amp_submission_status` (~44 tokens)

Check AMP registry submission status

Poll validation/listing progress for a submission_id returned by submit_api_to_amp_registry.

Input parameters:

- `submission_id` (string, required): Submission id returned by submit_api_to_amp_registry.

Output parameters:

- `created_at` (string)
- `error` (string)
- `listing_id` (string)
- `listing_url` (string)
- `message` (string)
- `status` (string)
- `submission_id` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 75
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 76
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-11: 71
- 2026-10-04: 71
- 2026-10-03: 56

## Common questions

### What is the Agent Manifest Protocol (AMP) MCP server?

Agent Manifest Protocol (AMP) is an MCP server listed in the public MCP registry as com.agent-manifest/amp-mcp. Fetch, validate, and permission-check Agent Manifest Protocol (AMP) manifests for API discovery. This page covers its npm package (@agentmanifest/mcp-server).

### Is the Agent Manifest Protocol (AMP) MCP server safe to use?

Agent Manifest Protocol (AMP) scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Agent Manifest Protocol (AMP) MCP server expose?

Agent Manifest Protocol (AMP) exposes 5 tools: fetch_manifest_by_domain, validate_manifest_syntax, check_agent_permissions, submit_api_to_amp_registry, check_amp_submission_status. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

### Is the Agent Manifest Protocol (AMP) MCP server still maintained?

Agent Manifest Protocol (AMP) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Agent Manifest Protocol (AMP) MCP server under?

Agent Manifest Protocol (AMP) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@agentmanifest/mcp-server
- Socket report: https://socket.dev/npm/package/@agentmanifest/mcp-server
- Repository: https://github.com/AMProtocol/AMP
- Website: https://agent-manifest.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/com-agent-manifest-amp-mcp/agentmanifest-mcp-server