What it does
The account server reads the sightings you have synced to Animal Checklist. A read-write key also lets an MCP client mark a catalog species as seen. It is one of two endpoints the publisher offers: a public, read-only species catalog returns names, habitats, countries, photos and source credits, and the account endpoint covers personal data.
Use it when an MCP app needs to work with your own sightings, such as reviewing what you have recorded or logging a new species. A read-only key is enough for review. Choose the read-write key only when the app must mark animals seen.
Create a personal key on the Account page, copy it when it appears, and add it to the HTTP header in your client configuration. Keep the key in the client's secret store and out of any repository. Remove the key on the same page when you stop using the app. The endpoints support MCP 2026-07-28 and legacy clients. Event notifications for sighting changes are available only after the operator enables the relay; you can check readiness with server/discover using your key.
Limitations and requirements
Requires an Animal Checklist account and a personal MCP key. Keys expire after 90 days and are shown only once when created. A read-write key is needed to mark species as seen. Keys must not be committed to a repository. Sighting-change events depend on the operator enabling the relay. The keyless public catalog has no Events capability.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Animal Checklist Account
Read your private animal sightings and mark species seen with a revocable account key.
v1.1.0As shown on registry.modelcontextprotocol.io when we last read it