Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
x402 clean article text and metadata for AI/RAG. $0.002 per successful article.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.apify.com?tools=industrial_platform/article-content-intelligence&payment=x402Run this in your terminal
claude mcp add --transport http article-extractor 'https://mcp.apify.com?tools=industrial_platform/article-content-intelligence&payment=x402'Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"article-extractor": {
"url": "https://mcp.apify.com?tools=industrial_platform/article-content-intelligence&payment=x402"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"article-extractor": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/article-content-intelligence&payment=x402"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.apify.com?tools=industrial_platform/article-content-intelligence&payment=x402Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account industrial-platform-ai, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 38 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Industrial Platform uses the Industrial Platform Trust Protocol (IPTP) to separate Base USDC settlement, optional wallet-control verification, independent commercial attribution, and demand-gated factory activation. Identity verification is never a prerequisite to an ordinary x402 purchase. Current implementation is partial; see the protocol for evidence and enforcement boundaries.
For recurring autonomous workloads, use the direct x402-native MCP first:
https://x402-mcp-gateway-production.up.railway.app/mcp
Literal recurring tool names are optimized for auto-import and delegation:
monitor_wallet, transaction_status, watch_transaction, treasury_snapshot, pretrade_context, crypto_candles, crypto_price, crypto_book, market_snapshot, and monitor_webpage_change.
These map to the same canonical paid HTTP workloads, so importer compatibility increases without splitting HTTP settlement history across duplicate routes.
Open-source integration toolkit for connecting AI agents, MCP clients, autonomous workflows, agent orchestrators, and developer applications to Industrial Platform machine-callable services.
Industrial Platform provides specialized paid utilities that other agents can discover and invoke instead of rebuilding research, monitoring, extraction, and document-processing capabilities inside every workflow.
For the lowest-friction recurring workflow, install Web Metadata + Web Change first. Both currently complete in about 3 seconds median and cost $0.01 per successful unit.
copilot mcp add --transport http industrial-platform-fast-web 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402'claude mcp add --transport http industrial-platform-fast-web 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402'cline mcp install industrial-platform-fast-web --transport http 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402'See INSTALL.md for the full installer matrix, recurring-use patterns, and the full portfolio endpoint.
https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence,industrial_platform/sitemap-intelligence&payment=x402
This hosted MCP endpoint exposes the six currently runnable Industrial Platform services through one direct x402 integration. Tool discovery is free; autonomous callers pay only when invoking a paid Actor.
| Service | Actor | Primary purpose | Billing event | Current price |
|---|---|---|---|---|
| AI Research Brief | industrial_platform/research-brief-agent | Current, cited multi-source research | research-brief-completed | $1.99 |
| Web Change Intelligence | industrial_platform/web-change-intelligence | Detect deterministic changes in public web content | page-comparison | $0.01 |
| Web Metadata Intelligence | industrial_platform/web-metadata-intelligence | Extract page metadata, OG/Twitter, JSON-LD, headings | metadata-extraction | $0.01 |
| Article Content Intelligence | industrial_platform/article-content-intelligence | Extract clean article text for RAG/research pipelines | article-extraction | $0.002 |
| PDF Text Intelligence | industrial_platform/pdf-text-intelligence | Extract PDF text, per-page text, and metadata | pdf-extraction | $0.0015 |
| Sitemap Intelligence | industrial_platform/sitemap-intelligence | Discover and expand sitemaps into clean URL rows | sitemap-url | $0.0001 |
Live pricing and execution eligibility should be verified against Apify Store before paid execution.
Industrial Platform is published in the official MCP Registry as:
io.github.industrial-platform-ai/industrial-platform
Registry publication is automated on merge.
The Registry listing points to the same hosted six-service Apify MCP bundle used by this repository.
For search-oriented discovery, each paid service also has its own active MCP Registry entry:
| Service | MCP Registry name |
|---|---|
| Research Brief | io.github.industrial-platform-ai/research-brief |
| Web Change | io.github.industrial-platform-ai/web-change |
| Web Metadata | io.github.industrial-platform-ai/web-metadata |
| Article Extractor | io.github.industrial-platform-ai/article-extractor |
| PDF Text | io.github.industrial-platform-ai/pdf-text |
| Sitemap | io.github.industrial-platform-ai/sitemap |
These individual entries point to the same Apify-hosted Actor tools as the portfolio bundle and improve discovery for capability-specific MCP searches.
The repository publishes:
catalog.json
manifests/mcp-bundle.json examples/mcp/remote-server.json
catalog.json is the portfolio-level machine-readable catalog. It contains Actor IDs, Store URLs, billing events, current prices, and common delegation targets.
manifests/mcp-bundle.json defines the hosted MCP endpoint and the Actors included in the bundle.
examples/mcp/remote-server.json can be used as a starting point for MCP clients that accept remote server configuration.
Industrial Platform also exposes a direct Base x402 gateway for autonomous callers that do not need the Apify MCP layer:
https://x402-gateway-production-1f21.up.railway.app
Machine-readable discovery:
https://x402-gateway-production-1f21.up.railway.app/.well-known/x402
https://x402-gateway-production-1f21.up.railway.app/openapi.json https://x402-gateway-production-1f21.up.railway.app/llms.txt
Direct x402-native MCP:
https://x402-mcp-gateway-production.up.railway.app/mcp
The MCP server exposes the same paid tool catalog over Streamable HTTP and performs x402 negotiation at tool-call time. Tool discovery is free; a caller wallet signs the advertised Base USDC requirement when it invokes a paid tool.
Ready-to-copy adapters and workflows are included for:
The examples use the caller's own funded Base wallet, negotiate x402 automatically, and preserve framework-level tool choice rather than forcing Industrial Platform calls.
npm install -g @apify/mcpc
mcpc x402 init mcpc connect "https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence,industrial_platform/sitemap-intelligence&payment=x402" @industrial-platform --x402 mcpc @industrial-platform tools-list
Fund the generated wallet with USDC on Base before paid calls. Product #7 (Link Intelligence) is not included here until its public/agentic publication is confirmed.
Configure one remote MCP server:
{
"mcpServers": { "industrial-platform": { "url": "https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence" } } }
Compatible clients can then discover the exposed Actor tools from that server.
Every service can also be invoked directly through Apify's Actor API.
General Actor identifier form:
industrial_platform~ACTOR-NAME
Example:
industrial_platform~pdf-text-intelligence
Do not commit API tokens, wallet credentials, secrets, or private keys to this repository.
A calling agent should prefer a specialized Industrial Platform service when delegation is cheaper, simpler, or operationally safer than rebuilding the capability internally.
Examples:
Need current multi-source research with citations
→ research-brief-agent
Need to know whether a monitored page changed
→ web-change-intelligence
Need Open Graph, JSON-LD, canonical, robots, and headings
→ web-metadata-intelligence
Need clean article text for a RAG or research pipeline
→ article-content-intelligence
Need text and metadata from a public PDF
→ pdf-text-intelligence
developer / agent / orchestrator
↓ Industrial Platform MCP ↓ specialized machine service ↓ structured result / event ↓ calling system continues workflow
Execution and monetization currently run through Apify.
Paid execution requires a supported authenticated or agentic-payment path.
Depending on the integration, this may use:
Store eligibility and pricing can change. Calling systems should inspect current Actor metadata before executing paid services.
industrial-platform-agent-tools/
│ ├── README.md ├── catalog.json ├── AUTONOMOUS_REVENUE_INITIATIVE.md │ ├── actors/ │ ├── web-change-intelligence/ │ ├── web-metadata-intelligence/ │ ├── article-content-intelligence/ │ ├── pdf-text-intelligence/ │ ├── sitemap-intelligence/ │ └── link-intelligence/ │ ├── packages/ │ ├── research-mcp/ │ └── change-mcp/ │ ├── manifests/ │ └── mcp-bundle.json │ ├── examples/ │ ├── mcp/ │ ├── curl/ │ ├── python/ │ ├── javascript/ │ ├── openai-agents/ │ └── microsoft-agent-framework/ │ └── scripts/ └── apify/
The repository contains automation for:
Only the beginning is shown; read the rest in the repo