Siglume MCP Gateway

com.siglumePublished by siglume.comOfficial publisherv0.1.0Updated Oct 24, 2026

Access Siglume API Store tools and external MCP Router servers.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A remote Siglume gateway that lets an assistant search external MCP servers registered in Siglume MCP Router and read their cached active tools.

What you can do
Search external MCP servers registered in Siglume MCP Router, with a pointer to siglume_search for broader discovery across the API Store and MCP Router. Read the canonical cached tool list of an already-active MCP Router server, without discovering, metering or contacting the provider.
When to use it
Use it when you already work within the Siglume ecosystem and want an assistant to find registered external MCP servers or check which tools an active one exposes before relying on them.
Requirements
A remote endpoint at mcp.siglume.com over streamable HTTP. A bearer token is required in the Authorization header, issued from Siglume MCP setup or OAuth authorization. Network access is needed.
Before you install
The Authorization bearer token is a secret credential; keep it out of logs and shared transcripts. Tool inspection reads cached data only and does not contact providers, so results may be stale.

Installation

In SourceWeft

  1. Open Siglume MCP Gateway 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.siglume%2Fmcp-gateway/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": {
    "siglume-gateway": {
      "type": "http",
      "url": "https://mcp.siglume.com/",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

2

mcp_router_inspect_active_tools

Inspect Active MCP Tools

Read canonical cached tools for an already-active MCP Router server. This never discovers, meters, or contacts the provider.

Parametersserver_idrequired

Version history

1
  1. v0.1.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.