OnlineCyberTools MCP (280+ filterable tools)

text_extract_urls

Read-onlyIdempotent

Extract every URL from a block of text, with per-match details, filtering by scheme, deduplication, and sorting. Returns matched URLs and statistics.

Instructions

Extract URLs From Text. Scan a block of text and return every URL it contains, with per-match scheme, byte position, line number, and optional surrounding context. Filter by extraction mode (all, http, https, ftp, or a custom scheme list), deduplicate case-insensitively, and sort alphabetically. Use this for hyperlinks and protocol URIs; use text_extract_emails instead when you only want email addresses. Pure regex extraction — read-only, non-destructive, performs no network requests against the found URLs, runs locally with no auth. Rate limited to 30 requests/min per IP (text category). Returns the matched urls array plus stats (original text metrics + extraction counts and per-scheme tally) and the resolved options.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Source text to scan for URLs. Required and non-empty.
`extractionMode`	No	Which schemes to match. all = http/https/ftp plus many app schemes and bare www. links; http = http or https; https = https only; ftp = ftp or ftps; custom = use customSchemes.	all
`customSchemes`	No	Comma-separated scheme list (e.g. "myapp,custom") used only when extractionMode is custom. Required and non-empty in that mode.
`removeDuplicates`	No	Drop case-insensitive duplicate URLs from the results.
`sortResults`	No	Sort results alphabetically by URL.
`includeContext`	No	Include surrounding text around each match.
`contextLength`	No	Characters of context on each side when includeContext is true. Clamped to 10-200.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when extraction succeeded.
`urls`	No	Matched URLs, after dedupe/sort.
`stats`	No	Original-text metrics and extraction summary.
`options`	No	Resolved options actually applied.
`error`	No	Error message when success is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / contextLength / default
```
Added value: +30
```

addedInput schema / properties / contextLength / description

Added value: +"Characters of context on each side when includeContext is true. Clamped to 10-200."

addedInput schema / properties / contextLength / maximum
```
Added value: +200
```
addedInput schema / properties / contextLength / minimum
```
Added value: +10
```
addedInput schema / properties / customSchemes / default
```
Added value: +""
```

addedInput schema / properties / customSchemes / description

Added value: +"Comma-separated scheme list (e.g. \"myapp,custom\") used only when extractionMode is custom. Required and non-empty in that mode."

addedInput schema / properties / extractionMode / default
```
Added value: +"all"
```

addedInput schema / properties / extractionMode / description

Added value: +"Which schemes to match. all = http/https/ftp plus many app schemes and bare www. links; http = http or https; https = https only; ftp = ftp or ftps; custom = use customSchemes."

addedInput schema / properties / extractionMode / enum

Added value: +[
+  "all",
+  "http",
+  "https",
+  "ftp",
+  "custom"
+]

addedInput schema / properties / includeContext / default
```
Added value: +false
```

addedInput schema / properties / includeContext / description

Added value: +"Include surrounding text around each match."

addedInput schema / properties / removeDuplicates / default
```
Added value: +true
```

addedInput schema / properties / removeDuplicates / description

Added value: +"Drop case-insensitive duplicate URLs from the results."

addedInput schema / properties / sortResults / default
```
Added value: +false
```
addedInput schema / properties / sortResults / description
```
Added value: +"Sort results alphabetically by URL."
```

addedInput schema / properties / text / description

Added value: +"Source text to scan for URLs. Required and non-empty."

addedInput schema / properties / text / minLength
```
Added value: +1
```

changedInput schema / required

Previous value: -[
-  "text",
-  "extractionMode",
-  "customSchemes",
-  "removeDuplicates",
-  "sortResults",
-  "includeContext",
-  "contextLength"
-]New value: +[
+  "text"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Error message when success is false.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "options": {
+      "description": "Resolved options actually applied.",
+      "properties": {
+        "contextLength": {
+          "description": "Context length applied.",
+          "type": "integer"
+        },
+        "customSchemes": {
+          "description": "Custom schemes applied.",
+          "type": "string"
+        },
+        "extractionMode": {
+          "description": "Mode applied.",
+          "type": "string"
+        },
+        "includeContext": {
+          "description": "Context inclusion applied.",
+          "type": "boolean"
+        },
+        "removeDuplicates": {
+          "description": "Dedupe applied.",
+          "type": "boolean"
+        },
+        "sortResults": {
+          "description": "Sort applied.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "stats": {
+      "description": "Original-text metrics and extraction summary.",
+      "properties": {
+        "extraction": {
+          "properties": {
+            "duplicatesRemoved": {
+              "description": "totalFound minus uniqueUrls.",
+              "type": "integer"
+            },
+            "extractionMode": {
+              "description": "The mode used.",
+              "type": "string"
+            },
+            "schemes": {
+              "additionalProperties": {
+                "type": "integer"
+              },
+              "description": "Per-scheme match counts.",
+              "type": "object"
+            },
+            "totalFound": {
+              "description": "URLs matched before dedupe.",
+              "type": "integer"
+            },
+            "uniqueUrls": {
+              "description": "URLs after dedupe.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "original": {
+          "properties": {
+            "characters": {
+              "description": "Character count of input.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Line count of input.",
+              "type": "integer"
+            },
+            "text": {
+              "description": "The input text.",
+              "type": "string"
+            },
+            "words": {
+              "description": "Alphabetic word count of input.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when extraction succeeded.",
+      "type": "boolean"
+    },
+    "urls": {
+      "description": "Matched URLs, after dedupe/sort.",
+      "items": {
+        "properties": {
+          "context": {
+            "description": "Surrounding text, empty when includeContext is false.",
+            "type": "string"
+          },
+          "line": {
+            "description": "One-based line number of the match.",
+            "type": "integer"
+          },
+          "position": {
+            "description": "Zero-based character offset of the match.",
+            "type": "integer"
+          },
+          "scheme": {
+            "description": "Lowercased scheme, or \"unknown\".",
+            "type": "string"
+          },
+          "url": {
+            "description": "The matched URL string.",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), description adds crucial traits: pure regex extraction, read-only, non-destructive, no network requests, local with no auth, rate limited to 30 req/min. No contradiction with annotations.

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?

Description is comprehensive but slightly long. It is front-loaded with main purpose and includes all critical details. Minor verbosity in listing every feature; still efficient and well structured.

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?

Given 7 parameters with full schema description and existence of output schema, the description covers purpose, behavior, limitations, rate limit, alternatives, and output summary completely. No gaps identified.

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%; description summarizes parameters (e.g., 'Filter by extraction mode', 'deduplicate case-insensitively') but repeats some schema info. It adds value by explaining output structure (per-match fields) not in input schema, and notes constraints like 'Required and non-empty'.

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?

Description clearly states 'Extract URLs From Text' with specific verb and resource. It details scanning text, returning per-match details, and distinguishes from sibling 'text_extract_emails' for email addresses.

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

Usage Guidelines4/5

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

Provides explicit context for use: 'Use this for hyperlinks and protocol URIs; use text_extract_emails instead when you only want email addresses.' Also mentions rate limits and local execution, but does not exhaustively list when not to use.

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

Deploy Server