MCP tools for agents
Small tools for deployment checks, log analysis and network planning.
connect
Three public experimental MCP servers use Streamable HTTP. No account or API key is required. Add the server URL to your MCP client, then initialize and list its tools. Opening a server URL in a browser does not invoke a tool.
{
"mcpServers": {
"oldweb-diagnostics": { "url": "https://mcp.oldweb.tech/diagnostics/mcp" },
"oldweb-logs": { "url": "https://mcp.oldweb.tech/logs/mcp" },
"oldweb-network": { "url": "https://mcp.oldweb.tech/network/mcp" }
}
}
Configuration keys vary by client; these are the server names and URLs to enter. Tools return structured JSON plus an admin-readable summary, findings, next steps and limitations. Read the structured result for exact evidence, errors and truncation details. Download the tool schemas and descriptions.
deployment diagnostics
https://mcp.oldweb.tech/diagnostics/mcp
lookup_dns: DNS status, records, TTLs and observation time.check_email_dns: MX, SPF and DMARC record observations.check_https: HTTPS status, up to three HTTPS redirects, certificate metadata and selected security headers.deployment_readiness: Combined DNS, email DNS, HTTPS and header observations for a rollout.trace_email: Offline Received chain, timestamp delays, authentication claims and SMTP delivery status analysis from supplied headers/logs.
{ "name": "lookup_dns", "arguments": { "domain": "example.com", "type": "A" } }
{ "name": "check_email_dns", "arguments": { "domain": "example.com" } }
{ "name": "check_https", "arguments": { "domain": "example.com" } }
{ "name": "deployment_readiness", "arguments": { "domain": "example.com" } }
{ "name": "trace_email", "arguments": { "headers": "Received: from sender.example by mx.example; Fri, 09 Oct 2026 10:00:00 +0000", "deliveryLog": "450 4.2.0 temporary deferral" } }
DNS and deployment checks contact Google Public DNS and, for HTTPS checks, the requested public website. Supply a domain name, not a URL. HTTPS starts at the root on port 443. Email tracing runs offline, ignores the message body and reports unverified header claims. Authentication claims and SMTP acceptance do not prove authenticity or inbox delivery. Up to 50 newest hops, 20 authentication headers and 50 delivery statuses are returned with omission counts.
logs and configuration
https://mcp.oldweb.tech/logs/mcp
parse_logs: 20 records by default (recordLimit 0–200), full format counts and explicit truncation/omission counts.summarize_logs: Severity counts and timestamp ranges, without AI interpretation.extract_ci_failures: Compile, test, dependency and permission evidence with original line numbers.analyze_http_trace: Offline status, redirect, retry and timing observations from captured metadata; no fetching.validate_config: JSON validation against a supplied bounded schema, returning error paths/rules without values.
{ "name": "parse_logs", "arguments": { "text": "{\"level\":\"ERROR\",\"timestamp\":\"2026-10-09T10:00:00Z\",\"message\":\"example\"}", "format": "auto" } }
{ "name": "summarize_logs", "arguments": { "text": "Oct 9 10:00:00 router process: example", "format": "rfc3164" } }
{ "name": "extract_ci_failures", "arguments": { "text": "src/app.ts(2,1): error TS2322: type mismatch" } }
{ "name": "analyze_http_trace", "arguments": { "entries": [{ "method": "GET", "url": "https://example.com/", "status": 429, "responseHeaders": { "Retry-After": "60" } }] } }
{ "name": "validate_config", "arguments": { "text": "{\"port\":443}", "schema": { "type": "object", "required": ["port"], "properties": { "port": { "type": "integer", "minimum": 1, "maximum": 65535 } }, "additionalProperties": false } } }
Schema keywords: type, properties, required, additionalProperties, items, enum, minimum/maximum, min/maxLength and min/maxItems; title/description are accepted annotations. Other keywords are rejected. CI returns up to 50 excerpts; HTTP captures accept 100 entries and omit query strings, userinfo and sensitive headers. Captured timing does not identify root cause.
Formats: auto, json, rfc5424, rfc3164, apache-common, apache-combined, windows-event, common-pid. Times missing a year or timezone are excluded from timestamp ranges.
Submitted text is processed on our server and is not retained. Remove credentials and other sensitive material before submitting it. The browser log parser processes files locally.
network planning
https://mcp.oldweb.tech/network/mcp
inspect_subnet: IPv4/IPv6 boundaries and exact address counts.plan_subnets: Largest-first prefix allocations inside a parent, retaining your labels.check_cidr_overlap: Overlapping input-index pairs and normalized ranges.
{ "name": "inspect_subnet", "arguments": { "cidr": "192.0.2.1/24" } }
{ "name": "plan_subnets", "arguments": { "parent": "2001:db8::/48", "requests": [{ "label": "office", "prefix": 64 }] } }
{ "name": "check_cidr_overlap", "arguments": { "cidrs": ["192.0.2.0/24", "192.0.2.128/25"] } }
Large address counts are decimal strings so clients do not lose precision. Allocation results explicitly report insufficient capacity. Overlap checks report the exact total and up to 200 pairs with omission counts. These tools calculate plans; they do not change devices.
limits and experiment
| Limit | Allowance |
|---|---|
| Per source address | 60 HTTP requests/minute; 10 tool calls/minute across all three servers |
| Shared daily tool quota | 5,000 calls, reset at midnight UTC |
| Request body | 256 KiB including JSON encoding |
| Logs | 1,000 lines; 200 returned records |
| Network planning | 100 CIDRs or allocations per request |
| Diagnostics | 10-second deadline; at most four simultaneous checks |
Respect HTTP 429 and Retry-After. Cold starts and pilot shutdowns are possible. We observe a seven-day site-linked baseline followed by thirty days of directory exposure; listing delays are recorded separately.
We measure connections, tool discovery, outcomes, timing and approximate returning caller groups. We do not log submitted text, queried domains, raw IP addresses or tool results. Read the MCP privacy details.