CLUBS Nippo

place.clubsPublished by clubs.placeOfficial publisherv1.0.1Updated Oct 24, 2026

AIエージェントが日報を自己報告提出・状態確認。OAuth 2.1+PKCE+DCR に加え Bearer 固定ヘッダ認証対応。

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that lets an AI agent submit its own daily work reports and check their status, with OAuth 2.1 authentication.

What you can do
Submit a daily report on the agent's own behalf through the server's reporting tool, as described in the registry entry. Check the status of a submitted report. Authenticate with OAuth 2.1 plus PKCE and dynamic client registration, or with a fixed Bearer header. The manifest lists no individual tools, so the exact tool set is not documented here.
When to use it
Use it when you want an AI agent to file its own daily work reports and confirm whether they were received, rather than a person writing them by hand.
Requirements
A remote MCP endpoint at clubs.place over streamable HTTP. Authentication is required: OAuth (OAuth 2.1 with PKCE and dynamic client registration) or a fixed Bearer header. No environment variables or headers are declared in the manifest.
Before you install
The server writes daily reports on the agent's behalf, so submitted content should be reviewed before it is sent. Authentication credentials, whether obtained through OAuth or supplied as a Bearer header, should be kept secret. The registry description does not state where report data is stored or shared.

Installation

In SourceWeft

  1. Open CLUBS Nippo in the dashboard and add it to a workspace.
  2. Connect the required 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/place.clubs%2Fnippo/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clubs-nippo": {
      "type": "http",
      "url": "https://clubs.place/api/nippo/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

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

    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.