Generect Live API MCP Server

Official

by generect

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Hybrid

Server and credential health (free)

health

Read-onlyIdempotent

Check MCP server availability with a free liveness call that never spends credits. Confirms server status, reports version, and optionally validates your API token, making it safe for monitoring.

Instructions

Liveness check. FREE — this call never spends credits. Confirms the MCP server is up, reports its version, and (unless you disable it) verifies the credential against a free account endpoint. It never touches a paid data endpoint, so it is safe to call from a monitor.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`timeout_ms`	No	Request timeout in milliseconds.
`check_credential`	No	Also verify the API token against the free /accounts/me endpoint. Default true.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ms`	No
`ok`	No
`cost`	No
`server`	No
`account`	No
`version`	No
`api_base`	No
`test_mode`	No
`balance_usd`	No
`has_credential`	No
`credential_error`	No
`credential_valid`	No
`test_mode_notice`	No
`vocabulary_warnings`	No
`deprecated_params_ignored`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.9.0Sep 24, 2026

addedInput schema / properties / check_credential

Added value: +{
+  "description": "Also verify the API token against the free /accounts/me endpoint. Default true.",
+  "type": "boolean"
+}

changedInput schema / properties / timeout_ms / description

Previous value: -"Request timeout in milliseconds"New value: +"Request timeout in milliseconds."

removedInput schema / properties / url

Removed value: -{
-  "description": "LinkedIn profile URL to validate (defaults to a public profile)",
-  "type": "string"
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "account": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "api_base": {
+      "type": "string"
+    },
+    "balance_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": false,
+      "properties": {
+        "amount_charged_usd": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "billed": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "operation": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "credential_error": {},
+    "credential_valid": {
+      "type": "boolean"
+    },
+    "deprecated_params_ignored": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "has_credential": {
+      "type": "boolean"
+    },
+    "ms": {
+      "type": "number"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "server": {
+      "type": "string"
+    },
+    "test_mode": {
+      "type": "boolean"
+    },
+    "test_mode_notice": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    },
+    "vocabulary_warnings": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark the tool as readOnly, idempotent, and openWorld, but the description adds valuable behavioral context: it never spends credits, only hits a free account endpoint, reports server version, and makes credential verification optional. This goes beyond the structured hints and helps an agent understand side effects and cost impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact: three short sentences with the core purpose and cost warning front-loaded. Every sentence adds useful information, and there is no filler or redundant restating of the tool name.

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?

For a simple tool with two optional parameters, a provided output schema, and strong annotations covering safety, this description is complete. It explains cost behavior, credential checking, endpoint usage, and monitor suitability—everything an agent needs to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers both parameters with clear descriptions, including the default for check_credential. The description adds only the paraphrased idea 'unless you disable it,' which does not significantly expand on the schema. Since schema coverage is 100%, the baseline of 3 is appropriate.

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?

The description opens with a concrete noun phrase, 'Liveness check,' and specifies exactly what the call does: confirm the server is up, report its version, and optionally verify the credential against a free endpoint. This makes it easy for an agent to distinguish from data-returning sibling tools like search_companies or enrich_lead, even without naming them.

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?

The description gives a clear use context: it is free, never spends credits, never touches a paid data endpoint, and is safe to call from a monitor. It does not explicitly name sibling alternatives or state when not to use it, but the free/safety framing is strong guidance for tool selection.

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

Deploy Server