Agent Manifest Protocol (AMP)
NPM · @AGENTMANIFEST/MCP-SERVER · 2 COMPONENTS
Fetch, validate, and permission-check Agent Manifest Protocol (AMP) manifests for API discovery.
Available components
Last scanned (3 hours ago)
Scores higher than 65% of npm servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 40 of 122 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 584 tokens (~116/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +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.
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@agentmanifest/mcp-server@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent_permissions Check action against AMP manifest constraints ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | – |
| compliant | boolean | yes | – |
| findings | array | yes | – |
| matched_endpoint | – | yes | – |
| verdict | string | yes | – |
No examples provided.
check_amp_submission_status Check AMP registry submission status ~44
Poll validation/listing progress for a submission_id returned by submit_api_to_amp_registry.
| Name | Type | Req | Description |
|---|---|---|---|
| submission_id | string | yes | Submission id returned by submit_api_to_amp_registry. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | string | – | – |
| error | string | – | – |
| listing_id | string | – | – |
| listing_url | string | – | – |
| message | string | – | – |
| status | string | yes | – |
| submission_id | string | yes | – |
| url | string | yes | – |
No examples provided.
fetch_manifest_by_domain Fetch AMP manifest by domain ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | API hostname or URL origin without a path, e.g. "example.com", "api.example.com", or "https://bakebase.agent-manifest.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| manifest | object | yes | Parsed AMP manifest object (agentmanifest-0.2 or agentmanifest-0.3). |
| manifest_url | string | yes | – |
| origin | string | yes | – |
| tried_urls | array | yes | – |
No examples provided.
submit_api_to_amp_registry Submit API to AMP registry ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | yes | HTTPS API origin where /.well-known/agent-manifest.json is served, e.g. "https://bakebase.agent-manifest.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| status | string | yes | – |
| status_poll_url | string | yes | – |
| status_url | string | yes | – |
| submission_id | string | yes | – |
No examples provided.
validate_manifest_syntax Validate AMP manifest JSON Schema ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | – | yes | Either a JSON string of the manifest, or a parsed manifest object with spec_version, name, endpoints, etc. |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | array | yes | – |
| schema_checked | string|null | yes | – |
| spec_version | string|null | yes | – |
| success_token | string|null | yes | – |
| valid | boolean | yes | – |
No examples provided.
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.
npm · @agentmanifest/mcp-server
claude mcp add com-agent-manifest-amp-mcp -- npx -y @agentmanifest/mcp-server
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.