Web Metadata, Open Graph & JSON-LD Extractor
by industrial-platform-ai · remote · no sign-in to list tools · v1.0.4 · published by GitHub user industrial-platform-ai
Open Graph, JSON-LD, canonical, robots, headings and page metadata extractor via direct x402 MCP.
5 tools: 2 can delete or cancel things and 3 only read.
Scanned Oct 21, 2026
- Deletes or cancels2Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads3Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http web-metadata https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
5 tools
Deletes or cancels 2Claude Code: deny
abort-actor-runAbort an Actor run that is currently starting or running.No findings
Why it is in this group
- The name "abort-actor-run" says "run": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Abort Actor run
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
industrial_platform--web-metadata-intelligenceThis tool calls the Actor "industrial_platform/web-metadata-intelligence" and retrieves its output results.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "call": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: industrial_platform/web-metadata-intelligence
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: true
Only reads 3Claude Code: allow
get-actor-runGet detailed information about a specific Actor run.No findings
Why it is in this group
- The name "get-actor-run" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get Actor run
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-dataset-itemsGet items (rows) from a dataset — the output/results produced by an Actor run.No findings
Why it is in this group
- The name "get-dataset-items" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get dataset items
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get-key-value-store-recordGet the value stored under a specific key in a key-value store — a single record, not a listing of all keys.No findings
Why it is in this group
- The name "get-key-value-store-record" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get key-value store record
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 15:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- none
- RFC 9728 protected resource metadata
- https://mcp.apify.com/.well-known/oauth-protected-resource
- Authorization servers
- https://console-backend.apify.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402: tools/list returned 5 tools to an anonymous client, including industrial_platform--web-metadata-intelligence (destructive), abort-actor-run (destructive)
Install
Pinned to version 1.0.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http web-metadata https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence&payment=x402Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__web-metadata__get-actor-run",
"mcp__web-metadata__get-dataset-items",
"mcp__web-metadata__get-key-value-store-record"
],
"ask": [],
"deny": [
"mcp__web-metadata__industrial_platform--web-metadata-intelligence",
"mcp__web-metadata__abort-actor-run"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as web-metadata. Review it before you use it.
Capability tags behind 1 rule
- mcp__web-metadata__industrial_platform--web-metadata-intelligence untrusted-input
