About Animal Checklist Account
Animal Checklist Account is the authenticated endpoint for reading private, synced animal sightings and marking catalog species seen. It is for MCP clients using a personal key, with read-only access available unless write access is needed.
Key features
- 01Read synced private sightings
- 02Mark catalog species as seen
- 03Authenticate with a personal key
- 04Revoke keys from the account page
- 05Keys expire after 90 days
Use cases
- 01Review private synced sightings
- 02Update a species as seen
- 03Give an MCP client read-only sighting access
- 04Remove an account key when access is no longer needed
MCP support
This is the authenticated account endpoint of Animal Checklist's remote MCP service, accessed over Streamable HTTP with a personal key in the Authorization Bearer header. It exposes synced sightings and can mark species seen when the key has read-write access.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://animalchecklist.com/mcp/accountclaude mcp add --transport http arneffm-animal-checklist-account https://animalchecklist.com/mcp/account{"mcpServers":{"arneffm-animal-checklist-account":{"type":"http","url":"https://animalchecklist.com/mcp/account"}}}Open in Cursor{"servers":{"arneffm-animal-checklist-account":{"type":"http","url":"https://animalchecklist.com/mcp/account"}}}Open in VS Code{"mcpServers":{"arneffm-animal-checklist-account":{"type":"http","url":"https://animalchecklist.com/mcp/account"}}}{"mcpServers":{"arneffm-animal-checklist-account":{"serverUrl":"https://animalchecklist.com/mcp/account"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://animalchecklist.com/mcp/accountAuth requiredTools
Details
From the project READMEAnimal Checklist MCP
Animal Checklist offers two remote MCP servers over Streamable HTTP.
| Server | URL | Access |
|---|---|---|
| Species catalog | https://animalchecklist.com/mcp | Public, read only |
| Your account | https://animalchecklist.com/mcp/account | Personal 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:
- Create a personal key on your Account page.
- Choose a read key unless your MCP app must mark animals seen.
- Copy the key when it appears. Animal Checklist shows it only once.
- 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.