Fiber AI
REMOTE · MCP.FIBER.AI · 2 COMPONENTS · SCANNED SEP 20
Search companies, enrich contacts, and reveal emails and phones from your AI agent.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Fiber AI MCP server?
Fiber AI is a hosted endpoint at https://mcp.fiber.ai/mcp/v2/, 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/v2/'
{
"mcpServers": {
"ai-fiber-mcp": {
"url": "https://mcp.fiber.ai/mcp/v2/"
}
}
} {
"servers": {
"ai-fiber-mcp": {
"type": "http",
"url": "https://mcp.fiber.ai/mcp/v2/"
}
}
} [mcp_servers.ai-fiber-mcp] url = "https://mcp.fiber.ai/mcp/v2/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-fiber-mcp": {
"type": "remote",
"url": "https://mcp.fiber.ai/mcp/v2/",
"enabled": true
}
}
} openclaw mcp add ai-fiber-mcp --url 'https://mcp.fiber.ai/mcp/v2/' --transport streamable-http
mcp_servers:
ai-fiber-mcp:
url: "https://mcp.fiber.ai/mcp/v2/" {
"McpServers": {
"ai-fiber-mcp": {
"Transport": "http",
"Url": "https://mcp.fiber.ai/mcp/v2/"
}
}
} assistant mcp add ai-fiber-mcp -t streamable-http -u 'https://mcp.fiber.ai/mcp/v2/'
{
"mcpServers": {
"ai-fiber-mcp": {
"type": "http",
"url": "https://mcp.fiber.ai/mcp/v2/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 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
- 5 Aug 26 0
- DNSSEC: unverified → fail ▼ security
- HSTS header: unverified → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Transport: Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. security
- 4 Aug 26 0
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 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
- 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 0
First indexed and scored.
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 20 Sept 2026 · Probed https://mcp.fiber.ai/mcp/v2/
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 |
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. | 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 | 307 |
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/v2/ | Redirected | 307 | http://mcp.fiber.ai/mcp/v2 |
| http (plaintext) | http://mcp.fiber.ai/mcp/v2/ | HTTPS enforced | 301 | https://mcp.fiber.ai/mcp/v2/ |
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 →
No tool schema has been captured from this endpoint yet.
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/v2/).
Is the Fiber AI MCP server safe to use?
Fiber AI scores 23 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.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.