← Registry

Developer Tools

fightingclubfinder.com

Lists and searches pages with full-text search capabilities.

1 endpoint2 known toolsFirst detected June 3, 2026Last detected June 10, 2026

ENDPOINT 1

https://fightingclubfinder.com/mcp

No auth detected

Known tools 2

list_pages

Lists all available pages with titles, descriptions and routes.

Inferred read-only
search_pages

Search pages by title, description, route, headings, keywords, and content using full-text search.

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.fightingclubfinder-com]
url = "https://fightingclubfinder.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "fightingclubfinder-com": {
      "type": "http",
      "url": "https://fightingclubfinder.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: fightingclubfinder-com
Remote MCP URL: https://fightingclubfinder.com/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": {
    "fightingclubfinder-com": {
      "url": "https://fightingclubfinder.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "fightingclubfinder-com": {
      "type": "http",
      "url": "https://fightingclubfinder.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "fightingclubfinder-com",
  "transport": "streamable-http",
  "url": "https://fightingclubfinder.com/mcp"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for fightingclubfinder.com was fetched 2026-09-15T19:57:10.765Z.

Trust status Trusted

fightingclubfinder.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

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