HTTP Status Lookup Skill

Overview

HTTP Status Code Lookup works by querying a comprehensive database of HTTP status codes defined in various RFCs. Returns detailed information including the status code name, description, category, and boolean flags for quick identification.

Live Test HTTP Status Lookup Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as HTTPStatusLookupSkill. 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.

Tool call

{
  "name": "HTTPStatusLookupSkill",
  "arguments": {
    "code": "404"
  }
}

You do not name the tool yourself; the model picks it. Asking about 404 in the terms this skill covers is enough for it to reach for HTTPStatusLookupSkill 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"
    }
  }
}

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.

Argument	Type	Description
`code`Required	integer	HTTP status code to lookup range 100–599

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.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "code": 404,
    "name": "Not Found",
    "description": "The requested resource could not be found",
    "category": "Client Error",
    "is_error": true,
    "is_success": false,
    "is_redirect": false,
    "is_informational": false
  }
}

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.

Field	Type	Example	Description
`code`	number	`404`	HTTP status code number
`name`	string	`Not Found`	Standard name of the status code
`description`	string	`The requested resource could not be found`	Detailed description of the status code
`category`Premium	string	`Client Error`	The classification of the status code by its leading digit: Informational, Success, Redirection, Client Error, or Server Error
`is_error`Premium	boolean	`true`	Whether the status code represents a client or server error (4xx or 5xx)
`is_success`	boolean	`false`	Whether the status code represents a successful response (2xx)
`is_redirect`	boolean	`false`	Whether the status code represents a redirection (3xx)
`is_informational`	boolean	`false`	Whether the status code represents an informational response (1xx)

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.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

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

API Development: Quickly reference HTTP status codes while developing and debugging APIs
Error Handling: Understand status codes when implementing error handling and response logic
Documentation: Generate status code documentation and error message templates for APIs
Troubleshooting: Diagnose HTTP errors and understand response codes during debugging

Other ways to use HTTP Status Lookup Skill

Set up HTTP Status Lookup 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.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →