← Registry

General Tools

timberandtackle.guide

Provides general-purpose tools through the Model Context Protocol.

1 endpoint4 known toolsFirst detected September 7, 2026Last detected September 7, 2026

ENDPOINT 1

https://timberandtackle.guide/api/mcp

No auth detected

MCP server metadata

Name
timber-tackle
Version
1.0.0
Capabilities
tools
Server instructions

Flat-fee booking software for hunting and fishing guides — the guide's home base, never a marketplace. Pricing comes from the site's single pricing module; every competitor figure is read from the competitor's own pages on a verified date, and an unpublished rate is stated as unpublished, never estimated. Read-only; touches no guide, booking or client.

Known tools 4

get_pricing

Retrieve Timber & Tackle's current pricing — the flat monthly and annual price, whether the founding rate is still open and when it closes, and the standard price after — plus the model: free until a guide accepts their first booking, never a cut of a client the guide brought.

Inferred read-only
list_competitors

List every booking marketplace and booking-software product Timber & Tackle keeps a verified fee-model record on, split into MARKETPLACES it works alongside (they find strangers, which it does not do) and BOOKING SOFTWARE it replaces.

Inferred read-only
get_competitor_fees

Retrieve the verified fee model for one competitor — commission or subscription, what is added to the client's bill, what is published and what is NOT (stated as a fact, never estimated), where their model is genuinely fairer, and the sources with the date each was checked.

Inferred read-only
compare_trip_cost

Calculate what a guide keeps from one trip under Timber & Tackle's flat fee versus a named competitor's published commission or client-fee model, from the trip price and trips per month.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.timber-tackle]
url = "https://timberandtackle.guide/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "timber-tackle": {
      "type": "http",
      "url": "https://timberandtackle.guide/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: timber-tackle
Remote MCP URL: https://timberandtackle.guide/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "timber-tackle": {
      "url": "https://timberandtackle.guide/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "timber-tackle": {
      "type": "http",
      "url": "https://timberandtackle.guide/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "timber-tackle",
  "transport": "streamable-http",
  "url": "https://timberandtackle.guide/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.