SRV Record Parser Skill

Overview

SRV Record Parser splits the `record` string on whitespace and accepts three layouts: the full zone-file form (`name TTL class SRV priority weight port target`), the name followed only by the four values, or the four values alone. When the first token starts with an underscore it is taken as the record `name`. A number after it is read as the TTL only when a class or `SRV` keyword follows, or when three more numbers follow it, so `_sip._tcp.host 10 60 5060 target` is not mistaken for a TTL of 10. The class may be IN, CH or HS and defaults to IN.

`priority`, `weight` and `port` must be integers from 0 to 65535 or the call returns a 400 naming the bad field, as it does when fewer than four values remain. The name is split on dots into `service` (such as `_http`), `protocol` (with its underscore removed) and `domain`. When no name is given these are null. The trailing dot is stripped from `target`.

`service_info` looks up the service and protocol pair in a built-in list of 19 entries covering HTTP, HTTPS, FTP, LDAP, LDAPS, XMPP client and server, SIP and SIPS, SMTP, IMAP, POP3 and their TLS variants, Kerberos, CalDAV and CardDAV. It is null for anything else, such as `_minecraft._tcp`. `interpretation` turns the numbers into text: priority 0 is described as highest priority, weight 0 as no preference, and a target of `.` reports that the service is deliberately not available, as RFC 2782 defines.

`is_valid` is true on every successful parse; malformed input returns an error instead. On the Free plan `priority`, `weight`, `port`, `target`, `service_info` and `interpretation` are removed.

Live Test SRV Record Parser Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as SRVRecordParserSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "SRVRecordParserSkill",
  "arguments": {
    "record": "_http._tcp.example.com. 3600 IN SRV 10 60 80 server.example.com."
  }
}

You do not name the tool yourself; the model picks it. Asking about _http._tcp.example.com. 3600 IN SRV 10 60 80 server.example.com. in the terms this skill covers is enough for it to reach for SRVRecordParserSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

https://api.vervekit.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

{
  "status": "ok",
  "error": null,
  "data": {
    "raw_record": "_http._tcp.example.com. 86400 IN SRV 10 60 80 server.example.com.",
    "parsed": {
      "name": "_http._tcp.example.com.",
      "service": "_http",
      "protocol": "tcp",
      "domain": "example.com.",
      "ttl": 86400,
      "class": "IN",
      "priority": 10,
      "weight": 60,
      "port": 80,
      "target": "server.example.com"
    },
    "service_info": {
      "name": "HTTP",
      "description": "Web service",
      "default_port": 80
    },
    "interpretation": {
      "priority_explanation": "Priority level 10 (lower is better)",
      "weight_explanation": "Weight 60 for load balancing",
      "target_explanation": "Connect to server.example.com:80"
    },
    "is_valid": true
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Service Discovery

Parse DNS SRV records for service discovery in distributed systems, microservices, and load-balanced environments

Network Diagnostics

Build network diagnostic tools that analyze SRV records for troubleshooting connectivity and service availability issues

Configuration Analysis

Analyze service configuration in DNS including priority, weight, port, and target information for optimization

Record Validation

Validate SRV record formatting and structure to ensure compliance with RFC 2782 standards and best practices

Other ways to use SRV Record Parser Skill

Set up SRV Record Parser Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Related

More in Reference Data: