Animal Checklist
Search animals in eight languages with habitats, countries, photos and source credits.
One address for any MCP client. No sign-in needed on this server.
What it does
4 read
Grouped by tool name. At most: only reads or looks up information.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Tools
4 · grouped by tool name · checked 8 Oct 2026Read · 4Look things up
- list_categories
- search_animals
- get_animal
- list_countries
Animal 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.
