Foxhound

io.github.caleb-lovePublished by GitHub account caleb-lovev0.3.0Updated Oct 24, 2026

MCP server for querying Foxhound traces from Claude Code, Cursor, and other MCP clients

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.caleb-love/foxhound
Transport: STDIO
Runtime: Desktop only
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 the GitHub account caleb-love for this listing. That does not show the account is the product's maker.

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/io.github.caleb-love%2Ffoxhound.svg)](https://sourceweft.com/mcp/io.github.caleb-love%2Ffoxhound?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant query Foxhound traces from MCP clients such as Claude Code and Cursor.

What you can do: Foxhound is a local stdio MCP server that exposes Foxhound trace data to MCP-capable clients. According to its registry description, it is used for querying Foxhound traces from Claude Code, Cursor, and other MCP clients. The manifest does not list individual tools, so the exact query operations are not documented here.
When to use it: Consider it when you already use Foxhound for tracing and want an assistant inside Claude Code, Cursor, or another MCP client to look up that trace data without leaving the editor. It is desktop-only, so it is not intended for browser-based or hosted clients.
Requirements: Runs as a local process over stdio, installed from the npm package @foxhound-ai/mcp-server, so Node.js is needed. Requires a Foxhound API key supplied through the FOXHOUND_API_KEY environment variable; the key is created at foxhound.dev. The optional FOXHOUND_ENDPOINT variable sets the API endpoint and defaults to

Before you install

The server requires a secret, FOXHOUND_API_KEY, which grants access to your Foxhound account data; keep it out of shared configuration and logs. The default endpoint is a local HTTP address, so trace data may be sent to whatever host that endpoint points to if it is changed. No tools are listed in the manifest, so review what the server can read or change before installing.

Installation

In SourceWeft

Open Foxhound in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.0LatestSep 16, 2026

Score

25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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.