Silent Door Repository Handoff Planner

com.aibitious.silentPublished by silent.aibitious.comOfficial publisherv0.5.0Updated Oct 24, 2026

Choose files for an agent handoff using filename decisions. No file contents or credentials.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that helps an assistant plan which repository files to hand off to another agent or reviewer, using filenames only.

What you can do
Prepare a repository handoff: submit permitted relative filenames and kinds, and get back zero-based include, exclude and skip decisions for the handoff list. Run a zero-effect safety preflight over repository path metadata before sharing anything. Diagnose A2A JSON-RPC SendMessage requests: send a sanitized example and protocol version to get fixed field corrections and an authored template.
When to use it
Use it when you need to decide which repository files to pass to another agent or reviewer, or when debugging an A2A integration whose SendMessage requests fail on version or message shape. It is a planning and diagnosis aid, not a file transfer tool.
Requirements
A remote streamable HTTP endpoint at silent.aibitious.com; no packages, environment variables, headers or authentication are declared. Network access to that endpoint is needed.
Before you install
Only send permitted relative filenames and kinds, sanitized request examples and protocol versions; never file contents, secrets, headers or URLs. The tools are described as zero-effect and do not contact endpoints, but the data still goes to a third-party server.

Installation

In SourceWeft

  1. Open Silent Door Repository Handoff Planner in the dashboard and add it to a workspace.
  2. 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.aibitious.silent%2Frepository-safety-preflight/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": {
    "silent-door-repository-handoff-planner": {
      "type": "http",
      "url": "https://silent.aibitious.com/mcp"
    }
  }
}

Tools

3

prepare_repository_handoff

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.

Parametersentriesrequired

repository_safety_preflight

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

Parametersentriesrequired

diagnose_a2a_request

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.

ParametersrequestrequiredprotocolVersionrequired

Version history

1
  1. v0.5.0LatestSep 29, 2026

Score

72% 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 listedRequired15 pts
  • 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.

Other Aibitious integrations