BeyondFolder Directories

com.beyondfolderPublished by beyondfolder.comOfficial publisherv2.0.0Updated Oct 24, 2026

Track SaaS directory submissions for your products via API key–gated Streamable HTTP MCP.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant track SaaS directory submissions for your products through a remote, API-key-gated MCP endpoint.

What you can do
BeyondFolder Directories is a remote Streamable HTTP MCP server that lets an assistant work with SaaS directory submission tracking for your products. It is reached at a hosted endpoint rather than installed locally, and access is gated by an API key. No tool list is published in the supplied material, so the exact operations available are not described here.
When to use it
Consider it when you list products in SaaS directories and want an assistant to check or follow the status of those submissions without leaving the chat. It is aimed at teams already using BeyondFolder Directories who want that data reachable through an MCP client.
Requirements
A remote MCP client that supports Streamable HTTP, network access to the provider's hosted endpoint, and a BeyondFolder Directories API key (prefix bfdir_) sent as an Authorization bearer token. Keys are created in the provider's dashboard.
Before you install
The Authorization header carries a secret API key, so treat it as a credential and avoid exposing it in logs or shared configuration. The server is hosted by a third party, so submission data you query passes through that provider. No tool list is published, so verify what the server can read or change before relying on it.

Installation

In SourceWeft

  1. Open BeyondFolder Directories 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.beyondfolder%2Fdirectories/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": {
    "beyondfolder-directories": {
      "type": "http",
      "url": "https://beyondfolder.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

60% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.