smart-data-extractor
Server Details
smart-data-extractor MCP server on Cloudflare Workers · REST + MCP JSON-RPC · free tier
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- lazymac2x/smart-data-extractor-worker
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.9/5 across 4 of 4 tools scored.
Each tool has a clear, distinct purpose: auto_schema_learn for schema inference, batch_extract for multi-source extraction, extract_from_api for API responses, and extract_from_url for URLs. No two tools overlap in their primary function.
Tool names use snake_case but with inconsistent patterns: 'auto_schema_learn' is adjective_noun_verb, while 'batch_extract' is noun_verb, and 'extract_from_api'/'extract_from_url' are verb_preposition_noun. This mismatch could confuse an agent.
Four tools is on the low side for a data extraction server, covering basic sources but lacking something like direct file extraction. The count is reasonable for a minimal server but feels slightly incomplete.
Covers schema learning and extraction from URLs, APIs, and batch sources, but missing extraction from local files, databases, or direct text input. No schema management or listing tools exist, leaving notable gaps.
Available Tools
4 toolsauto_schema_learnInspect
Idempotent · 30s timeout · Automatically infer JSON Schema from sample data without extraction. Pass idempotency_key to deduplicate within 5 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| sample_data | Yes | Representative sample data as JSON string (array of objects or single object). Schema is inferred from structure; use first 1-10 rows for array samples. Max 200KB. | |
| idempotency_key | No | Optional cache key (UUID/string) for 5-minute deduplication. Repeat calls with same key return cached inferred schema instantly. |
batch_extractInspect
Idempotent · 30s timeout · Extract data from multiple sources (JSON/JSONL/text) with a single consistent schema. Pass idempotency_key to deduplicate within 5 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| schema | No | Optional target JSON Schema (draft-07) applied to all sources. If omitted, inferred from first source and reused across remaining sources. Enables consistent field extraction from diverse formats. | |
| sources | Yes | Array of 1-100 data sources to extract from. Each source includes type (format) and content (raw data). | |
| idempotency_key | No | Optional deduplication key (UUID/string) for 5-minute cache. Identical batch calls (same sources + schema + key) return cached results instantly. |
extract_from_apiInspect
Idempotent · 30s timeout · Extract structured data from API response JSON with schema adaptation. Pass idempotency_key to deduplicate within 5 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| schema | No | Optional target JSON Schema (draft-07) for field extraction. If omitted, inferred from content structure. Enforces consistent field extraction across multiple API responses. | |
| content | Yes | API response body as raw JSON string (max 200KB). Can be single object, array of objects, or array of primitives. Automatically parsed and validated. | |
| idempotency_key | No | Optional deduplication key (UUID or unique string) for 5-minute cache. Identical calls return cached result instantly. |
extract_from_urlInspect
Idempotent · 30s timeout · Extract structured data from URL content with auto schema learning. Pass idempotency_key to deduplicate identical calls within 5 minutes.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | HTTP(S) URL to fetch (will auto-download and parse), or raw content string (up to 200KB). Max 200KB after fetch. | |
| schema | No | Optional pre-defined JSON Schema (draft-07). If omitted, schema is auto-inferred from content. Provide to enforce strict field extraction and type coercion. | |
| idempotency_key | No | Optional UUID or unique identifier for 5-minute deduplication cache. Same key + tool = cached result in <5ms, zero re-fetching. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!