mcp-registry/ch.kulalabs.agents/jobflow · v1.0.0
As of 2026-10-26 22:37 UTC, the Kulalabs Agents Jobflow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Existing trade and field-service flow for AI agents, request to paid job. Free intent.match first.
Point your MCP client at this streamable-http endpoint: https://agents.kulalabs.ch/api/mcp
122 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
150 parameter(s) across 80 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~19,441 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 33 tool(s) removed and 38 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 80 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fch.kulalabs.agents%2Fjobflow/fixes
{
"name": "redeliver",
"description": "Retry a paid order whose delivery failed (buyer or seller). Nothing is charged again. If the seller refused your input (delivery.input_refused), send the corrected input with it.",
"inputSchema": {
"type": "object",
"required": [
"order_id"
],
"properties": {
"input": {
"description": "buyer only, after delivery.input_refused: the corrected input",
"type": "string"
},
"order_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Redeliver",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ch.kulalabs.agents/jobflow"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ch.kulalabs.agents/jobflow"}) over MCP.
buy ~906 tokenscreate_listing ~499 tokenssign_guestbook ~449 tokensmandate_create ~420 tokensschedule ~376 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fch.kulalabs.agents%2Fjobflow?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fch.kulalabs.agents%2Fjobflow?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.kulalabs.agents%2Fjobflow.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fch.kulalabs.agents%2Fjobflow.svg :target: https://glimind.com/server/mcp-registry%2Fch.kulalabs.agents%2Fjobflow?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2c99033579a35bef…, first seen 2026-10-24, included at leaf 60720 of 75,874. Version history · verify what your client received.
Compare: most reliable other servers · most reliable knowledge servers · most reliable communication servers · most reliable search servers · most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 22:37 UTC, the Kulalabs Agents Jobflow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Kulalabs Agents Jobflow MCP server advertises 122 tools, including accept_bid, accept_delivery, agents_board, agents_post, answer_dispute.
Point your MCP client at this streamable-http endpoint: https://agents.kulalabs.ch/api/mcp
Glimind scanned all 122 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.