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

Confirms the MCP server is running, reports its version, and verifies API credentials against a free endpoint without spending credits, 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 disabled) verifies the credential against a free account endpoint. It never touches a paid data endpoint, so it is safe for monitors.

Input 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

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.

Changed5 schema fields changedv0.12.2Oct 16, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / properties / deprecated_params_ignored / propertyNames
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / vocabulary_warnings / items
```
Added value: +{}
```

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.4/5.0

Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld; the description adds the trait that actually matters for an agent's routing decision — zero credit cost and no paid-endpoint contact — plus the default-on credential check against a free endpoint. That is substantive, non-redundant behavioral context.

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

Conciseness4/5

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

Short, front-loaded, with the cost guarantee stated immediately after the one-word purpose. Slight redundancy between 'never spends credits' and 'never touches a paid data endpoint', though the latter also introduces the monitor-safety use case.

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?

The tool is trivial to call (0 required params), annotations cover the safety profile, and an output schema exists to describe what is reported. The description covers the one thing structured fields cannot express — that calling it is free — so nothing an agent needs is missing.

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?

Schema coverage is 100%, so both parameters are already fully documented, including the 'Default true' note that 'unless disabled' merely restates. The description adds no format, unit, or edge-case meaning beyond the schema (timeout_ms is never mentioned), so baseline 3 applies.

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?

States a specific verb and resource ('Liveness check... confirms the MCP server is up, reports its version') plus a secondary behavior (credential verification). This is unmistakably distinct from every sibling, all of which are paid data/enrichment tools.

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?

'Free: this call never spends credits' and 'safe for monitors' give a clear condition for calling it. It stops short of explicitly routing the agent away from siblings (e.g., 'use get_balance for remaining credits, not this'), so it lacks an explicit alternatives clause.

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