Hosting

Local stdio process

Transport

stdio

Endpoint

Local process; no hosted endpoint documented

Authentication

No credentials were configured; the tested read-only tool “specbridge_list_specs” succeeded in an isolated environment. Other tools may have additional requirements.

Requirements

• Node.js 18+
• The public install config and runtime call passed; npm metadata did not declare a repository URL.

Setup steps

1. npx -y specbridge@1.0.2

Inventory varies with local API specs; stored eleven rows are not a complete invariant tool set.

• specbridge_list_specs

  List all OpenAPI specification files in the specs folder

  01
• specbridge_get_spec

  Get the content of a specific OpenAPI specification file

  Parameters: filename
  02
• specbridge_update_spec

  Update the content of a specific OpenAPI specification file

  Parameters: filename, content
  03
• specbridge_download_spec

  Download an OpenAPI specification from a URL and save it to the specs folder

  Parameters: url, filename
  04
• apisguru_listAPIs

  List all APIs in the APIs.guru directory with links to OpenAPI definitions

  05
• apisguru_getProviders

  List all API providers in the APIs.guru directory

  06
• apisguru_getProvider

  List all APIs for a particular provider

  Parameters: provider
  07
• apisguru_getServices

  List all service names for a particular provider

  Parameters: provider
  08
• apisguru_getAPI

  Get details for a specific API version (without service name)

  Parameters: provider, api
  09
• apisguru_getServiceAPI

  Get details for a specific API version with service name

  Parameters: provider, service, api
  10
• apisguru_getMetrics

  Get basic metrics for the APIs.guru directory (number of APIs, endpoints, etc.)

  11

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Runtime verification covered one read-only tool call (specbridge_list_specs); other listed tools were not individually exercised.
• The npm package metadata did not declare a repository URL; the repository link comes from the public MCP.Directory profile.
• A successful list-specs response was tested without a user-provided OpenAPI spec folder; generated API-specific tools were not tested.
• {}

• MCP.Directory public profile

  Name, description, publisher identifier, categories, transport, tool inventory, and install configuration.

• Linked publisher repository

  Repository URL linked from the public profile; any npm repository difference is recorded separately.

• npm registry metadata

  Published package version 1.0.2 checked before launch. Registry metadata did not declare a repository URL.

• maintainer repository documentation

  Maintainer README says tools are generated from whatever OpenAPI specs are present and identifies no fixed universal inventory; stored 11 is a snapshot only.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.