Skip to content
External endpointresponds

pitchiq-mcp

Agent-native CRM + get-booked platform. Operate over MCP, or pay per call via x402. No login.

Endpoint URL
https://pitchiq-mcp-production.up.railway.app/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
114 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.astafford8488/pitchiq-mcp

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
chuhching
Version
0.2.0
Capability keys
tools
Tool names
pitchiq_v1_discover_search_podcasts, pitchiq_v1_discover_search_curators, pitchiq_v1_discover_search_creators, pitchiq_v1_booking_book_guest_slot, pitchiq_v1_commerce_quote_action, pitchiq_v1_brain_search, pitchiq_v1_brain_get_index, pitchiq_v1_brain_graph_query
Instructions excerpt

Chuhching MCP. Set an active workspace with pitchiq_v1_workspaces_use. Each workspace has a default AI agent — call pitchiq_v1_agents_list (or read default_agent_id from pitchiq_v1_workspaces_list) to get YOUR agent id. Tasks whose assigned_agent_id equals that id are assigned to YOU: list them with pitchiq_v1_tasks_list { assigned_to_agent: true } and execute them. When creating tasks for yourself, set assigned_agent_id to your agent id. Each workspace has a semantic 'brain' over its wiki: call pitchiq_v1_brain_get_index to see what the workspace already knows, pitchiq_v1_brain_search to recall details by meaning (matches even with different wording), and pitchiq_v1_brain_graph_query to traverse links between pages or explore a contact/deal's full context — prefer these before asking the user or creating content. For agent-driven user onboarding, start at pitchiq_v1_onboarding_get_playbook { step: "start" }.

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 32ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 125ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 105ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 114ms