All servers · Email & messaging · Company & business data
Fiber AI
ai.fiber/mcp · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | experimental, extensions, logging, prompts, resources, tools |
| Tool definitions | 5 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Search companies, enrich contacts, and reveal emails and phones from your AI agent.
Connect
streamable-http · https://mcp.fiber.ai/mcp/v2/
claude mcp add --transport http mcp https://mcp.fiber.ai/mcp/v2/{
"mcpServers": {
"mcp": {
"url": "https://mcp.fiber.ai/mcp/v2/"
}
}
}streamable-http · https://mcp.fiber.ai/mcp
claude mcp add --transport http mcp https://mcp.fiber.ai/mcp{
"mcpServers": {
"mcp": {
"url": "https://mcp.fiber.ai/mcp"
}
}
}Tools as reported by the server
search_endpointsCanonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key.list_tag_packsList curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).list_all_endpointsList available Fiber API endpoints with optional tag/search filtering.get_endpoint_details_fullGet COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body schema, rescall_operationExecute any Fiber API operation by operationId. IMPORTANT: - Most operations require `apiKey` in the request body. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes. Args: operationId: Th
Repository · JSON · Text for agents · Registry updated 2026-03-05