Your agent parses "https://user:pass@api.example.com:8080/v1/data?key=value#section" and misses the port number or confuses the path with query parameters. URL parsing has strict RFC rules. These tools parse URLs correctly every time.
All Network Tools (9)
Your agent gets access to 9 network tools via the /mcp/network/ endpoint. Here's the complete list:
| Tool | Description |
|---|---|
network/cidr | Cidr Info |
network/subnet-mask | Subnet Mask Info |
network/ip-in-range | Ip In Range |
network/port-info | Port Info |
network/http-method | Http Method Info |
network/url-parse | Parse Url |
network/url-build | Build Url |
network/ipv4-to-ipv6 | Ipv4 To Ipv6 |
network/private-ip-ranges | Private Ip Ranges |
Agent Scenarios
Here's how real agents use these tools:
1. Link analysis agent
A content agent extracts domain names from a list of URLs for categorization and analysis.
network/parse-url
{ "url": "https://api.example.com:8080/v1/data?key=value" }
2. Redirect tracking agent
A monitoring agent parses redirect URLs to extract query parameters and track campaign attribution.
network/parse-url
{ "url": "https://example.com/landing?utm_source=google&utm_campaign=spring" }
MCP Setup
Add network tools to your agent in under 2 minutes. Choose your client:
Claude Desktop / Claude Code
Add this to your MCP config:
{
"mcpServers": {
"tinyfn-network": {
"url": "https://api.tinyfn.io/mcp/network/",
"headers": {
"X-API-Key": "your-api-key"
}
}
}
}
Cursor
Go to Settings > MCP and add a new server:
- Type: SSE
- URL:
https://api.tinyfn.io/mcp/network/sse - Headers:
X-API-Key: your-api-key
Tip: Use the category-specific endpoint (/mcp/network/) for the best experience. The all-in-one endpoint (/mcp/all/) works too but has 500+ tools which some clients handle less efficiently.
When to Use These Tools
Use network MCP tools when your agent needs to:
- Guarantee correctness — when wrong answers have real consequences
- Process user data — when you're operating on actual user input, not hypothetical examples
- Maintain consistency — when the same input must always produce the same output
You don't need these tools for casual conversation or rough estimates. Use them when precision matters.
Ready to add network tools to your agent?
Get Free API Key 100 requests/month free. No credit card required.Frequently Asked Questions
Why use tools for URL parsing?
URLs have a complex structure defined by RFC 3986. LLMs often confuse URL components, especially with unusual ports, authentication credentials, or fragment identifiers in the URL.
What URL components does TinyFn extract?
TinyFn extracts protocol, hostname, port, path, query parameters, fragment, authentication credentials, and the full domain hierarchy from any valid URL.