Registry Expansion Routing

com.bonissystemsPublished by bonissystems.comOfficial publisherv1.0.0Updated Oct 24, 2026

Public-registry routing map by entity kind. Read-only reference data, not a determination.

The publisher's own server: Booking Request

VerifiedStreamable HTTPWeb executable

Server details

Identifier: com.bonissystems/registry-expansion
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to bonissystems.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.bonissystems%2Fregistry-expansion.svg)](https://sourceweft.com/mcp/com.bonissystems%2Fregistry-expansion?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant look up which public registries the expansion agent would consult for each entity kind.

What you can do: The server exposes a single tool, describe_routing, which returns the registry routing map: for each entity kind, the set of public registries the expansion agent would consult. It takes no input and is read-only reference data rather than a determination.
When to use it: Use it when you want to understand, before requesting an authenticated expansion, which public registries the expansion agent would consult for each entity kind. It is reference information only, not for obtaining actual lookups or determinations.
Requirements: Remote endpoint reached over streamable HTTP at bonissystems.com; no packages, environment variables, or headers are declared.

Before you install

The tool itself is read-only and involves no personal data, but the description states that actual expansion requests are authenticated; expect credentials to be required by that later step.

Installation

In SourceWeft

Open Registry Expansion Routing in the dashboard and add it to a workspace.
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.bonissystems%2Fregistry-expansion/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": {
    "registry-expansion-routing": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/agents/registry-expansion/mcp"
    }
  }
}

Tools

describe_routing

Return the registry routing map: for each entity kind, the set of public registries the expansion agent would consult. Pure, local, no input, no PII. Use it to understand coverage before requesting an (authenticated) expansion.

Takes no parameters.

Version history

v1.0.0LatestSep 16, 2026

Score

83% 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
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.