Web Metadata, Open Graph & JSON-LD Extractor MCP server

• abort-actor-runwrite actionFree

  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.

• get-actor-runwrite actionFree

  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.

• get-dataset-itemsFree

  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.

• get-key-value-store-recordFree

  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.

• industrial_platform--web-metadata-intelligenceFree

  This tool calls the Actor "industrial_platform/web-metadata-intelligence" and retrieves its output results. Actor description: Use for Open Graph, JSON-LD, canonical, robots, headings, language, and page metadata. Input: urls[]. $0.001 per successful URL; failed URLs are not billed. 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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 862ms20/20
• Tool poisoning5 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

5

the typical server has 7

Tools that change things

40%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

186 ms

faster than 66% of 30,031 servers

Web Metadata, Open Graph & JSON-LD Extractor: common questions

Is Web Metadata, Open Graph & JSON-LD Extractor MCP server safe?

Mostly: it is graded B (80/100). Read the Web Metadata, Open Graph & JSON-LD Extractor safety report

How do I install Web Metadata, Open Graph & JSON-LD Extractor?

It runs remotely at mcp.apify.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Web Metadata, Open Graph & JSON-LD Extractor need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Web Metadata, Open Graph & JSON-LD Extractor maintained?

The last commit was 34 days ago (2026-09-30). The latest release is v1.0.4.

Is Web Metadata, Open Graph & JSON-LD Extractor up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Web Metadata, Open Graph & JSON-LD Extractor?

Servers from other publishers that do the same job: Front-End Checklist MCP server.

How does Web Metadata, Open Graph & JSON-LD Extractor compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.