Skip to content

Agent Manifest Protocol (AMP)

by agent-manifest.com · remote · local (npm) · no sign-in to list tools · v0.1.5 · published by com.agent-manifest

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

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 info
  • Infocheck_agent_permissions

    The input schema at properties.intends_unauthenticated.description mentions "credentials".

    Matched text

    inputSchema.properties.intends_unauthenticated.description: "...the agent plans to call the API without credentials."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • check_agent_permissionsGiven an intended HTTP action (method + path or full URL) and a manifest, determine whether the action aligns with declared endpoints, authentication, payment onboarding, rate limi…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The input schema at properties.intends_unauthenticated.description mentions "credentials".

      Matched text

      inputSchema.properties.intends_unauthenticated.description: "...the agent plans to call the API without credentials."

      What this check looks for
    Description, as the server wrote it
    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.
Only reads 2Claude Code: allow
  • fetch_manifest_by_domainResolve an API origin from a domain (e.g.No findings

    Why it is in this group

    • The name "fetch_manifest_by_domain" says "fetch": a word for reading.
    Description, as the server wrote it
    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.
  • validate_manifest_syntaxValidate a manifest JSON string or object against the official AMP JSON Schema for its spec_version (agentmanifest-0.2 or agentmanifest-0.3).No findings

    Why it is in this group

    • The name "validate_manifest_syntax" says "validate": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.5. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__amp__fetch_manifest_by_domain",
      "mcp__amp__validate_manifest_syntax"
    ],
    "ask": [
      "mcp__amp__check_agent_permissions"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as amp. Review it before you use it.