Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Fiber AI

REMOTE · MCP.FIBER.AI · 2 COMPONENTS · SCANNED AUG 3

Search companies, enrich contacts, and reveal emails and phones from your AI agent.

+5 this week 64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 723 tokens (~90/item across 8 items; 5 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.fiber.ai

# add to Claude Code
claude mcp add --transport http ai-fiber-mcp https://mcp.fiber.ai/mcp
# ~/.codex/config.toml
[mcp_servers.ai-fiber-mcp]
url = "https://mcp.fiber.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-fiber-mcp": {
      "type": "remote",
      "url": "https://mcp.fiber.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-fiber-mcp --url https://mcp.fiber.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-fiber-mcp:
    url: "https://mcp.fiber.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "ai-fiber-mcp": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.fiber.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.fiber.ai CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 29 May 2026 29 Nov 2026 RSA 2048 SHA256-RSA c146d2c4c9ecbe87646f81ce4522352
SANs: mcp.fiber.ai
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5
DNSSEC insecure

Validation of mcp.fiber.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
fiber.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.fiber.ai/mcp Verified 200
http (plaintext) http://mcp.fiber.ai/mcp HTTPS enforced 301 https://mcp.fiber.ai/mcp
MCP tools — 5 exposed · ~371 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
call_operation ~120

Execute 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: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.

NameTypeReqDescription
operationIdstringyes
params

Structured output declared, but exposes no named fields.

No examples provided.

get_endpoint_details_full ~86

Get 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, response schema, and example usage.

NameTypeReqDescription
operationIdstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_all_endpoints ~42

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

NameTypeReqDescription
limit
search
tagPack
tags

Structured output declared, but exposes no named fields.

No examples provided.

list_tag_packs ~32

List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_endpoints ~91

Canonical 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.

NameTypeReqDescription
constraints
excludedTags
limit
preferredTags
querystringyes
tagPack

Structured output declared, but exposes no named fields.

No examples provided.