serp-extract-mcp

by io.github.robertoyanguas-ops

Overview Discussions Admin

Server Details

Executes live web/news search queries and returns clean, token-pruned results with zero ad bloat.

Ownership verified

Status: Healthy
Uptime: 100.0% over 15 days
Last Tested: 2026-11-02 13:55
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.3/5.0

Scored 2026-10-19 01:15 across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes: one is a read-only account/billing inspector, the other performs live search queries. Their descriptions explicitly cross-reference each other with clear WHEN TO USE / WHEN NOT TO USE guidance, so an agent cannot confuse them.

Naming Consistency4/5

Both names use snake_case with a leading verb (get_, search_) followed by a noun phrase, which is a predictable pattern. The second name ('search_clean_agent_web') is a bit more adjectival/verbose but still fits the same convention without mixing styles.

Tool Count3/5

Only two tools exist for a server whose name implies search plus extraction, which feels thin. The billing/status tool is arguably auxiliary rather than a core capability, leaving essentially one functional operation.

Completeness2/5

Despite 'extract' in the server name, there is no content-extraction tool, no pagination/filter options, and no other marketplace endpoints, so the surface has significant gaps relative to its stated domain. An agent needing extraction after search would hit a dead end.

Available Tools

2 tools

get_agent_wallet_statusA

Read-onlyIdempotent

Inspect

Inspect an agent's account ledger: remaining free trial calls (out of 5), prepaid USD balance, cumulative spend, total API calls, and total LLM tokens saved. WHEN TO USE: Call before a batch of paid tool executions or after completing a Stripe or USDC top-up to confirm your balance. WHEN NOT TO USE: Do not use to process web content, execute marketplace tools, or submit payments; use the other tools on this server for execution. PARAMETER INTERACTIONS: Omit agent_id to inspect the default trial account derived from your client IP, or pass your explicit agent_id or agd_pass_ session key to check a specific funded wallet. Free and read-only: never charges a fee or consumes a free trial call. Example: get_agent_wallet_status(agent_id='example')

Name	Required	Description	Default
`agent_id`	No	Optional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it never charges a fee or consumes a free trial call, and the default wallet is derived from the caller's client IP. It does not discuss rate limits or caching, but the cost/free-trial guarantee is meaningful behavioral disclosure.

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

Conciseness4/5

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

Front-loaded with the ledger contents, then structured WHEN TO USE / WHEN NOT TO USE / PARAMETER INTERACTIONS / Example. The labeled sections make it scannable, though the repetition of the read-only guarantee and the worked example add a little bulk.

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?

An output schema exists, so return-value detail is optional, yet the description still names the key fields. With a single optional parameter, no nested objects, and annotations covering safety, an agent has everything needed to invoke it correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description goes slightly further by naming the agd_pass_ session-key form and framing the two modes as an interaction (omit for IP-derived trial account vs. pass explicit agent_id/session key for a funded wallet), which aids selection even though the schema states the omit behavior.

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?

States a specific verb (inspect) and resource (agent's account ledger) and enumerates exactly what is returned: trial calls out of 5, prepaid USD balance, cumulative spend, total API calls, tokens saved. This clearly separates it from the sibling web-content tools (distill_webpage, extract_structured_data, recon_webpage_skeleton), which operate on webpages rather than wallet state.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE (before paid tool batches, after a Stripe or USDC top-up) and WHEN NOT TO USE (not for processing web content, executing marketplace tools, or submitting payments). The exclusion clause routes the agent back to the other server tools for execution, so the alternative is named.

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

search_clean_agent_webA

Read-onlyIdempotent

Inspect

Executes live Google News RSS + HackerNews Algolia search queries and returns clean, token-pruned results with zero ad bloat. WHEN TO USE: Call search_clean_agent_web when your task requires deterministic serp-extract analysis for query; use get_agent_wallet_status to check your remaining free trial quota or prepaid balance. WHEN NOT TO USE: Do not use for unrelated domains or binary media. PARAMETER INTERACTIONS: Pass the target query as a non-empty string; omit agent_id and tx_hash during your 5 free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). $0.01 per call. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: search_clean_agent_web(query='example')

Name	Required	Description
`query`	Yes	Search query for live news, technical articles, and web results.
`tx_hash`	No	Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id.
`agent_id`	No	Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up.

Output Schema

Name	Required	Description
`data`	No	Structured tool output payload.
`status`	Yes	Execution status ('ok' or 'payment_required').
`roi_proof`	No	Token compression and cost-savings verification metrics.

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), yet the description adds substantial behavioral context beyond them: 1-hour caching with <5ms hits, a $0.01 per-call price, 5 free calls per agent_id, and critically that after quota exhaustion it returns a payment-required quote rather than a fatal error, plus the retry flow. This is exactly the kind of undisclosed-by-annotations detail that prevents agent failure loops.

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

Conciseness4/5

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

Front-loads purpose, then usage, then parameter interactions using clear labeled sections, so an agent can scan it quickly. It is slightly over-long with some redundancy (pricing stated as '$0.01 per call' and again in the 'Pricing:' clause) and payment mechanics that verge on marketing copy, but no sentence is wholly wasted.

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?

With an output schema present, return format needn't be restated, and the description covers the remaining gaps: cost, quota, caching, auth requirements, failure mode, and retry procedure. Nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds interaction semantics not present in the schema: omit agent_id and tx_hash during free trial calls, or supply agent_id (agd_pass_...) / tx_hash for paid execution. It clarifies the mutually-alternative relationship between the two optional auth params, which the schema only describes individually.

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?

States a specific verb and resource ('Executes live Google News RSS + HackerNews Algolia search queries'), names the output quality ('clean, token-pruned results'), and implicitly distinguishes itself from the sibling get_agent_wallet_status by scoping it to search 'serp-extract' analysis. An agent can tell what this does without opening the schema.

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

Usage Guidelines5/5

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

Contains explicit WHEN TO USE and WHEN NOT TO USE sections, names the alternative sibling for quota checks, and states the exclusion ('unrelated domains or binary media'). Routing is fully specified rather than inferred.

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.

2 tool updatesOct 19, 2026
- Changedget_agent_wallet_status1 field changed
  - addedInput schema / examples
```
Added value: +[
+  {
+    "agent_id": "example"
+  }
+]
```
- Changedsearch_clean_agent_web1 field changed
  - addedInput schema / examples
```
Added value: +[
+  {
+    "query": "example"
+  }
+]
```

2 tool updatesOct 19, 2026

Changedget_agent_wallet_status6 fields changed

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."New value: +"Optional Agent ID or agd_pass_ session key to inspect. Omit to check the default wallet derived from your client IP."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

removedInput schema / properties / tx_hash

Removed value: -{
-  "description": "Not needed; this tool is free.",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

Changedsearch_clean_agent_web8 fields changed

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

changedInput schema / properties / agent_id / description

Previous value: -"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."New value: +"Optional agent identifier or prepaid agd_pass_ session key. Omit during your 5 free trial calls to use an ID automatically derived from your client IP, or pass your agd_pass_ key after topping up."

addedInput schema / properties / agent_id / maxLength
```
Added value: +256
```
addedInput schema / properties / agent_id / minLength
```
Added value: +1
```

changedInput schema / properties / tx_hash / description

Previous value: -"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."New value: +"Optional on-chain Base Mainnet (0x...) or Solana SPL USDC transaction hash. Omit unless settling an individual call directly on-chain instead of using an agd_pass_ key in agent_id."

addedInput schema / properties / tx_hash / maxLength
```
Added value: +256
```
addedInput schema / properties / tx_hash / minLength
```
Added value: +10
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Structured tool output payload.",
+      "type": "object"
+    },
+    "roi_proof": {
+      "description": "Token compression and cost-savings verification metrics.",
+      "type": "object"
+    },
+    "status": {
+      "description": "Execution status ('ok' or 'payment_required').",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

2 tool updatesOct 16, 2026

Changedget_agent_wallet_status2 fields changed

changedInput schema / properties / agent_id / description

Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Agent ID or agd_pass_ key to look up. Omit it to see the ID derived from your IP and client."

changedInput schema / properties / tx_hash / description

Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Not needed; this tool is free."

Changedsearch_clean_agent_web3 fields changed

changedInput schema / properties / agent_id / description

Previous value: -"Optional Agent ID or Session Pass (agd_pass_...)"New value: +"Your agent ID, or the agd_pass_ key you got from a payment. It tracks your free calls and credit, so treat it like a password. Omit it to use an ID derived from your IP and client."

changedInput schema / properties / query / description

Previous value: -"Search query for live news, technical articles, and web results"New value: +"Search query for live news, technical articles, and web results."

changedInput schema / properties / tx_hash / description

Previous value: -"Optional Base (0x...) or Solana USDC tx hash"New value: +"Use only after paying on-chain: the Base (0x...) or Solana USDC transfer hash. It is verified on-chain before the call runs, and any overpayment is returned as an agd_pass_ credit key."

2 tool updatesOct 16, 2026

Changedget_agent_wallet_status5 fields changed
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- addedInput schema / properties / agent_id / description
```
Added value: +"Optional Agent ID or Session Pass (agd_pass_...)"
```
- removedInput schema / properties / agent_id / maxLength
```
Removed value: -99999
```
- removedInput schema / properties / agent_id / minLength
```
Removed value: -1
```
- addedInput schema / properties / tx_hash
```
Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}
```

Changedsearch_clean_agent_web3 fields changed

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional Agent ID or Session Pass (agd_pass_...)",
+  "type": "string"
+}

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "Optional Base (0x...) or Solana USDC tx hash",
+  "type": "string"
+}

2 tool updatesOct 15, 2026
- Changedget_agent_wallet_status3 fields changed
  - addedInput schema / additionalProperties
```
Added value: +false
```
  - addedInput schema / properties / agent_id / maxLength
```
Added value: +99999
```
  - addedInput schema / properties / agent_id / minLength
```
Added value: +1
```
- Changedsearch_clean_agent_web3 fields changed
  - addedInput schema / additionalProperties
```
Added value: +false
```
  - addedInput schema / properties / query / maxLength
```
Added value: +99999
```
  - addedInput schema / properties / query / minLength
```
Added value: +1
```
2 tool updatesOct 13, 2026
- First observedget_agent_wallet_status
- First observedsearch_clean_agent_web

Related MCP Connectors

AgentDiet Zero-Bloat A2A Live Web Search & Tech News Grounding A
dev.agentdiet
Executes live Google News RSS + HackerNews Algolia search queries and returns clean, token-pruned.
Search Browser Automation
21
https://serp-extract.agentdiet.dev/mcp
Exa Search
io.github.pollinations
Search the live web and fetch clean content from source pages.
Search Browser Automation Web Scraping
15,144
https://gen.pollinations.ai/mcp/exa
web-search ADeprecated
ai.keenable
Live web search and clean-markdown page fetch over the Keenable web index.
Search Web Scraping
226
https://api.keenable.ai/mcp?keenable_title=mcp-registry
Web Search API for all your agents and LLMs
ai.blopus
Live web search, image search, topic filters and full-text fetch over our own crawled index.
Search Browser Automation
1
https://mcp.blopus.ai/mcp/

Related MCP Servers

DuckDuckGo MCP Server
Search RAG Systems
ericthered926
A
license
A
quality
C
maintenance
Provides web and news search via DuckDuckGo with support for region filtering, time ranges, and token optimization for AI assistants.
Updated 10 months ago (2025-12-18 07:04 UTC)
2
42,091 npm
1
MIT
Google Search MCP Server
Search Browser Automation
thejusdutt
A
license
A
quality
D
maintenance
Enables comprehensive web and news searches via the Google Custom Search API with integrated content extraction using the Mozilla Readability algorithm. It allows users to perform quick snippet lookups or deep searches that fetch and format full article content into clean markdown.
Updated a month ago (2026-09-24 12:01 UTC)
3
7 npm
2
MIT
Tavily MCP
Search RAG Systems Browser Automation
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables AI agents to perform LLM-optimized web searches, retrieve recent news articles with full text, and extract clean readable content from URLs. It returns synthesized answers, ranked cited sources, and page text suitable for grounding RAG workflows.
Updated 4 days ago (2026-10-29 06:34 UTC)
228 npm
MIT
mcp-google-serp-agent
RAG Systems Browser Automation Web Scraping
meanusarcanus
F
license
Not graded
quality
B
maintenance
High-speed Google search intelligence and token-optimized Markdown grounding engine for AI LLMs, autonomous agents, and RAG pipelines.
Updated 2 months ago (2026-09-01 12:44 UTC)
-

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?

Server Details

TDQS

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

DuckDuckGo MCP Server

Google Search MCP Server

Tavily MCP

mcp-google-serp-agent

Glama MCP Gateway

Resources