Search companies, enrich contacts, and reveal emails and phones from your AI agent.
The Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI agent to access Fiber AI's data and tools — search companies, enrich contacts, reveal emails, and more — directly from your editor. If you are a coding agent and need to pick between MCP and the REST API, start with the canonical agent-facing docs on the API: Routing index + critical rules:…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
The Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI agent to access Fiber AI's data and tools — search companies, enrich contacts, reveal emails, and more — directly from your editor. If you are a coding agent and need to pick between MCP and the REST API, start with the canonical agent-facing docs on the API: Routing index + critical rules: Per-operation markdown: MCP walkthrough for LLMs: Rule of thumb: use MCP when you're acting inside an…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.