English Français العربية

Animal Checklist Account

Official registry Other

Read your private animal sightings and mark species seen with a revocable account key.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http animal-checklist-account 'https://animalchecklist.com/mcp/account' --header 'Authorization: <Bearer followed by your MCP key from Account settings, for example Bearer acm_...>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "animal-checklist-account": {
            "type": "http",
            "url": "https://animalchecklist.com/mcp/account",
            "headers": {
                "Authorization": "<Bearer followed by your MCP key from Account settings, for example Bearer acm_...>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Animal Checklist MCP

Animal Checklist offers two remote MCP servers over Streamable HTTP.

ServerURLAccess
Species cataloghttps://animalchecklist.com/mcpPublic, read only
Your accounthttps://animalchecklist.com/mcp/accountPersonal MCP key

The public server searches animal species and returns these details:

  • Names.
  • Habitats.
  • Countries.
  • Photos.
  • Source credits.

The account server also reads your synced sightings. A read-write key can mark a catalog species seen.

To configure account access:

  1. Create a personal key on your Account page.
  2. Choose a read key unless your MCP app must mark animals seen.
  3. Copy the key when it appears. Animal Checklist shows it only once.
  4. Remove the key from the same page when you no longer use the app.

Keys expire after 90 days.

Configure the account server with this HTTP header:

Authorization: Bearer YOUR_MCP_KEY

Keep the key in your MCP client's secret store. Do not commit it to a repository. The public mcp.json contains only the keyless catalog server because the Agent Plugins 1.0.0 format does not define portable secret references.

Both endpoints support MCP 2026-07-28 with per-request metadata and matching HTTP headers. Legacy clients retain initialization and result shapes. The authenticated account endpoint can expose checklist.sighting_changed after the operator enables its safe relay. Check server/discover with your key for Events readiness. The keyless catalog has no Events capability. See the Events contract.

The server.json and server-account.json files describe both servers for the official MCP Registry. The mcp.json file provides a portable public-server connection. See the developer guide for tool details and a client config example.

Frequently asked questions

What is Animal Checklist Account?

Read your private animal sightings and mark species seen with a revocable account key.

How do I install Animal Checklist Account?

It runs as a remote server. In Claude Code: claude mcp add --transport http animal-checklist-account 'https://animalchecklist.com/mcp/account' --header 'Authorization: <Bearer followed by your MCP key from Account settings, for example Bearer acm_...>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Animal Checklist Account need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Animal Checklist Account open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Animal Checklist Account?

It is published by ArneFfm. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.