Web Metadata, Open Graph & JSON-LD Extractor
REMOTE · MCP.APIFY.COM
Open Graph, JSON-LD, canonical, robots, headings and page metadata extractor via direct x402 MCP.
Available components
Last scanned (11 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (industrial_platform--web-metadata-intelligence). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1918 tokens (~383/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.18.3 → 0.18.4 functional
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 455 → 387 ▲ functional
- Server version: 0.18.2 → 0.18.3 functional
- 15 Oct 26 0
- Server version: 0.18.0 → 0.18.2 functional
- 14 Oct 26 +1
- Server version: 0.17.4 → 0.18.0 functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Server version: 0.17.3 → 0.17.4 functional
- 8 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 27. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.apify.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 3 Jul 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 33947021329345fc779537cd9a338fd |
| SANs: *.apify.com, apifier.com, *.apifier.com, apify.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.apify.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| apify.com. | present | 54503 | 13 | Verified |
| mcp.apify.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402 | Verified | 200 | |
| http (plaintext) | http://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402 | HTTPS enforced | 301 | https://mcp.apify.com:443/?tools=industrial_platform/web-metadata-intelligence&payment=x402 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
abort-actor-run Abort Actor run ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gracefully | boolean | – | If true, the Actor run will abort gracefully with a 30-second timeout. |
| runId | string | yes | The ID of the Actor run to abort. |
Structured output declared, but exposes no named fields.
No examples provided.
get-actor-run Get Actor run ~306
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.
| Name | Type | Req | Description |
|---|---|---|---|
| runId | string | yes | The ID of the Actor run. |
| waitSecs | integer | – | Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30. |
Structured output declared, but exposes no named fields.
No examples provided.
get-dataset-items Get dataset items ~406
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clean | boolean | – | If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true. |
| datasetId | string | yes | Dataset ID or username~dataset-name. |
| desc | boolean | – | If true, results are returned in reverse order (newest to oldest). |
| fields | string | – | Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes. |
| flatten | string | – | Comma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify onl… |
| limit | integer | – | Maximum number of items to return. Default is 20. |
| offset | number | – | Number of items to skip at the start. Default is 0. |
| omit | string | – | Comma-separated list of fields to exclude from results. |
Structured output declared, but exposes no named fields.
No examples provided.
get-key-value-store-record Get key-value store record ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyValueStoreId | string | yes | Key-value store ID or username~store-name. |
| recordKey | string | yes | Key of the record to retrieve. |
Structured output declared, but exposes no named fields.
No examples provided.
industrial_platform--web-metadata-intelligence industrial_platform/web-metadata-intelligence ~264
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.
| Name | Type | Req | Description |
|---|---|---|---|
| concurrency | integer | – | Maximum number of URLs fetched concurrently during this run. Example values: 10 |
| timeout_seconds | integer | – | Maximum time allowed for each individual page fetch. Example values: 30 |
| urls | array | yes | **REQUIRED** Public HTTP/HTTPS pages to inspect. Up to 100 unique URLs per run. Example values: ["https://example.com/"] |
| waitSecs | integer | – | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to pol… |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Web Metadata, Open Graph & JSON-LD Extractor MCP server?
Web Metadata, Open Graph & JSON-LD Extractor is a hosted endpoint at https://mcp.apify.com/?tools=industrial_platform/web-metadata-intelligence&payment=x402, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.apify.com
claude mcp add --transport http industrial-platform-ai-web-metadata 'https://mcp.apify.com/?tools=industrial_platform/web-metadata-intelligence&payment=x402'
What is the Web Metadata, Open Graph & JSON-LD Extractor MCP server?
Web Metadata, Open Graph & JSON-LD Extractor is an MCP server listed in the public MCP registry as io.github.industrial-platform-ai/web-metadata. Open Graph, JSON-LD, canonical, robots, headings and page metadata extractor via direct x402 MCP. This page covers its hosted endpoint (https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402).
Is the Web Metadata, Open Graph & JSON-LD Extractor MCP server safe to use?
Web Metadata, Open Graph & JSON-LD Extractor scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Web Metadata, Open Graph & JSON-LD Extractor MCP server expose?
Web Metadata, Open Graph & JSON-LD Extractor exposes 5 tools: industrial_platform--web-metadata-intelligence, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run. Their descriptions and schemas cost roughly 1,358 tokens of context every time the server is loaded.
Does the Web Metadata, Open Graph & JSON-LD Extractor MCP server require authentication?
No. We connected to Web Metadata, Open Graph & JSON-LD Extractor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Web Metadata, Open Graph & JSON-LD Extractor MCP server still maintained?
Web Metadata, Open Graph & JSON-LD Extractor is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.