Koskamo

Agent Manifest Protocol MCP

An MCP server that enables AI agents to fetch, validate, and check permissions for Agent Manifest Protocol (AMP) manifests, facilitating autonomous API discovery at the origin manifest.

Visit Agent Manifest Protocol

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Agent Manifest Protocol MCP logo, by Agent Manifest ProtocolVendor evidenceLegacy SSENo sign-inEndpoint checked 2026-11-01Operated by Agent Manifest Protocol
MCP endpoint (Legacy SSE)
https://mcp.agent-manifest.com/mcp
Vendor documentation

What you can do with it

  • Fetch manifest by domain
  • Validate manifest syntax
  • Check agent permissions
  • Submit API to AMP registry

Source and maintenance

Vendor evidenceRegistry 0.1.5
mcp-registry: com.agent-manifest/amp-mcp@0.1.5Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
agent-manifest-protocol 0.1.0
MCP protocol
2025-06-18
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

You are connected to the official Agent Manifest Protocol (AMP) MCP server. Use fetch_manifest_by_domain to discover /.well-known/agent-manifest.json (and fallbacks) for any API origin. Use validate_manifest_syntax before trusting manifest JSON. Use check_agent_permissions before calling an API operation to see if it matches declared endpoints, auth, payment, and agent_notes constraints. AMP complements MCP: MCP carries tools; AMP declares what remote agents/APIs allow, cost, and how to authenticate.

Tools

3 advertised

fetch_manifest_by_domain — Fetch AMP manifest by domain
Advertised by the server during the last successful anonymous check.

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.

fetch_manifest_by_domain input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "minLength": 1,
      "description": "API hostname or URL origin without a path, e.g. \"example.com\", \"api.example.com\", or \"https://bakebase.agent-manifest.com\"."
    }
  },
  "additionalProperties": false
}
validate_manifest_syntax — Validate AMP manifest JSON Schema
Advertised by the server during the last successful anonymous check.

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.

validate_manifest_syntax input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "manifest"
  ],
  "properties": {
    "manifest": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "description": "Parsed AMP manifest object (agentmanifest-0.2 or agentmanifest-0.3).",
          "additionalProperties": {}
        }
      ],
      "description": "Either a JSON string of the manifest, or a parsed manifest object with spec_version, name, endpoints, etc."
    }
  },
  "additionalProperties": false
}
check_agent_permissions — Check action against AMP manifest constraints
Advertised by the server during the last successful anonymous check.

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.

check_agent_permissions input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "action",
    "manifest"
  ],
  "properties": {
    "action": {
      "type": "string",
      "minLength": 1,
      "description": "Intended operation, e.g. \"POST /baking/validate-mix\", \"GET /health\", or \"POST https://api.example.com/v1/search\"."
    },
    "manifest": {
      "type": "object",
      "description": "Parsed AMP manifest object (agentmanifest-0.2 or agentmanifest-0.3).",
      "additionalProperties": {}
    },
    "payment_onboarded": {
      "type": "boolean",
      "description": "Set true if AMP payment onboarding is already complete for this API."
    },
    "intends_unauthenticated": {
      "type": "boolean",
      "description": "Set true if the agent plans to call the API without credentials."
    }
  },
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
329 ms
95th percentile latency
329 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 329 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport sse agent-manifest-protocol-mcp https://mcp.agent-manifest.com/mcp

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "agent-manifest-protocol-mcp": {
      "type": "sse",
      "url": "https://mcp.agent-manifest.com/mcp",
      "disabled": false
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport sse agent-manifest-protocol-mcp https://mcp.agent-manifest.com/mcp

Let your agent find its tools

Find servers like Agent Manifest Protocol MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,747

Do you run Agent Manifest Protocol MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing