io.usefulapi/kickserv
REMOTE · KICKSERV.USEFULAPI.IO · SCANNED OCT 4
Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3534 tokens (~176/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/kickserv MCP server?
io.usefulapi/kickserv is a hosted endpoint at https://kickserv.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · kickserv.usefulapi.io
claude mcp add --transport http io-usefulapi-kickserv 'https://kickserv.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-kickserv": {
"url": "https://kickserv.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-kickserv": {
"type": "http",
"url": "https://kickserv.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-kickserv] url = "https://kickserv.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-kickserv": {
"type": "remote",
"url": "https://kickserv.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-kickserv --url 'https://kickserv.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-kickserv:
url: "https://kickserv.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-kickserv": {
"Transport": "http",
"Url": "https://kickserv.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-kickserv -t streamable-http -u 'https://kickserv.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-kickserv": {
"type": "http",
"url": "https://kickserv.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://kickserv.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of kickserv.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://kickserv.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://kickserv.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://kickserv.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://kickserv.usefulapi.io/mcp |
| Authorisation server | https://kickserv.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kickserv.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://kickserv.usefulapi.io/mcp | HTTPS enforced | 301 | https://kickserv.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
kickserv_add_customer_note Add a note to a customer ~85
WRITE: add a note to a customer. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/customers/{customer_number}/notes.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_number | integer | yes | Customer number. |
| note | string | yes | Note text. |
| public | boolean | – | True to make the note public (customer-visible). |
No output schema declared.
No examples provided.
kickserv_add_job_charge Add a charge to a job ~166
WRITE: add a charge (line item — a product, service or part) to a job. This changes the job's estimate/invoice total; it does NOT charge the customer's card. Pick `item_id` from kickserv_list_items. Kickserv: POST /{account}/jobs/{job_number}/job_charges.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Line-item description. |
| details | string | – | Line-item details. |
| discount | number | – | Discount. |
| item_id | integer | – | Item `id` from kickserv_list_items. |
| job_charge_type_id | integer | yes | Job charge type id. |
| job_number | integer | yes | Job number. |
| price_per_unit | number | – | Unit price. |
| quantity | number | – | Quantity. |
No output schema declared.
No examples provided.
kickserv_add_job_note Add a note to a job ~85
WRITE: add a note to a job. Set `public` to true to make it visible to the customer. Kickserv: POST /{account}/jobs/{job_number}/notes.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| job_number | integer | yes | Job number. |
| note | string | yes | Note text. |
| public | boolean | – | True to make the note public (customer-visible). |
No output schema declared.
No examples provided.
kickserv_create_customer Create a customer ~437
WRITE: create a new customer. Kickserv assigns the customer number. Kickserv: POST /{account}/customers.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | – | Your own account number for the customer. |
| alt_contact | string | – | Alternate contact name. |
| alt_phone_number | string | – | Alternate phone number. |
| billing_address | string | – | Billing address (where invoices go), line 1. |
| billing_address_2 | string | – | Billing address line 2. |
| billing_city | string | – | Billing city. |
| billing_country | string | – | Billing country. |
| billing_state | string | – | Billing state. |
| billing_zip_code | string | – | Billing ZIP/postal code. |
| company | boolean | – | True if the customer is a company rather than a person. |
| company_name | string | – | Company name. |
| contact | string | – | Primary contact name. |
| customer_source_id | integer | – | Customer source (lead source) id. |
| customer_type_id | integer | – | Customer type id. |
| email_address | string | – | Email address. |
| fax | string | – | Fax number. |
| first_name | string | – | Contact first name. |
| is_active | boolean | – | False to mark the customer inactive (reversible). |
| last_name | string | – | Contact last name. |
| mobile | string | – | Mobile number. |
| name | string | yes | Customer name (required). |
| notify_via_email | boolean | – | Send the customer email notifications. |
| notify_via_sms | boolean | – | Send the customer SMS notifications. |
| phone_number | string | – | Phone number. |
| service_address | string | – | Service address (where the work happens), line 1. |
| service_address_2 | string | – | Service address line 2. |
| service_city | string | – | Service city. |
| service_country | string | – | Service country (2-letter code). |
| service_state | string | – | Service state (2-letter abbreviation in the US). |
| service_zip_code | string | – | Service ZIP/postal code. |
| special_instructions | string | – | Special instructions shown to technicians. |
No output schema declared.
No examples provided.
kickserv_create_job Create a job ~302
WRITE: create a job (work order) for a customer. `customer_id` is the customer's internal `id` (from kickserv_get_customer), not the customer number; `job_type_id` is the job category. Set `estimate` to create it as an estimate. Kickserv: POST /{account}/jobs.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | The customer's internal `id` (NOT the customer_number). |
| description | string | – | Job description / work to be done. |
| duration | number | – | Job duration. |
| employee_ids | array | – | Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment. |
| ends_at | string | – | When the job ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
| estimate | boolean | – | True to create the job as an estimate. |
| job_type_id | integer | yes | Job category (job type) id. |
| name | string | – | Job name/title. |
| po_number | string | – | Customer purchase-order number. |
| scheduled_on | string | – | When the job is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
No output schema declared.
No examples provided.
kickserv_create_task Create a task ~265
WRITE: create a task (appointment / to-do) on a job and optionally assign employees. `job_id` is the job's internal `id` (from kickserv_get_job), not the job number. Kickserv: POST /{account}/tasks.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | – | The customer's internal `id`. |
| description | string | – | Task description. |
| duration | integer | – | Task duration. |
| employee_ids | array | – | Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment. |
| ends_at | string | – | When the task ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
| job_id | integer | yes | The job's internal `id` (NOT the job_number). |
| name | string | yes | Task name. |
| scheduled_at | string | – | When the task is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
| task_type_id | integer | yes | Task type id. |
No output schema declared.
No examples provided.
kickserv_get_customer Get a customer ~104
Fetch one customer by customer number, optionally with related contacts, jobs, tasks and notes. The result's `id` is what job/task create calls need as `customer_id`. Kickserv: GET /{account}/customers/{customer_number}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_number | integer | yes | Customer number (as shown in Kickserv). |
| include | array | – | Related data to embed: contacts, jobs, tasks, notes, tax_entity, custom_field_assignments. |
No output schema declared.
No examples provided.
kickserv_get_job Get a job ~105
Fetch one job by job number, optionally with its customer, assigned employees, job charges (line items), time entries and notes. Kickserv: GET /{account}/jobs/{job_number}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments. |
| job_number | integer | yes | Job number (as shown in Kickserv). |
No output schema declared.
No examples provided.
kickserv_get_task Get a task ~51
Fetch one task (appointment / to-do attached to a job) by id. Kickserv: GET /{account}/tasks/{task_id}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Task id. |
No output schema declared.
No examples provided.
kickserv_list_customer_jobs List a customer's jobs ~148
List the jobs for one customer, 30 per page. Kickserv: GET /{account}/customers/{customer_number}/jobs.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_number | integer | yes | Customer number. |
| include | array | – | Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments. |
| only | string | – | Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster. |
| page | integer | – | Page number (Kickserv returns 30 records per page). Omit for page 1. |
No output schema declared.
No examples provided.
kickserv_list_customer_notes List a customer's notes ~44
List the notes on one customer. Kickserv: GET /{account}/customers/{customer_number}/notes.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_number | integer | yes | Customer number. |
No output schema declared.
No examples provided.
kickserv_list_customers List customers ~258
List or search customers, 30 per page. Every filter is an exact match on that field. Use `only` to keep the response small. Kickserv: GET /{account}/customers.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_city | string | – | Billing city. |
| billing_state | string | – | Billing state. |
| customer_number | integer | – | Customer number. |
| email_address | string | – | Exact email address. |
| include | array | – | Related data to embed: contacts, jobs, tasks, notes, tax_entity, custom_field_assignments. |
| name | string | – | Exact customer name. |
| only | string | – | Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster. |
| page | integer | – | Page number (Kickserv returns 30 records per page). Omit for page 1. |
| phone_number | string | – | Exact phone number, e.g. 800-555-1212. |
| service_city | string | – | Service city. |
| service_state | string | – | Service state (2-letter abbreviation). |
| service_zip_code | string | – | Service ZIP (full zip+4 if the record has one). |
No output schema declared.
No examples provided.
kickserv_list_employees List employees ~58
List all employees (technicians and office staff), active and inactive. Use their `id` for job/task assignment and time entries, and `employee_number` to filter jobs. Kickserv: GET /{account}/employees.xml.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kickserv_list_items List items ~100
List products/services (the price list used for job charges), 30 per page. Active items only by default. Kickserv: GET /{account}/items.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Filter by item name. |
| page | integer | – | Page number (Kickserv returns 30 records per page). Omit for page 1. |
| which | string | – | Which items to return: active (default), inactive, or all. |
No output schema declared.
No examples provided.
kickserv_list_job_notes List a job's notes ~44
List the notes on one job. Kickserv: GET /{account}/jobs/{job_number}/notes.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| job_number | integer | yes | Job number. |
No output schema declared.
No examples provided.
kickserv_list_job_time_entries List a job's time entries ~53
List the time entries (hours logged by technicians) on one job. Kickserv: GET /{account}/jobs/{job_number}/time_entries.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| job_number | integer | yes | Job number. |
No output schema declared.
No examples provided.
kickserv_list_jobs List jobs ~232
List jobs (work orders, estimates, invoices), 30 per page, filterable by schedule window, status, assigned employee, category (job type) or job status. Kickserv: GET /{account}/jobs.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_number | integer | – | Only jobs assigned to this employee number. |
| include | array | – | Related data to embed: customer, employees, job_charges, time_entries, notes, job_type, job_status, tax_entity, custom_field_assignments. |
| job_status_id | integer | – | Only jobs with this custom job status id. |
| job_type_id | integer | – | Only jobs in this category (job type id). |
| only | string | – | Comma-separated list of columns to return, e.g. `customer_number,name`. Kickserv recommends this: it makes responses much smaller and faster. |
| page | integer | – | Page number (Kickserv returns 30 records per page). Omit for page 1. |
| scheduled | string | – | Scheduled-date window, e.g. today or this_week. |
| status | string | – | Job status. |
No output schema declared.
No examples provided.
kickserv_log_time_entry Log time on a job ~239
WRITE: log hours worked by an employee on a job. `employee_id` is the employee's `id` from kickserv_list_employees. Kickserv: POST /{account}/jobs/{job_number}/time_entries.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| billable | boolean | – | Whether the time is billable. |
| employee_id | integer | yes | The employee's `id`. |
| ended_on | string | – | When the work ended. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
| job_number | integer | yes | Job number. |
| mileage | number | – | Mileage driven. |
| note | string | – | Note about the work. |
| number_of_hours | number | yes | Hours worked, e.g. 1.25. |
| started_on | string | yes | When the work started, e.g. `2026-10-02 13:00` or `10/02/2026 01:00pm`. |
| time_entry_type_id | integer | – | Time entry type id. |
No output schema declared.
No examples provided.
kickserv_update_customer Update a customer ~468
WRITE: update fields on an existing customer. Only the fields you pass change. Balances, credit limit and custom fields are not settable here. Kickserv: PATCH /{account}/customers/{customer_number}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | – | Your own account number for the customer. |
| alt_contact | string | – | Alternate contact name. |
| alt_phone_number | string | – | Alternate phone number. |
| billing_address | string | – | Billing address (where invoices go), line 1. |
| billing_address_2 | string | – | Billing address line 2. |
| billing_city | string | – | Billing city. |
| billing_country | string | – | Billing country. |
| billing_state | string | – | Billing state. |
| billing_zip_code | string | – | Billing ZIP/postal code. |
| company | boolean | – | True if the customer is a company rather than a person. |
| company_name | string | – | Company name. |
| contact | string | – | Primary contact name. |
| customer_number | integer | yes | Customer number to update. |
| customer_source_id | integer | – | Customer source (lead source) id. |
| customer_type_id | integer | – | Customer type id. |
| email_address | string | – | Email address. |
| fax | string | – | Fax number. |
| first_name | string | – | Contact first name. |
| is_active | boolean | – | False to mark the customer inactive (reversible). |
| last_name | string | – | Contact last name. |
| mobile | string | – | Mobile number. |
| name | string | – | New customer name. |
| notify_via_email | boolean | – | Send the customer email notifications. |
| notify_via_sms | boolean | – | Send the customer SMS notifications. |
| phone_number | string | – | Phone number. |
| service_address | string | – | Service address (where the work happens), line 1. |
| service_address_2 | string | – | Service address line 2. |
| service_city | string | – | Service city. |
| service_country | string | – | Service country (2-letter code). |
| service_state | string | – | Service state (2-letter abbreviation in the US). |
| service_zip_code | string | – | Service ZIP/postal code. |
| special_instructions | string | – | Special instructions shown to technicians. |
No output schema declared.
No examples provided.
kickserv_update_job Update a job ~290
WRITE: update an existing job — reschedule it, rename it, change its description, category or custom job status, or reassign employees (employee_ids replaces the assignment). Totals, tax and payment fields are not settable here. Kickserv: PATCH /{account}/jobs/{job_number}.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Job description / work to be done. |
| duration | number | – | Job duration. |
| employee_ids | array | – | Employee `id`s (from kickserv_list_employees) to assign. Replaces the current assignment. |
| ends_at | string | – | When the job ends. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
| job_number | integer | yes | Job number to update. |
| job_status_id | integer | – | New custom job status id. |
| job_type_id | integer | – | New job category (job type) id. |
| name | string | – | Job name/title. |
| po_number | string | – | Customer purchase-order number. |
| scheduled_on | string | – | When the job is scheduled. A date/time string Kickserv can parse, e.g. `2026-10-02 09:30` or `10/2/2026 09:30am`. |
No output schema declared.
No examples provided.
What is the io.usefulapi/kickserv MCP server?
io.usefulapi/kickserv is an MCP server listed in the public MCP registry as io.usefulapi/kickserv. Look up Kickserv customers, jobs, notes and time entries, and create jobs, tasks and charges. This page covers its hosted endpoint (https://kickserv.usefulapi.io/mcp).
Is the io.usefulapi/kickserv MCP server safe to use?
io.usefulapi/kickserv scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.usefulapi/kickserv MCP server expose?
io.usefulapi/kickserv exposes 20 tools: kickserv_list_customers, kickserv_get_customer, kickserv_list_customer_jobs, kickserv_list_jobs, kickserv_get_job, and 15 more. Their descriptions and schemas cost roughly 3,534 tokens of context every time the server is loaded.
Does the io.usefulapi/kickserv MCP server require authentication?
Yes. io.usefulapi/kickserv asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/kickserv MCP server still maintained?
io.usefulapi/kickserv is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.