Fiber AI
REMOTE · MCP.FIBER.AI · 2 COMPONENTS
Search companies, enrich contacts, and reveal emails and phones from your AI agent.
Available components
Last scanned (6 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 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
- 25 Sept 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 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 13 Aug 26 0
- Tool “list_tag_packs” changed its title: List Tag Packs cosmetic
- Tool “search_endpoints” changed its title: Search Endpoints cosmetic
- Tool “call_operation” changed its title: Call Operation cosmetic
- Tool “get_endpoint_details_full” changed its title: Get Endpoint Details cosmetic
- Tool “list_all_endpoints” changed its title: List All Endpoints cosmetic
5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 11 Aug 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 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
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 5 Nov 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 Oct 2026 | 29 Apr 2027 | RSA 2048 | SHA256-RSA | 9ca7684a3ea4b3821189e938209a2c0 |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.fiber.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| fiber.ai. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_operation 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.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | – |
| params | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_endpoint_details_full Get Endpoint Details ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| operationId | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_all_endpoints List All Endpoints ~42
List available Fiber API endpoints with optional tag/search filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | – | – | – |
| search | – | – | – |
| tagPack | – | – | – |
| tags | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_tag_packs 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | – | – | – |
| excludedTags | – | – | – |
| limit | – | – | – |
| preferredTags | – | – | – |
| query | string | yes | – |
| tagPack | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Fiber AI MCP server?
Fiber AI is a hosted endpoint at https://mcp.fiber.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.fiber.ai
claude mcp add --transport http ai-fiber-mcp 'https://mcp.fiber.ai/mcp'
What is the Fiber AI MCP server?
Fiber AI is an MCP server listed in the public MCP registry as ai.fiber/mcp. Search companies, enrich contacts, and reveal emails and phones from your AI agent. This page covers its hosted endpoint (https://mcp.fiber.ai/mcp).
Is the Fiber AI MCP server safe to use?
Fiber AI scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fiber AI MCP server expose?
Fiber AI exposes 5 tools: search_endpoints, list_tag_packs, list_all_endpoints, get_endpoint_details_full, call_operation. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the Fiber AI MCP server require authentication?
No. We connected to Fiber AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fiber AI MCP server still maintained?
Fiber AI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Fiber AI MCP server?
VerifyMCP ran 13 checks on Fiber AI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.