A lightweight bridge that connects Claude Code to Genudo's Model Context Protoco
A lightweight bridge that connects Claude Code to Genudo's Model Context Protocol (MCP) server, enabling AI-powered workflow automation directly from your Claude Code interface.
active Production-safe Score 87/100 http auth required
At a glance
| Endpoint | https://api.genudo.ai/mcp |
|---|---|
| Source | https://github.com/genudo-ai/genudo_mcp |
| Transport | http |
| Tools | 47 |
| Auth | bearer (bearer) |
| First seen | 2026-07-31 22:52:54 |
| Last checked | 2026-11-17 21:41:46 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 641 / 886 ms |
| Last successful check | 2026-11-17 21:41:46 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (47)
get_profile— Get the authenticated user's profile details (id, name, email, phone, image, gender) and current active subscription (including package titlget_account_summary— Get a quick snapshot of the user's account, including total pipelines, total opportunities, and message counts. Note: active_pipelines repreget_messaging_stats— Get messaging volume statistics with optional filtering by date, pipeline, and provider.get_ai_performance— Get AI performance statistics, including total messages, average response time, and total cost.get_pipeline_options— Returns available agent types, AI providers, AI models, languages, dialects, and user-connected channels to use when creating a pipeline. Asstart_pipeline_journey— Begins a guided, step-by-step journey to help the user build a complete pipeline: pipeline settings → stages (including won/lost) → actionscreate_pipeline— Creates a new AI pipeline with specified configurations. Requires agent_type_id, name, ai_model_id, and language_id. Smart Routing is the usduplicate_pipeline— Duplicates an existing pipeline into a new one named "Copy of <original name>". Requires pipeline_id. The copy includes the pipeline settingupdate_pipeline— Updates an existing pipeline. Requires pipeline_id; every other field is optional and only the provided fields are changed. Use list_pipelinlist_pipelines— List the authenticated user's pipelines with their id, name, description, status, archived flag, and connected channels (id, name, identifieget_pipeline_details— Get one pipeline's full details: persona, global instructions, operational settings, stages count, Smart Routing status, opportunity countscreate_stage— Creates a new stage inside a pipeline. Requires pipeline_id, name, nature, and order. Use list_pipelines to get pipeline IDs and list_pipeliupdate_stage— Updates an existing stage. Requires stage_id; every other field is optional and only the provided fields are changed. Use list_pipeline_staglist_pipeline_stages— List the stages of a specific pipeline owned by the authenticated user, ordered by stage order.create_action— Creates an action that integrates the pipeline with an external platform via HTTP webhook. Attach it to a specific stage by passing stage_idupdate_action— Updates an existing action. Requires action_id; every other field is optional and only the provided fields are changed. NOTE: on update, fixlist_action_results— List execution logs (OpportunityAction records) for actions belonging to a pipeline. Filter by opportunity, conversation, or a specific actilist_actions— Lists actions for a pipeline owned by the authenticated user. Pass stage_id to filter to a specific stage only, or omit it to return all actcreate_variable— Creates a pipeline variable that actions can reference by name in their url, headers, or payload (e.g. an action payload containing "{{custoupdate_variable— Updates an existing pipeline variable. Requires variable_id; every other field is optional and only the provided fields are changed. Note: ilist_variables— List the variables defined on a pipeline owned by the authenticated user. Call this BEFORE create_action / update_action to discover which {create_followup— Creates a followup sequence for a stage. A followup automatically sends re-engagement messages to opportunities that have gone quiet in thatupdate_followup— Updates an existing followup configuration. Only the fields you provide are changed. Use get_stage_followup to find the followup_id for a giget_stage_followup— Returns the followup configuration for a stage, including its intervals schedule. Use this to check whether a stage already has a followup bupdate_model_pool— Creates or updates the Smart Routing model pool for an existing pipeline. Smart Routing is the user-facing name for the internal routing fealist_model_pool— Lists the Smart Routing model pool for a pipeline. Smart Routing is the user-facing name for the internal routing feature: a router tier cholist_messages— List messages via cursor pagination. Looping through pages is allowed — pass next_cursor from each response into the next call and stop whenlist_contacts— List contacts derived from opportunities in pipelines the user owns. Each row merges custom overrides (name/email/phone/priority) over the cupdate_opportunities— Update one or many opportunities at once. Pass opportunity_ids as an array (use [123] for a single update or [1,2,3] for bulk). Supports updlist_opportunities— List opportunities (one row per opportunity) in pipelines the user owns. Includes contact, stage, source, tags, and import_result. Filters:create_knowledge_table— Creates a new knowledge table with its columns in one call. The table acts as a structured knowledge base the pipeline AI agent can search alist_knowledge_tables— Lists the authenticated user's knowledge tables with their column count and attached pipelines. Call this before upsert_knowledge_points tolist_knowledge_points— Lists the rows stored in a knowledge table, including each row's default_id and column values. Use this to find the default_ids to pass to dupsert_knowledge_points— Inserts or updates rows in a knowledge table. Each row may have a default_id (your stable identifier used for matching — if a row with thatsearch_knowledge_table— Search a knowledge table by natural-language query. Returns the most relevant rows from the table. Use list_knowledge_tables to find valid kdelete_knowledge_points— Delete specific rows from a knowledge table by their default_id values. Use list_knowledge_tables to find the knowledge_table_id, and list_klist_custom_dashboards— List all custom dashboards belonging to the authenticated user, returning each dashboard's id, name, url, and timestamps.create_custom_dashboard— Creates a new custom dashboard (embedded via iframe in the frontend) for the authenticated user with a given name and URL (must be http or hupdate_custom_dashboard— Updates an existing custom dashboard owned by the authenticated user. Requires custom_dashboard_id; name and url are optional (only provideddelete_custom_dashboard— Deletes a custom dashboard owned by the authenticated user by its custom_dashboard_id. Use list_custom_dashboards to find the ID first.list_whatsapp_chats— List the chats (personal and group) of a WhatsApp QR Code channel, most recent first, with each chat's id, name, picture and last message. Ulist_whatsapp_chat_messages— List the messages of one WhatsApp QR Code chat straight from WhatsApp, newest first — including messages sent from the phone or by humans, nget_whatsapp_media— Download the media file (image, voice note, audio, video, or document) of a WhatsApp message directly over MCP. Pass the message's `media.urlist_whatsapp_groups— List the WhatsApp groups the channel's number is in, sorted by subject (participants are not included — use list_whatsapp_group_participantsget_whatsapp_group— Get one WhatsApp group's details (subject, description, owner, settings) by its id.list_whatsapp_group_participants— List the participants of a WhatsApp group with their id and role (participant, admin, superadmin, or left).send_whatsapp_message— Send a WhatsApp message from the channel's number to a person or group. type=text needs `text`. type=image|file|voice|video needs `url` — a
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:41:46 | ✓ | ✓ | 701 ms | 90 | active |
| 2026-11-17 20:56:55 | ✓ | ✓ | 514 ms | 90 | active |
| 2026-11-17 20:27:16 | ✓ | ✓ | 523 ms | 90 | active |
| 2026-11-17 19:42:34 | ✓ | ✓ | 739 ms | 90 | active |
| 2026-11-17 19:18:02 | ✓ | ✓ | 534 ms | 90 | active |
| 2026-11-17 18:41:56 | ✓ | ✓ | 527 ms | 90 | active |
| 2026-11-17 17:57:30 | ✓ | ✓ | 502 ms | 90 | active |
| 2026-11-17 17:31:30 | ✓ | ✓ | 503 ms | 90 | active |
| 2026-11-17 16:42:27 | ✓ | ✓ | 493 ms | 90 | active |
| 2026-11-17 16:00:06 | ✓ | ✓ | 668 ms | 90 | active |
| 2026-11-17 15:25:20 | ✓ | ✓ | 682 ms | 90 | active |
| 2026-11-17 14:40:25 | ✓ | ✓ | 634 ms | 90 | active |
| 2026-11-17 13:42:58 | ✓ | ✓ | 489 ms | 90 | active |
| 2026-11-17 13:25:31 | ✓ | ✓ | 770 ms | 90 | active |
| 2026-11-17 12:41:42 | ✓ | ✓ | 505 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://api.genudo.ai/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/api-genudo-ai-mcp # JSON