FoxNose Knowledge

net.foxnosePublished by foxnose.netOfficial publisherv2.0.0Updated Oct 24, 2026

Hybrid search, schema introspection and record read/write over FoxNose collections

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & Memory

Overview

AI-generated overview

Lets an assistant search FoxNose collections, inspect their schemas, and read or write records through a hosted remote endpoint.

What you can do
FoxNose Knowledge exposes FoxNose collections to an assistant over a remote streamable HTTP endpoint. It supports hybrid search, schema introspection, and reading and writing records. Access is scoped to the API key used, so the assistant can only reach collections that key can read over REST.
When to use it
Useful when your content or data lives in FoxNose and you want an assistant to search it, look up its structure, or create and update records without building a custom integration.
Requirements
A remote endpoint at mcp.foxnose.net over streamable HTTP. A FoxNose API key pair created per environment in the dashboard under Flux API > Access, or via the Management API, sent as a bearer token in the Authorization header. The x-foxnose-prefix header selects which Flux API to expose and is only needed when the key can read more than one.
Before you install
The Authorization header carries a FoxNose API key pair; treat it as a secret and scope it narrowly. The server can write records, so assistant actions may create or change data in your collections. Access is limited to what the key can read over REST, so key scopes determine exposure.

Installation

In SourceWeft

  1. Open FoxNose Knowledge 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/net.foxnose%2Fknowledge/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": {
    "foxnose-knowledge": {
      "type": "http",
      "url": "https://mcp.foxnose.net/_mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

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

  • 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.