Back to Browse

Animal Checklist Agents MCP Server

by ArneFfm
Developer ToolsLow Risk10.0RemoteNew
Free

Search animals in eight languages with habitats, countries, photos and source credits.

About

Search animals in eight languages with habitats, countries, photos and source credits.

Remote endpoints: streamable-http: https://animalchecklist.com/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (6/6 approved).

4 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-arneffm-animal-checklist": {
      "url": "https://animalchecklist.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

Reviews

No reviews yet

Be the first to review this server!