Animal Checklist Account

io.github.ArneFfmPublished by GitHub account ArneFfmv1.1.0Updated Oct 24, 2026

Read your private animal sightings and mark species seen with a revocable account key.

The publisher's own server: wcway

VerifiedStreamable HTTPWeb executableLocation & LifestyleKnowledge & Memory

Overview

AI-generated overview

A remote MCP server that lets an assistant read your private animal sightings and, with a read-write key, mark catalog species as seen.

What you can do
Read your synced animal sightings from your Animal Checklist account, including species details such as names, habitats, countries, photos and source credits, and mark a catalog species as seen when the key allows writing. The companion public catalog server, which needs no key, searches animal species and returns the same species details. The account endpoint can also expose a sighting-changed event once the operator enables its relay.
When to use it
Use it when you want an assistant to look up your own recorded sightings or to update your checklist by marking species seen, rather than only browsing the public species catalog.
Requirements
A remote endpoint at animalchecklist.com over Streamable HTTP; no local package. A personal MCP key created on your Account page, sent as the Authorization header in the form Bearer followed by the key. Choose a read key unless the app must mark animals seen. Keys expire after 90 days.
Before you install
The key grants access to your private sightings and, if read-write, can change your checklist. It is shown only once, so store it in your client's secret store and do not commit it to a repository. Remove the key from your Account page when you stop using the app.

Installation

In SourceWeft

  1. Open Animal Checklist Account in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ArneFfm%2Fanimal-checklist-account/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "animal-checklist-account": {
      "type": "http",
      "url": "https://animalchecklist.com/mcp/account",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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:

text
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.

Source: README.md at commit a8343bf

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v1.1.0LatestOct 4, 2026
  2. v1.0.0Sep 26, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wcway integrations