Skip to main content
Glama
terradeed

TerraDeed MCP Server

Official
by terradeed
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

TerraDeed MCP Server

x402-powered web scraping and structured data extraction for AI agents.

Overview

This MCP server connects your AI agent to the TerraDeed Scrape API, enabling:

  • Web scraping — Clean, LLM-ready markdown from any URL ($0.01 USDC)

  • Structured extraction — Schema-driven JSON data from any page ($0.05 USDC)

  • Wallet balance checks — Free USDC balance lookups on Base mainnet

Payments are handled transparently via the x402 protocol on Base mainnet using USDC.

Related MCP server: SchemaFetch MCP Server

Installation

Via npx (recommended)

TERRADEED_PRIVATE_KEY=0x... npx terradeed-mcp-server

Global install

npm install -g terradeed-mcp-server
TERRADEED_PRIVATE_KEY=0x... terradeed-mcp-server

Environment Variables

Variable

Required

Description

TERRADEED_PRIVATE_KEY

Yes

Ethereum private key for signing x402 payments. Must hold USDC on Base mainnet.

Tools

terradeed_scrape_url

Scrape any public URL and return clean markdown.

Cost: $0.01 USDC per call

{
  "url": "https://example.com",
  "render_js": false
}

terradeed_extract_structured

Extract structured JSON data using a schema.

Cost: $0.05 USDC per call

{
  "url": "https://example.com",
  "schema": {
    "type": "object",
    "properties": {
      "title": { "type": "string" },
      "price": { "type": "number" }
    }
  },
  "instructions": "Extract the product title and price"
}

terradeed_check_wallet

Check USDC balance on Base mainnet. Free.

{
  "address": "0x..."
}

Configuration

Add to your MCP client config (e.g., Claude Desktop, Cursor):

{
  "mcpServers": {
    "terradeed": {
      "command": "npx",
      "args": ["terradeed-mcp-server"],
      "env": {
        "TERRADEED_PRIVATE_KEY": "your-private-key"
      }
    }
  }
}

Links

License

MIT

Available Tools

3 tools
terradeed_check_walletA

Check the USDC balance of a wallet on Base mainnet. Free — no x402 payment required.

ParametersJSON Schema
NameRequiredDescriptionDefault
addressNoEthereum address to check (defaults to the payment wallet)

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description must carry the burden of behavioral disclosure. It adds key context by specifying that the tool is free (no x402 payment required) and operates on Base mainnet. It does not explain error handling or return format, but for a simple read-only balance check, this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that front-loads the core purpose and includes only essential additional context (free, network). Every word contributes to understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple: one optional parameter, no output schema, no annotations. The description provides sufficient information to know what the tool does, under what conditions (free, Base mainnet), and implies the output is the balance. This is complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides a complete description for the address parameter (including default behavior), achieving 100% coverage. The description adds no additional parameter-level information, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks the USDC balance of a wallet on Base mainnet, using a specific verb and resource. It also distinguishes itself from sibling tools by focusing on wallet balance rather than URL scraping or structured extraction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its usage by explaining it checks wallet balance and is free, but it does not explicitly state when to use it over alternatives. The sibling tools are clearly for different purposes, so the intended use is inferred rather than explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

terradeed_extract_structuredA

Extract structured JSON data from any URL using a provided schema. Cost: $0.05 USDC per call. The schema defines exactly what fields to extract.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to extract data from
schemaYesJSONSchema object defining the output shape
instructionsNoOptional plain-language instructions for the extraction

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses the cost of $0.05 per call, which is a behavioral trait beyond the schema. However, it does not mention read-only nature, failure behavior, rate limits, or any side effects. Without annotations, this is only partial transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences, each providing useful information (purpose, cost, schema behavior). No extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is adequate for a simple extraction tool without an output schema, but it omits details like the optional instructions parameter, what happens on failure, and any URL limitations. Given no annotations, more context would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for all three parameters, so the baseline is 3. The description adds minimal meaning beyond the schema: it reinforces that the schema defines the output fields, but this is largely redundant with the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool extracts structured JSON data from a URL using a provided schema, which is a specific verb+resource. It distinguishes from siblings like terradeed_scrape_url by emphasizing structured extraction with a schema rather than a general scrape.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for structured extraction but does not explicitly compare to alternatives like terradeed_scrape_url or state when to use one over the other. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

terradeed_scrape_urlA

Scrape any public URL and return clean, LLM-ready markdown. Cost: $0.01 USDC per call. Supports JavaScript-rendered pages.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to scrape
render_jsNoRender JavaScript before scraping (slower, more complete)

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must convey behavioral traits. It adds the cost per call ($0.01 USDC) and JS rendering support, which are valuable. However, it omits details like rate limits, error behavior, or authentication requirements, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences covering purpose, cost, and capability. It is front-loaded with the primary function and contains no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple scraping tool with no output schema and no annotations, the description provides enough information to understand the main task and return format. It lacks explicit guidance on alternatives and edge cases, but the core function is well covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes both parameters with full coverage (100%), so the baseline is 3. The description confirms that URLs must be public and mentions JS rendering, but it does not add significant new meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Scrape' and the resource 'any public URL,' with the output 'clean, LLM-ready markdown.' This distinguishes it from siblings like terradeed_extract_structured (structured extraction) and terradeed_check_wallet (wallet check).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives context that it scrapes public URLs and supports JS rendering but does not explicitly state when to prefer this tool over siblings or any exclusions. Usage is implied rather than explicit, so it falls short of full guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv0.1.4
    • First observedterradeed_check_wallet
    • First observedterradeed_extract_structured
    • First observedterradeed_scrape_url
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

Each tool serves a clearly distinct purpose: scraping to markdown, extracting structured JSON, and checking wallet balance. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tools follow the consistent 'terradeed_verb_noun' pattern (scrape_url, extract_structured, check_wallet). The naming is uniform and predictable.

Tool Count5/5

With 3 tools, the server is tightly scoped to its core functions of scraping and extraction. Each tool earns its place, and the count is neither too thin nor too heavy.

Completeness4/5

The core workflow of scraping and structured extraction is well-covered. The only minor gap is the lack of schema management or a listing of predefined schemas, but this is not a critical omission.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/terradeed/terradeed-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server