Fiber AI
Search companies, enrich contacts, and reveal emails and phones from your AI agent.
https://mcp.fiber.ai/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- fiber-core
- Version
- 3.2.0
- Capability keys
- experimental, logging, prompts, resources, tools, extensions
- Tool names
- search_endpoints, list_tag_packs, list_all_endpoints, get_endpoint_details_full, call_operation
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 choi
Reported Aug 17, 2026, 05:03 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 35ms
- respondsMCP initialize · 8s limit · HTTP 200 · 299ms
- respondsMCP initialize · 8s limit · HTTP 200 · 221ms
- respondsMCP initialize · 8s limit · HTTP 200 · 478ms