Marketing

fiber.ai

Provides APIs for searching companies and people and enriching their profiles, useful for lead generation and sales intelligence.

3 endpoints15 known toolsFirst detected June 5, 2026Last detected August 24, 2026

ENDPOINT 1

https://mcp.fiber.ai/mcp/v2

No auth detected

MCP server metadata

Name: fiber-api
Version: 3.2.0

Capabilities

experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui

Server instructions

Fiber AI API - Pre-built tools for common operations. These tools provide direct access to specific Fiber APIs with proper input schemas. Each tool has detailed documentation about required and optional parameters. EXAMPLES: - api_sync_contact_enrichment: Get emails/phones from LinkedIn profile - api_company_search: Search companies by criteria - api_people_search: Search people by criteria AUTHENTICATION: - Pass apiKey directly in the tool call parameters, OR - Configure mcp.json headers with x-api-key/x-apikey (Authorization: Bearer <apiKey> also works).

Known tools 10

companySearch_tool

OperationId: companySearch.

Inferred read-only

peopleSearch_tool

OperationId: peopleSearch.

Inferred read-only

profileLiveEnrich_tool

OperationId: profileLiveEnrich.

Inferred read-only

companyLiveEnrich_tool

OperationId: companyLiveEnrich.

Inferred read-only

getQuickstartScript_tool

OperationId: getQuickstartScript.

Inferred read-only

getOrgCredits_tool

OperationId: getOrgCredits.

Inferred read-only

getRateLimits_tool

OperationId: getRateLimits.

Inferred read-only

getAutoTopupSettings_tool

OperationId: getAutoTopupSettings.

Inferred read-only

cardsAttach_tool

OperationId: cardsAttach.

Inferred read-only

getAllApiKeys_tool

OperationId: getAllApiKeys.

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.fiber-api]
url = "https://mcp.fiber.ai/mcp/v2"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fiber-api": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp/v2"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fiber-api
Remote MCP URL: https://mcp.fiber.ai/mcp/v2

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": {
    "fiber-api": {
      "url": "https://mcp.fiber.ai/mcp/v2"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fiber-api": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp/v2"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fiber-api",
  "transport": "streamable-http",
  "url": "https://mcp.fiber.ai/mcp/v2"
}

MCP Inspector

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

ENDPOINT 2

https://mcp.fiber.ai/mcp/v3

Auth required

Known tools 0

No tool metadata was available in the registry cache.

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.fiber-ai]
url = "https://mcp.fiber.ai/mcp/v3"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "fiber-ai": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp/v3",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: fiber-ai
Remote MCP URL: https://mcp.fiber.ai/mcp/v3

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "fiber-ai": {
      "url": "https://mcp.fiber.ai/mcp/v3",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "fiber-ai": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp/v3",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "fiber-ai bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "fiber-ai",
  "transport": "streamable-http",
  "url": "https://mcp.fiber.ai/mcp/v3",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

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

ENDPOINT 3

https://mcp.fiber.ai/mcp

No auth detected

MCP server metadata

Name: fiber-core
Version: 3.2.0

Capabilities

experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui

Server instructions

Fiber AI API - Discovery and execution tools. HOW TO USE (3 steps): 1. search_endpoints("your intent", constraints=[...], preferredTags=[...], tagPack="...") - Choose the best operations with ranked alternatives 2. get_endpoint_details_full("operationId") - Get complete schema and examples for complex fields 3. call_operation("operationId", {body: {...}}) - Execute EXAMPLES: - "find companies" → search_endpoints("find AI companies in SF", constraints=["country", "headcount"]) → companySearch - "get email" → search_endpoints("reveal work email for known profile") → syncContactEnrichment - "find people" → search_endpoints("find VP engineering in fintech") → peopleSearch AUTHENTICATION: Every API call requires an apiKey parameter. Ask the user for their Fiber API key (starts with sk_live_ or sk_test_) and include it in every call_operation request body. FOR COMPLEX WORKFLOWS (bulk operations, audiences): Read llms://fiber.ai/llms.txt for step-by-step guidance. For API choice among similar operations, read llms://fiber.ai/api-selector.

Known tools 5

search_endpoints

Canonical API selection tool for endpoint discovery and ranking.

Inferred read-only

list_tag_packs

List curated tag packs for large tool catalogs.

Inferred read-only

list_all_endpoints

List available Fiber API endpoints with optional tag/search filtering.

Inferred read-only

get_endpoint_details_full

Get COMPLETE schema and details for a specific API operation.

Inferred read-only

call_operation

Execute any Fiber API operation by operationId.

Potential side effects

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.fiber-core]
url = "https://mcp.fiber.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "fiber-core": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: fiber-core
Remote MCP URL: https://mcp.fiber.ai/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": {
    "fiber-core": {
      "url": "https://mcp.fiber.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "fiber-core": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "fiber-core",
  "transport": "streamable-http",
  "url": "https://mcp.fiber.ai/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 fiber.ai was fetched 2026-08-29T14:15:07.800Z.

Trust status Trusted

fiber.ai 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.