{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"firecrawl-mcp-server","slug":"firecrawl-mcp-server","name":"Firecrawl MCP Server","type":"mcp","url":"https://github.com/mendableai/firecrawl-mcp-server","page_url":"https://unfragile.ai/firecrawl-mcp-server","categories":["mcp-servers","data-pipelines"],"tags":["firecrawl","scraping","crawling","official"],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"firecrawl-mcp-server__cap_0","uri":"capability://search.retrieval.single.page.web.content.scraping.with.markdown.conversion","name":"single-page web content scraping with markdown conversion","description":"Scrapes a single URL and converts HTML content to clean markdown using Firecrawl's content extraction pipeline. The firecrawl_scrape tool accepts a URL and optional parameters (formats, headers, wait time, screenshot capability) and returns structured markdown output with automatic cleanup of boilerplate, navigation, and ads. Implements MCP tool handler pattern that marshals arguments through the @mendable/firecrawl-js client library to Firecrawl's backend processing engine.","intents":["I need to extract clean article text from a webpage for an AI agent to analyze","I want to convert a single web page to markdown for storage in a knowledge base","I need to scrape a page and get both markdown and a screenshot for verification"],"best_for":["AI agents performing research on individual web pages","developers building content extraction pipelines","teams integrating web scraping into MCP-compatible workflows"],"limitations":["Single URL per request — batch operations require separate firecrawl_batch_scrape tool","Markdown output quality depends on page structure — poorly formatted HTML may produce suboptimal results","Screenshot generation adds latency and consumes additional credits","No built-in caching — repeated scrapes of same URL consume credits each time"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Valid HTTP(S) URL","Network connectivity to Firecrawl service","Sufficient Firecrawl credits for operation"],"input_types":["URL string","JSON object with optional parameters (formats, headers, waitFor, screenshot)"],"output_types":["Markdown text","HTML (optional)","Base64-encoded screenshot (optional)","Metadata object with success status and credit usage"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_1","uri":"capability://search.retrieval.batch.multi.url.content.scraping.with.parallel.processing","name":"batch multi-url content scraping with parallel processing","description":"Scrapes multiple URLs in a single operation using Firecrawl's batch processing pipeline. The firecrawl_batch_scrape tool accepts an array of URLs and shared options, submitting them to Firecrawl's backend which processes them in parallel and returns an array of markdown-converted content objects. Implements batching through the @mendable/firecrawl-js client's batch method, which handles request queuing, parallel execution, and result aggregation without requiring client-side coordination.","intents":["I need to scrape 10+ URLs at once for a research project without making sequential requests","I want to extract content from a list of competitor websites efficiently","I need to bulk-process URLs and get results back as a structured array"],"best_for":["bulk content extraction workflows","research teams processing multiple sources simultaneously","agents performing comparative analysis across multiple websites"],"limitations":["Batch size may be limited by Firecrawl backend (specific limit not documented in DeepWiki)","All URLs in batch share the same options — cannot customize per-URL parameters","Batch processing consumes credits for each URL regardless of success/failure","No partial failure recovery — if batch fails, must retry entire batch"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Array of valid HTTP(S) URLs","Network connectivity to Firecrawl service","Sufficient credits for all URLs in batch"],"input_types":["JSON array of URL strings","JSON object with shared options (formats, headers, waitFor, screenshot)"],"output_types":["JSON array of content objects (each with markdown, HTML optional, metadata)","Status object indicating batch completion and credit usage"],"categories":["search-retrieval","data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_10","uri":"capability://automation.workflow.docker.containerized.deployment.with.environment.configuration","name":"docker containerized deployment with environment configuration","description":"Packages the Firecrawl MCP server as a Docker container with environment-based configuration, enabling deployment to containerized infrastructure (Kubernetes, Docker Compose, cloud platforms). The Dockerfile builds a Node.js runtime with the server code and exposes configuration through environment variables, allowing operators to deploy without modifying code. Supports both cloud and self-hosted Firecrawl instances through configuration.","intents":["I need to deploy Firecrawl MCP server to Kubernetes for multi-tenant access","I want to run Firecrawl MCP server in Docker Compose alongside other services","I need to deploy to cloud platforms (AWS, GCP, Azure) with environment-based configuration"],"best_for":["teams deploying to containerized infrastructure","organizations standardizing on Docker/Kubernetes","cloud-native deployments requiring scalability"],"limitations":["Docker image size and build time not documented","No built-in health checks or readiness probes documented","Scaling requires load balancing across multiple container instances","No persistent storage — state is ephemeral per container"],"requires":["Docker runtime (Docker Desktop, Docker Engine, etc.)","Environment variables for configuration (FIRECRAWL_API_KEY, transport mode, retry settings)","Network access to Firecrawl service (cloud or self-hosted)"],"input_types":["Docker image (built from Dockerfile)","Environment variables passed at container startup"],"output_types":["Running container exposing MCP server on configured transport"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_11","uri":"capability://tool.use.integration.smithery.registry.integration.for.one.click.mcp.server.discovery","name":"smithery registry integration for one-click mcp server discovery","description":"Registers the Firecrawl MCP server in the Smithery registry, enabling one-click installation and discovery through Smithery's MCP client marketplace. The server is published to Smithery with metadata (description, tags, configuration schema) allowing users to discover and install it without manual setup. Smithery handles server distribution, version management, and client integration.","intents":["I want to install Firecrawl MCP server in Claude Desktop with one click","I need to discover available MCP servers and their capabilities","I want to manage MCP server versions and updates automatically"],"best_for":["end users installing MCP servers without technical setup","organizations standardizing on Smithery for MCP server distribution","developers discovering and evaluating MCP tools"],"limitations":["Smithery registry availability and uptime depend on Smithery service","Updates to server require re-publishing to Smithery (not automatic)","Configuration schema must be documented in Smithery metadata","No built-in version pinning — users get latest version by default"],"requires":["Smithery account and registry access","Server published to Smithery registry","Smithery-compatible MCP client (Claude Desktop, etc.)"],"input_types":["Smithery registry lookup (automatic)"],"output_types":["Server metadata and installation instructions","Installed MCP server in client"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_12","uri":"capability://tool.use.integration.self.hosted.firecrawl.instance.support.with.custom.endpoint.configuration","name":"self-hosted firecrawl instance support with custom endpoint configuration","description":"Supports connecting to self-hosted Firecrawl instances in addition to Firecrawl's cloud service through configurable API endpoint. The FIRECRAWL_API_URL environment variable allows operators to specify a custom Firecrawl endpoint, enabling deployment scenarios where Firecrawl runs on-premises or in a private cloud. The @mendable/firecrawl-js client library handles endpoint abstraction, routing all API calls to the configured endpoint.","intents":["I need to run Firecrawl on-premises for data privacy or compliance requirements","I want to use a private Firecrawl instance in my VPC","I need to deploy Firecrawl MCP server with a self-hosted Firecrawl backend"],"best_for":["organizations with data residency requirements","teams deploying to private infrastructure","deployments requiring air-gapped or offline operation"],"limitations":["Requires self-hosted Firecrawl instance — adds operational complexity","Self-hosted Firecrawl must be accessible from MCP server (network connectivity required)","No built-in failover between cloud and self-hosted instances","Self-hosted instance requires separate maintenance and updates"],"requires":["Self-hosted Firecrawl instance running and accessible","FIRECRAWL_API_URL environment variable pointing to self-hosted endpoint","Network connectivity between MCP server and self-hosted Firecrawl","API key for self-hosted instance (FIRECRAWL_API_KEY)"],"input_types":["FIRECRAWL_API_URL environment variable with custom endpoint"],"output_types":["All Firecrawl operations routed to custom endpoint"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_2","uri":"capability://search.retrieval.website.structure.discovery.and.url.mapping","name":"website structure discovery and url mapping","description":"Discovers all URLs within a website by crawling from a base URL and building a sitemap-like structure. The firecrawl_map tool accepts a base URL and optional parameters (max depth, include patterns, exclude patterns) and returns a hierarchical array of discovered URLs with metadata about page structure. Uses Firecrawl's crawler to traverse internal links up to specified depth, filtering by inclusion/exclusion patterns, and returns the complete URL graph without fetching full page content.","intents":["I need to discover all pages on a website before deciding which ones to scrape","I want to map a website's structure to understand its navigation hierarchy","I need to get a list of all URLs matching a pattern (e.g., all blog posts) without scraping content"],"best_for":["agents performing reconnaissance before targeted scraping","teams building website crawlers with selective content extraction","developers implementing search or indexing workflows"],"limitations":["Returns URLs only — does not fetch or analyze page content","Depth-based crawling may miss dynamically-generated URLs (JavaScript-rendered content)","Large websites with thousands of URLs may timeout or hit rate limits","Pattern matching uses simple string matching — no regex support documented"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Valid base URL (domain root or specific path)","Network connectivity to Firecrawl service","Target website must be publicly accessible"],"input_types":["Base URL string","JSON object with optional parameters (maxDepth, includePatterns, excludePatterns)"],"output_types":["JSON array of URL objects with metadata (URL, depth, title optional)","Status object with total URLs discovered and crawl statistics"],"categories":["search-retrieval","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_3","uri":"capability://search.retrieval.full.website.crawling.with.scheduled.content.extraction","name":"full-website crawling with scheduled content extraction","description":"Crawls an entire website and extracts content from all discovered pages in a single asynchronous operation. The firecrawl_crawl tool accepts a base URL and options (max pages, allowed domains, exclude patterns, scrape options) and returns a crawl ID for polling. The crawler discovers URLs, extracts markdown content from each page, and stores results server-side. Clients poll firecrawl_crawl_status to retrieve results as they complete, implementing an async job pattern rather than blocking until completion.","intents":["I need to extract content from an entire website (50-1000 pages) without managing individual requests","I want to build a searchable knowledge base from a company's documentation site","I need to archive a website's content with automatic markdown conversion for all pages"],"best_for":["documentation site indexing and knowledge base creation","competitive intelligence gathering across entire websites","agents performing comprehensive research on specific domains"],"limitations":["Asynchronous operation — requires polling or webhook integration to retrieve results","Max pages limit (default/configurable limit not specified in DeepWiki) prevents unlimited crawls","Large crawls consume significant credits — cost scales with page count","Results stored server-side temporarily — must retrieve before expiration","No built-in deduplication — may crawl multiple URLs pointing to same content"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Valid base URL","Network connectivity to Firecrawl service","Polling mechanism or webhook endpoint for result retrieval","Sufficient credits for estimated page count"],"input_types":["Base URL string","JSON object with crawl options (maxPages, allowedDomains, excludePatterns, scrapeOptions)"],"output_types":["Crawl ID string (for polling)","Status object with crawl progress and statistics","Array of content objects (via status polling) with markdown, metadata, source URL"],"categories":["search-retrieval","automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_4","uri":"capability://automation.workflow.crawl.status.polling.and.result.retrieval","name":"crawl status polling and result retrieval","description":"Polls the status of an in-progress or completed website crawl and retrieves extracted content. The firecrawl_crawl_status tool accepts a crawl ID and returns current progress (pages crawled, pages remaining, completion percentage), status state (running/completed/failed), and paginated results. Implements polling pattern where clients repeatedly call this tool with the same crawl ID to check progress and incrementally retrieve content as pages are processed, supporting streaming-like result consumption.","intents":["I need to check if a crawl is still running and get partial results so far","I want to retrieve results from a crawl in pages rather than waiting for everything","I need to monitor crawl progress and abort if it's taking too long"],"best_for":["agents managing long-running crawl operations","systems requiring incremental result consumption","workflows with timeout constraints on crawl duration"],"limitations":["Polling adds latency — no real-time push notifications (webhook support not documented)","Results expire after unspecified duration — must retrieve before expiration","No built-in pagination limit — large result sets may require multiple status calls","Cannot modify crawl parameters after initiation — must restart with new crawl ID"],"requires":["Valid crawl ID from prior firecrawl_crawl invocation","Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Network connectivity to Firecrawl service"],"input_types":["Crawl ID string","Optional pagination parameters (limit, offset)"],"output_types":["Status object with state (running/completed/failed), progress metrics","Array of content objects (paginated) with markdown, URL, metadata","Completion timestamp and total credit usage"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_5","uri":"capability://tool.use.integration.mcp.protocol.transport.abstraction.with.multi.mode.support","name":"mcp protocol transport abstraction with multi-mode support","description":"Abstracts communication between MCP clients and the Firecrawl server across multiple transport modes (stdio, SSE local, SSE cloud) using the @modelcontextprotocol/sdk. The server implements the MCP specification with tool definitions, argument schemas, and response marshaling, allowing any MCP-compatible client (Claude Desktop, custom agents, Smithery) to invoke Firecrawl tools without transport-specific code. Transport mode is configured via environment variables (SSE_LOCAL, SSE_CLOUD) and automatically selected at startup.","intents":["I want to use Firecrawl tools in Claude Desktop without writing custom integration code","I need to deploy Firecrawl scraping as a service accessible to multiple MCP clients","I want to switch between local and cloud deployment without changing client code"],"best_for":["developers integrating Firecrawl into MCP-compatible AI clients","teams deploying Firecrawl as a shared service for multiple agents","organizations standardizing on MCP protocol for tool integration"],"limitations":["Requires MCP-compatible client — cannot be used with non-MCP tools","stdio transport limited to single client connection at a time","SSE transport requires HTTP/HTTPS infrastructure for cloud deployment","No built-in authentication beyond Firecrawl API key — relies on transport-layer security"],"requires":["Node.js 18+ (TypeScript runtime)","@modelcontextprotocol/sdk dependency","MCP-compatible client (Claude Desktop, custom agent, etc.)","Firecrawl API key for backend authentication"],"input_types":["MCP tool call with tool name and arguments","Transport-specific request format (stdio JSON, SSE event stream)"],"output_types":["MCP tool response with result or error","Transport-specific response format"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_6","uri":"capability://automation.workflow.exponential.backoff.retry.mechanism.with.configurable.parameters","name":"exponential backoff retry mechanism with configurable parameters","description":"Implements automatic retry logic for failed Firecrawl API calls using exponential backoff with configurable parameters. The retry mechanism is configured via environment variables (FIRECRAWL_RETRY_MAX_ATTEMPTS, FIRECRAWL_RETRY_INITIAL_DELAY, FIRECRAWL_RETRY_MAX_DELAY, FIRECRAWL_RETRY_BACKOFF_FACTOR) and automatically retries transient failures (network errors, rate limits, timeouts) without client intervention. Each retry doubles the delay (or uses custom backoff factor) up to maximum delay, then gives up and returns error.","intents":["I need my scraping operations to automatically recover from temporary network failures","I want to handle Firecrawl rate limiting gracefully without failing immediately","I need to configure retry behavior for different deployment environments (dev vs production)"],"best_for":["production deployments requiring resilience to transient failures","agents performing high-volume scraping with rate limit handling","teams deploying to unreliable networks or shared infrastructure"],"limitations":["Retries only transient errors — permanent failures (invalid URL, auth error) fail immediately","Exponential backoff may cause long delays for max retries (default 3 attempts, max 10s delay = ~13s total)","No jitter randomization documented — may cause thundering herd on simultaneous retries","Retry configuration is global — cannot customize per-operation"],"requires":["Environment variables for retry configuration (optional, uses sensible defaults)","Firecrawl API key (FIRECRAWL_API_KEY environment variable)"],"input_types":["Any Firecrawl API call (automatic, no explicit input)"],"output_types":["Successful API response (after retries if needed)","Error response if all retries exhausted"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_7","uri":"capability://automation.workflow.credit.usage.monitoring.with.configurable.alert.thresholds","name":"credit usage monitoring with configurable alert thresholds","description":"Monitors Firecrawl account credit balance and emits warnings/alerts when balance falls below configurable thresholds. The monitoring is configured via environment variables (FIRECRAWL_CREDIT_WARNING_THRESHOLD, FIRECRAWL_CREDIT_CRITICAL_THRESHOLD) and checks credit balance after each operation, logging warnings to stderr when thresholds are crossed. Enables operators to detect credit exhaustion before it causes service disruption.","intents":["I need to be alerted when my Firecrawl credits are running low","I want to prevent scraping operations from failing due to insufficient credits","I need to track credit consumption across multiple deployments"],"best_for":["production deployments with cost monitoring requirements","teams managing shared Firecrawl accounts across multiple services","operators needing early warning of credit exhaustion"],"limitations":["Monitoring is passive (logging only) — does not automatically pause operations","Thresholds are global — cannot set different thresholds per operation type","Credit balance checked after operation completes — cannot prevent credit-exhausting operations","No integration with alerting systems (PagerDuty, Slack, etc.) — requires log aggregation"],"requires":["Environment variables for threshold configuration (optional, uses sensible defaults)","Firecrawl API key with credit balance accessible (FIRECRAWL_API_KEY environment variable)","Log aggregation or monitoring system to capture stderr warnings"],"input_types":["Automatic monitoring (no explicit input)"],"output_types":["Warning/critical log messages to stderr","Credit balance metadata in operation responses"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_8","uri":"capability://data.processing.analysis.structured.data.extraction.with.schema.based.parsing","name":"structured data extraction with schema-based parsing","description":"Extracts structured data from web pages using a provided JSON schema, returning parsed objects instead of raw markdown. The firecrawl_extract tool accepts a URL, a JSON schema defining desired fields, and optional parameters, and returns extracted data conforming to the schema. Uses Firecrawl's LLM-based extraction engine to identify and parse relevant content from the page, handling variations in page structure and content format automatically.","intents":["I need to extract product information (price, title, rating) from e-commerce pages","I want to parse job listings into structured records with title, company, salary, location","I need to extract contact information from business directories in a consistent format"],"best_for":["data extraction workflows requiring structured output","agents building databases from web content","teams performing web scraping for business intelligence"],"limitations":["Schema-based extraction depends on page content matching schema fields — missing fields return null","LLM-based extraction may hallucinate or misinterpret ambiguous content","Complex nested schemas may have lower accuracy than simple flat structures","Extraction consumes more credits than simple markdown scraping due to LLM processing"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Valid URL","JSON schema defining extraction structure (required)","Network connectivity to Firecrawl service"],"input_types":["URL string","JSON schema object defining fields and types","Optional parameters (prompt, headers, waitFor)"],"output_types":["JSON object conforming to provided schema","Metadata object with extraction confidence/status"],"categories":["data-processing-analysis","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__cap_9","uri":"capability://search.retrieval.search.based.web.discovery.with.relevance.ranking","name":"search-based web discovery with relevance ranking","description":"Searches the web for URLs matching a query and returns ranked results with relevance scores. The firecrawl_search tool accepts a search query and optional parameters (number of results, search type) and returns an array of URLs ranked by relevance. Integrates with web search APIs to discover relevant pages without requiring a known base URL, enabling agents to find sources for research or fact-checking.","intents":["I need to find the top 10 most relevant pages about a topic for research","I want to discover sources for fact-checking a claim","I need to find competitor websites or industry resources matching a query"],"best_for":["research agents performing open-ended web discovery","fact-checking workflows requiring source discovery","competitive intelligence gathering"],"limitations":["Search results depend on underlying search engine (Google, Bing, etc.) — results may be biased or outdated","Relevance ranking is search engine's ranking, not customizable","Search queries must be well-formed — complex queries may return irrelevant results","No filtering by content type, domain, or date range documented"],"requires":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Search query string","Network connectivity to Firecrawl service"],"input_types":["Search query string","Optional parameters (limit, searchType)"],"output_types":["JSON array of result objects with URL, title, description, relevance score"],"categories":["search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"firecrawl-mcp-server__headline","uri":"capability://data.processing.analysis.mcp.server.for.web.scraping.and.crawling","name":"mcp server for web scraping and crawling","description":"The Firecrawl MCP Server is a robust solution for web scraping and crawling, enabling AI clients to extract structured data and convert web content into clean markdown through a standardized interface.","intents":["best MCP server for web scraping","MCP server for data extraction","top tools for web crawling","MCP solutions for structured data","best practices for web scraping with AI"],"best_for":["AI-driven web scraping","data extraction from websites"],"limitations":[],"requires":[],"input_types":["URLs","scraping options"],"output_types":["Markdown","HTML","structured data"],"categories":["data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":79,"verified":false,"data_access_risk":"high","permissions":["Firecrawl API key (FIRECRAWL_API_KEY environment variable)","Valid HTTP(S) URL","Network connectivity to Firecrawl service","Sufficient Firecrawl credits for operation","Array of valid HTTP(S) URLs","Sufficient credits for all URLs in batch","Docker runtime (Docker Desktop, Docker Engine, etc.)","Environment variables for configuration (FIRECRAWL_API_KEY, transport mode, retry settings)","Network access to Firecrawl service (cloud or self-hosted)","Smithery account and registry access"],"failure_modes":["Single URL per request — batch operations require separate firecrawl_batch_scrape tool","Markdown output quality depends on page structure — poorly formatted HTML may produce suboptimal results","Screenshot generation adds latency and consumes additional credits","No built-in caching — repeated scrapes of same URL consume credits each time","Batch size may be limited by Firecrawl backend (specific limit not documented in DeepWiki)","All URLs in batch share the same options — cannot customize per-URL parameters","Batch processing consumes credits for each URL regardless of success/failure","No partial failure recovery — if batch fails, must retry entire batch","Docker image size and build time not documented","No built-in health checks or readiness probes documented","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.62,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.691Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=firecrawl-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=firecrawl-mcp-server"}},"signature":"rln8WMOtZ4MR1Of9tivZVM4sdBimUKwYiPsCoQgROeN2AOeNSbZStGr2WU+sqIEyyPwZLcviJKmF6zwPS08LAQ==","signedAt":"2026-06-23T14:23:27.565Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/firecrawl-mcp-server","artifact":"https://unfragile.ai/firecrawl-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=firecrawl-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}