x402-extract-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXTRACT_URL | No | URL of the seller endpoint | https://x402-extract-production.up.railway.app/extract |
| BUYER_PRIVATE_KEY | Yes | Your Ethereum private key for paying x402 fees |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_productA | Extract structured Product schema from any product page URL. Renders the page through a headless browser, then returns name, description, brand, price, currency, availability, and variants. Costs $0.01 USDC per call (paid automatically from the configured wallet on Base Sepolia). Use this whenever the user gives you a product URL and wants the structured fields, or when you need clean product data for shopping comparisons, price tracking, or catalog ingestion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined.
With a single tool, naming is consistent by default. The name 'extract_product' follows a clear verb_noun pattern.
A single tool for extracting product data is very thin. While the tool is focused, the server would benefit from additional tools for related operations (e.g., listing recent extractions, managing config). Count feels too low for a robust toolset.
The tool only handles extraction from a product page URL. Missing any complementary operations like validation, history, batch processing, or error handling. The surface is incomplete for a full workflow.