いぬねこ帳簿 (Inuneko Chobo)

com.inuneko-choboPublished by inuneko-chobo.comOfficial publisherv1.0.0Updated Oct 24, 2026

Dog/cat breeder records (Japan): mating limits, headcount, microchips. Bearer API key required.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for Japanese dog and cat breeder records, letting an assistant work with mating limits, headcount and microchip data.

What you can do
Connect an assistant to a Japanese dog and cat breeder record service covering breeding operations such as mating limits, animal headcount and microchip records. The manifest lists no individual tools, so the exact read and write actions are not documented here. Access is through a remote endpoint authenticated with a bearer API key.
When to use it
Relevant if you manage Japanese dog or cat breeding records and want an assistant to consult or work with that data, for example around mating limits, headcount or microchips. Not useful for other kinds of animal, pet or livestock records.
Requirements
A remote endpoint at inuneko-chobo.com over streamable HTTP. A bearer API key is required in the Authorization header; an organization admin issues it in Settings > Integrations (設定 > 連携) with the mcp:invoke scope. No environment variables or local packages are declared.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. The manifest lists no tools, so whether the assistant can only read records or also change them is unclear; confirm before relying on it for updates. Breeding records may contain identifying or business-sensitive data.

Installation

In SourceWeft

  1. Open いぬねこ帳簿 (Inuneko Chobo) 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/com.inuneko-chobo%2Finuneko-chobo/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": {
    "inuneko-chobo": {
      "type": "http",
      "url": "https://inuneko-chobo.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

1
  1. v1.0.0LatestOct 24, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.