# Scrapfly Codex MCP Evaluation

**Category:** Webscraping
**Score:** 76 (B)

This is the agent-readable Devtool Arena evaluation page for Scrapfly on Codex MCP.

## Summary

| Metric | Value |
|--------|-------|
| Status | completed |
| Overall score | 76 |
| Grade | B |
| Eval score | 89 |
| Discovery score | 45 |
| Cost | $0.11 |
| Runtime | 2m 42s |
| Tool calls | 2 |
| Errors | 0 |
| Tokens used | 333182 |
| Success | Yes |

## Agent-Readiness Checklist

| Signal | Evidence |
|--------|----------|
| Context7 | Not found |
| llms.txt | Not found |
| MCP server | Not found |
| Typed SDK | Not found |
| OpenAPI | Not found |
| Agent skills | Not found |
| CLI | Not found |

## Evaluation Prompt

````text

# Task
Using the Scrapfly MCP, scrape web content:

1. Discover available MCP tools and their capabilities
2. Scrape the page at "https://news.ycombinator.com"
3. Extract the top 5 story titles and their URLs
4. Print the results as JSON

Use ONLY the MCP tools for all operations.

You MUST use the Scrapfly MCP server to accomplish this task.
Use the MCP tools for the actual product operations. Do NOT use curl, fetch, raw HTTP requests, CLI commands, or SDK calls as substitutes.

Use the MCP tools' help/descriptions to understand what each tool does.
If you need additional context, check the documentation: https://github.com/scrapfly/scrapfly-mcp

## Setup
Do NOT assume the Scrapfly MCP server is already installed or already running in this sandbox.
Review the installation and authentication details below before starting the task.

### Installation
Transport: `http`
This MCP server uses `http` transport.
Codex should connect to: `https://mcp.scrapfly.io/mcp`
Do not assume a local MCP package is already installed; the task depends on the remote server being reachable.
Bootstrap notes: Scrapfly documents this hosted MCP endpoint and accepts the API key as an Authorization: Bearer token. Official OpenAI documentation confirms Codex supports bearer_token_env_var for HTTP MCP servers. No local installation or long-running launch command is needed.

### Authentication
The following environment variables are already set in this environment: `SCRAPFLY_API_KEY`
The MCP server should read them automatically when it starts.

## Execution
1. The harness has already written the launch configuration for `scrapfly`. Start with the task directly; do not rewrite agent settings, `.mcp-runtime.json`, or build a separate MCP client unless the connected server still fails after a normal retry.
2. You do not need to enumerate every MCP tool up front; inspect only the relevant tools you need. Agent-facing MCP tool names may be namespaced like `mcp__scrapfly__<tool_name>`.
3. Complete the task described above using MCP tools for the actual product operations.
4. If the server fails to start or authenticate, debug the documented setup and retry. Do not fall back to raw HTTP, SDK, CLI, or manual JSON-RPC/MCP calls as a substitute for exposed MCP tools.

Work in the /home/daytona/app directory.
If you use Bash during setup or debugging, limit it to installation/configuration work and then return to MCP tools for the task itself.
If there are errors, debug and fix them until the task runs successfully.

## Summary
When you are done, write a JSON summary file to /home/daytona/app/results.json with this structure:
{
  "operations": [
    {"step": 1, "description": "What you did", "mcp_tool": "tool_name", "success": true/false, "output_summary": "brief result"},
    ...
  ],
  "overall_success": true/false,
  "notes": ["any relevant notes about the execution"]
}

````

## Grader Results

| Check | Passed | Weight | Score | Details |
|-------|--------|--------|-------|---------|
| Task | Yes | — | — | — |
| Llms Txt | No | — | 0 | — |
| Tool Count | Yes | — | 10 | — |
| Auth Method | Yes | — | 15 | — |
| Official Mcp | Yes | — | 5 | — |
| Output Schema | No | — | 0 | — |
| Tool Stability | Yes | — | 5 | — |
| Tool Description Length | Yes | — | 10 | — |

## Run Artifacts

| Artifact | Value |
|----------|-------|
| Conversation turns | 5 |
| Tool call traces | 2 |
| Generated files | 1 |
| Exit code | — |
| Completed at | 2026-09-27T14:44:07.586695+00:00 |

### Generated Files

- /home/daytona/app/results.json

## Related Pages

- [Codex MCP leaderboard](/leaderboard/codex/mcp)
- [Compare Codex MCP companies](/leaderboard/codex/mcp/compare)
- [Agent Landscape](/leaderboard/discoverability)

Canonical URL: https://devtoolarena.com/codex/mcp/scrapfly
