Is the Astafford8488 Pitchiq MCP server down?

mcp-registry/io.github.astafford8488/pitchiq-mcp · v0.2.0

healthy
Last checked 2026-10-26 16:38 UTC · handshake 258ms

As of 2026-10-26 16:38 UTC, the Astafford8488 Pitchiq MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
4,922
outages (90d)
3
tools
8

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

Point your MCP client at this streamable-http endpoint: https://pitchiq-mcp-production.up.railway.app/mcp

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 8 tool(s); ~1,752 tokens of tool definitions.
Scores higher than 8% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~1,752 tokens per session — lighter than 60% of servers.
72 → 73 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints10
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: pitchiq_v1_booking_book_guest_slot, pitchiq_v1_brain_get_index, pitchiq_v1_brain_graph_query, pitchiq_v1_brain_search, pitchiq_v1_commerce_quote_action and 3 more

4 parameter(s) across 4 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 →

Tools: pitchiq_v1_brain_search, pitchiq_v1_discover_search_creators, pitchiq_v1_discover_search_curators, pitchiq_v1_discover_search_podcasts

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: pitchiq_v1_booking_book_guest_slot

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp/fixes

pitchiq_v1_booking_book_guest_slot 1 change 
{
  "name": "pitchiq_v1_booking_book_guest_slot",
  "description": "Book a confirmed guest slot on a PitchIQ host's PUBLIC booking calendar (Calendly-style). Outcome-priced — you pay per confirmed booking. Re-checks slot availability, sends the confirmation email, and pushes to the host's Google Calendar when connected. Find bookable hosts via discover_search_podcasts. x402-payable; no PAT required.",
  "inputSchema": {
    "type": "object",
    "required": [
      "host_handle",
      "start_at",
      "attendee_name",
      "attendee_email"
    ],
    "properties": {
      "start_at": {
        "type": "string",
        "format": "date-time",
        "description": "Slot start (ISO-8601 UTC). Must be a currently-free slot on the host's calendar — re-checked before insert."
      },
      "host_handle": {
        "type": "string",
        "maxLength": 80,
        "minLength": 1,
        "description": "The PitchIQ host's PUBLIC booking handle (e.g. from discover_search_podcasts). Books on THEIR public calendar, not yours."
      },
      "attendee_name": {
        "type": "string",
        "maxLength": 120,
        "minLength": 1,
        "description": "Name of the guest being booked (the agent's principal)."
      },
      "attendee_email": {
        "type": "string",
        "format": "email",
        "description": "Guest email — receives the confirmation + cancel link."
      },
      "attendee_notes": {
        "type": "string",
        "maxLength": 2000,
        "description": "Pitch / context the host sees alongside the booking."
      },
      "duration_minutes": {
        "type": "integer",
        "default": 30,
        "maximum": 240,
        "minimum": 5,
        "description": "Meeting length. Default 30."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
pitchiq_v1_brain_get_index 1 change 
{
  "name": "pitchiq_v1_brain_get_index",
  "description": "Return the workspace 'brain index' — every wiki page's title, slug, and one-line summary, in hierarchy order. Call this at the START of a session to learn what the workspace already knows before searching, asking the user, or creating anything. Requires an active workspace.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
pitchiq_v1_brain_graph_query 1 change 
{
  "name": "pitchiq_v1_brain_graph_query",
  "description": "Traverse the workspace knowledge graph from a specific entity. For wiki_page: returns forward links, backlinks, 5 most similar pages, and CRM entity mentions found in the page text. For contact: returns linked deals, opportunities, tasks, outreach summary, conversation count, and wiki pages mentioning this contact. For deal: returns primary contact, tasks, bookings, conversation count, and wiki pages mentioning this deal. Use this to understand relationships and discover connected information ac",
  "inputSchema": {
    "type": "object",
    "required": [
      "entity_type",
      "entity_id"
    ],
    "properties": {
      "entity_id": {
        "type": "string",
        "format": "uuid",
        "description": "UUID of the entity to query."
      },
      "entity_type": {
        "enum": [
          "wiki_page",
          "contact",
          "deal"
        ],
        "type": "string",
        "description": "The type of entity to traverse from."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/io.github.astafford8488/pitchiq-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.astafford8488/pitchiq-mcp"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.astafford8488%2Fpitchiq-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5ec3a68ae7749248…, first seen 2026-10-17, included at leaf 2484 of 74,150. Version history · verify what your client received.

Tools (8)

Compare: most reliable calendar servers · most reliable knowledge servers · most reliable search servers · most reliable finance servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Astafford8488 Pitchiq MCP server down right now?

As of 2026-10-26 16:38 UTC, the Astafford8488 Pitchiq MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Astafford8488 Pitchiq MCP server provide?

Astafford8488 Pitchiq MCP server advertises 8 tools, including pitchiq_v1_booking_book_guest_slot, pitchiq_v1_brain_get_index, pitchiq_v1_brain_graph_query, pitchiq_v1_brain_search, pitchiq_v1_commerce_quote_action.

How do I install Astafford8488 Pitchiq MCP server?

Point your MCP client at this streamable-http endpoint: https://pitchiq-mcp-production.up.railway.app/mcp

Is the Astafford8488 Pitchiq MCP server safe to connect to an AI agent?

Glimind scanned all 8 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.

Operator of Astafford8488 Pitchiq MCP server?

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.

Feedback
Help us improve