Link Extractor for AI Agents MCP Server

by industrial-platform-ai Your server? Claim it

answering

Link Extractor for AI Agents is answering right now. Last checked 12 min ago. It exposes 5 tools. Last commit 8 Oct 2026.

x402 structured link extraction for agents. $0.0005 per successfully processed page.

Uptime history 12 days of history

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

478 ms

Response time

average over 24h

Stars

last commit 8 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

8 Oct a tool changed version

7 Oct a tool changed version

5 Oct a tool changed version

1 Oct a tool changed version

What the code does

We read the source, 3 d ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command buyer/zeroxwork-acquisition.mjs:5, integrations/agentkit-industrial-platform/install.mjs:118

    const child=spawn(command,args,{env:{...process.env,...env},stdio:['ignore','pipe','pipe']});

Image runs as root industrial-sentinel-runtime/Dockerfile:15

USER root

Long encoded blob in source observability/native-fast-x402.json:8, observability/production-gateway-activation.json:321

      "paymentRequiredRaw": "eyJ4NDAyVmVyc2lvbiI6MiwiZXJyb3IiOiJQQVlNRU5ULVNJR05BVFVSRSBoZWFkZXIgaXMgcmVxdWlyZWQuIiwicmVzb3VyY2UiOnsiZGVzY3JpcHRpb24iOiJBcGlmeSBTdG9yZSBpcyB0aGUgbGFyZ2VzdCBtYXJrZXRwbGFjZSBvZiB0b29scyBmb3IgQUkgYWdlbnRzLiBFeHRyYWN0IGRhdGEgZnJvbSBhbnkgd2Vic2l0ZSBhbmQ…

In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

Builds a database query by concatenation .github/workflows/optimize-agent-routing-metadata.yml:17, .github/workflows/optimize-store-discovery.yml:17, .github/workflows/optimize-top-three-conversion.yml:17 и ещё 1

      - name: Update machine-facing Actor metadata
        env:
          APIFY_TOKEN: ${{ secrets.APIFY_TOKEN }}

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add link-extractor --transport http https://mcp.apify.com?tools=industrial_platform/link-intelligence&payment=x402

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "link-extractor": {
      "url": "https://mcp.apify.com?tools=industrial_platform/link-intelligence\u0026payment=x402"
    }
  }
}

~/.codex/config.toml

[mcp_servers.link-extractor]
url = "https://mcp.apify.com?tools=industrial_platform/link-intelligence&payment=x402"

.cursor/mcp.json

{
  "mcpServers": {
    "link-extractor": {
      "url": "https://mcp.apify.com?tools=industrial_platform/link-intelligence\u0026payment=x402"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "link-extractor": {
      "url": "https://mcp.apify.com?tools=industrial_platform/link-intelligence\u0026payment=x402"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

abort

abort-actor-run

Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request. USAGE: - Use when you need to stop a run that is taking too long or misconfigured. USAGE EXAMPLES: - user_input: Abort run y2h7sK3Wc - user_input: Gracefully abort run y2h7sK3Wc This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

actor

get-actor-run

Get detailed information about a specific Actor run. Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep. - summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available."). - nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=..."). - waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning. USAGE: - Use to check the status of a run started by any Actor-running tool. - Pass waitSecs > 0 to block until terminal (or until the cap elapses). USAGE EXAMPLES: - user_input: Show details of run y2h7sK3Wc - user_input: Wait for run y2h7sK3Wc to finish This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

dataset

get-dataset-items

Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields. USAGE: - Use when you need to read data from a dataset (all items or only selected fields). USAGE EXAMPLES: - user_input: Retrieve results from dataset abc123 - user_input: Get only metadata.url and title from dataset username~my-dataset This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

industrial

industrial_platform--link-intelligence

This tool calls the Actor "industrial_platform/link-intelligence" and retrieves its output results. Actor description: Extract links, anchors, rel flags and link class. Price: $0.0005 per successful page. This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

key

get-key-value-store-record

Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. USAGE: - Use when you need to retrieve a specific record (JSON, text, or binary) from a store. USAGE EXAMPLES: - user_input: Get record INPUT from store abc123 - user_input: Get record data.json from store username~my-store This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com?tools=industrial_platform/link-intelligence&payment=x402	streamable-http	answering	314 ms	12 min ago

Alternatives to Link Extractor for AI Agents

same job, measured the same way

PDF Text Extractor for AI Agents

by industrial-platform-ai

x402 PDF text, pages, and metadata for AI/RAG. $0.0015 per successful PDF.

5 tools answering

Article Content Extractor for AI Agents

by industrial-platform-ai

x402 clean article text and metadata for AI/RAG. $0.002 per successful article.

5 tools answering

Sitemap URL Extractor for AI Agents

by industrial-platform-ai

x402 sitemap discovery and URL extraction for agents. $0.0001 per emitted URL.

5 tools answering

MCP Browser Research

by infoinlet-marketplace

Web browsing & research for AI agents — fetch/read pages, structured extraction, Exa search.

39 installs/wk local only

Trace Forge

by mdfifty50-boop

Structured execution trace and span logging for AI agents

33 installs/wk local only

срезAI — Search API for AI agents

by srezai

Web search, page reading and structured extraction for AI agents, with strong RU coverage

12 tools answering

Agentrender MCP

by corbinvachal48

URL to screenshot, PDF, or structured extract for AI agents via MCP.

93 installs/wk local only

Gildara

by gildara

Operating contracts for AI agents. Structured instructions compiled into system prompts.

local only

Link Extractor for AI Agents — questions

Answers built from our own checks of this server.

What can Link Extractor for AI Agents do?

It exposes 5 tools, read directly from the server on our last check. Among them: abort-actor-run, get-actor-run, get-dataset-items, get-key-value-store-record, industrial_platform--link-intelligence. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Link Extractor for AI Agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 478 ms. The bar chart above shows every period we have measured.

How do I connect Link Extractor for AI Agents?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Link Extractor for AI Agents need an API key?

No. Link Extractor for AI Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Link Extractor for AI Agents?

It answers our handshake in 478 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Link Extractor for AI Agents open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 8 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.