Read your private animal sightings and mark species seen with a revocable account key.
One address for any MCP client. Your key stays in your Odel vault.
At most: creates or changes data: records, files, settings.
Odel charges nothing per call. The publisher may charge for its own service.
Odel could not list its tools without signing in.
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:
The account server also reads your synced sightings. A read-write key can mark a catalog species seen.
To configure account access:
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.