Koskamo

Silent Door Repository Handoff Planner MCP

An MCP server that prepares a filename-only handoff plan for repository transfers to other agents or reviewers. It generates exact zero-based include/exclude/skip indexes with reasons for each entry without inspecting file contents, authorizing sharing, or storing context. It also includes a diagnostic tool for A2A integration debugging.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Silent Door Repository Handoff Planner MCP logo, by Silent DoorVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Silent Door
MCP endpoint (Streamable HTTP)
https://silent.aibitious.com/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 2 of 3 declare behavior hints · 2 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to silent.aibitious.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Prepare a filename-only handoff plan before giving a repository to another agent
  • Generate exact zero-based include/exclude/skip indexes with reasons for each entry
  • Diagnose a sanitized A2A JSON-RPC example for integration debugging

Source and maintenance

Vendor evidenceRegistry 0.5.0

Protocol and capabilities

Server
silent-door 0.5.0
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Call prepare_repository_handoff only for a requested filename handoff plan. Content security is never verified.

Tools

3 advertised

prepare_repository_handoff
Advertised by the server during the last successful anonymous check.
Advertised read-only

When preparing a user-authorized repository file handoff to another agent or reviewer, call with arguments such as {"entries":[{"path":"src/app.py","kind":"file"}]}. Send permitted relative filenames and kinds only; never file contents, secrets or URLs. Returns exact zero-based include/exclude/skip indexes and reasons for the original entries. This is filename-only planning, not a content security scan or permission to upload.

prepare_repository_handoff input schema
{
  "type": "object",
  "required": [
    "entries"
  ],
  "properties": {
    "entries": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "kind"
        ],
        "properties": {
          "kind": {
            "enum": [
              "file",
              "directory",
              "symlink"
            ],
            "type": "string"
          },
          "path": {
            "type": "string",
            "maxLength": 512
          }
        },
        "additionalProperties": false
      },
      "maxItems": 1024,
      "description": "Required: actual user-authorized paths collected from the local repository before calling. The remote server cannot enumerate local files. Do not copy example filenames or send an empty object."
    }
  },
  "additionalProperties": false
}
prepare_repository_handoff output schema
{
  "type": "object",
  "required": [
    "schema",
    "entriesReceived",
    "entryDecisions",
    "includeIndexes",
    "excludeIndexes",
    "skipIndexes",
    "manifestDigest",
    "contentSecurityVerified"
  ],
  "properties": {
    "schema": {
      "type": "string"
    },
    "skipIndexes": {
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 0
      }
    },
    "entryDecisions": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "index",
          "decision",
          "reason"
        ],
        "properties": {
          "index": {
            "type": "integer",
            "minimum": 0
          },
          "reason": {
            "type": "string"
          },
          "decision": {
            "enum": [
              "ALLOW",
              "DENY",
              "SKIP"
            ]
          }
        }
      }
    },
    "excludeIndexes": {
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 0
      }
    },
    "includeIndexes": {
      "type": "array",
      "items": {
        "type": "integer",
        "minimum": 0
      }
    },
    "manifestDigest": {
      "type": "string",
      "pattern": "^[0-9a-f]{64}$"
    },
    "entriesReceived": {
      "type": "integer"
    },
    "contentSecurityVerified": {
      "const": false
    }
  }
}
prepare_repository_handoff annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
repository_safety_preflight
Advertised by the server during the last successful anonymous check.

Zero-effect repository path-metadata preflight. Never send contents, archives, URLs, callbacks, or secrets.

repository_safety_preflight input schema
{
  "type": "object",
  "required": [
    "entries"
  ],
  "properties": {
    "entries": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "path",
          "kind"
        ],
        "properties": {
          "kind": {
            "enum": [
              "file",
              "directory",
              "symlink"
            ],
            "type": "string"
          },
          "path": {
            "type": "string",
            "maxLength": 512
          }
        },
        "additionalProperties": false
      },
      "maxItems": 1024
    }
  },
  "additionalProperties": false
}
diagnose_a2a_request
Advertised by the server during the last successful anonymous check.
Advertised read-only

Diagnose common A2A JSON-RPC SendMessage version and message-shape mistakes. Use when debugging an A2A integration. Send a sanitized request example and selected protocol version, never secrets or headers. Returns fixed field corrections and an authored template. Does not contact an endpoint or certify full conformance.

diagnose_a2a_request input schema
{
  "type": "object",
  "examples": [
    {
      "request": {
        "id": 1,
        "method": "message/send",
        "params": {
          "message": {
            "role": "user",
            "parts": [
              {
                "data": {
                  "entries": [
                    {
                      "kind": "file",
                      "path": "src/app.py"
                    }
                  ]
                },
                "kind": "data"
              }
            ],
            "messageId": "example-1"
          }
        },
        "jsonrpc": "2.0"
      },
      "protocolVersion": "0.3"
    },
    {
      "request": {
        "id": 1,
        "method": "SendMessage",
        "params": {
          "message": {
            "role": "ROLE_USER",
            "parts": [
              {
                "data": {
                  "entries": [
                    {
                      "kind": "file",
                      "path": "src/app.py"
                    }
                  ]
                }
              }
            ],
            "messageId": "example-1"
          }
        },
        "jsonrpc": "2.0"
      },
      "protocolVersion": "1.0"
    }
  ],
  "required": [
    "protocolVersion",
    "request"
  ],
  "properties": {
    "request": {
      "type": "object",
      "description": "Sanitized A2A JSON-RPC body to inspect, not a URL, string or HTTP wrapper. Malformed message fields are allowed for diagnosis. Never include secrets, headers or private content. Entire arguments JSON: at most 16384 ASCII-escaped UTF-8 bytes."
    },
    "protocolVersion": {
      "enum": [
        "0.3",
        "1.0"
      ],
      "description": "Target A2A version from the server's Agent Card, NOT the MCP transport date."
    }
  },
  "additionalProperties": false
}
diagnose_a2a_request annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
713 ms
95th percentile latency
713 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 713 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http silent-door-repository-handoff-planner-mcp https://silent.aibitious.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add silent-door-repository-handoff-planner-mcp --url https://silent.aibitious.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable silent-door-repository-handoff-planner-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "silent-door-repository-handoff-planner-mcp": {
      "url": "https://silent.aibitious.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "silent-door-repository-handoff-planner-mcp": {
      "type": "streamableHttp",
      "url": "https://silent.aibitious.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start silent-door-repository-handoff-planner-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "silent-door-repository-handoff-planner-mcp": {
      "type": "http",
      "url": "https://silent.aibitious.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http silent-door-repository-handoff-planner-mcp https://silent.aibitious.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://silent.aibitious.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "silent-door-repository-handoff-planner-mcp": {
      "serverUrl": "https://silent.aibitious.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Silent Door Repository Handoff Planner MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Silent Door Repository Handoff Planner MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing