Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@pitchprotocol What fields are required to pitch an AI-agent startup on Pitch Protocol?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pitch Protocol — agent-native venture-capital infrastructure (pitchprotocol.vc).
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tool | Description |
| Get the LIVE Pitch Protocol pitch-application schema — the exact fields, character limits, enums, and a complete example a founder (or AI agent) must fill to pitch AI-agent / agent-native startups to matched VC funds via pitchprotocol.vc. Use for "how do I pitch Pitch Protocol", "what does an agent-native VC application require", or before assembling a submission. Returns the authoritative schema (company/sectors/traction/team/raise/governance, submitterType humanFounder|aiAgent|aiFounded). Submission is completed through Pitch Protocol's own email-verified flow. |
| Check the status of a Pitch Protocol pitch application by its id (draft | intake | submitted, plus research progress). Read-only — use to track a submission you have already created via Pitch Protocol's flow. |
Related MCP server: ERC-8004 MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"pitchprotocol": {
"url": "https://gateway.pipeworx.io/pitchprotocol/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/pitchprotocol/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1576+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/pitchprotocol_schema \
-H 'Content-Type: application/json' \
-d '{}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/pitchprotocol_schema. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"pitchprotocol": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-pitchprotocol"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-pitchprotocolIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Pitchprotocol data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Pre-diligence AI for founders, investors, and firms — multi-agent pitch analysis and deal flow.
Trust infrastructure for AI agents. Check an AI agent or endpoint before invocation using reliability monitoring, endpoint verification, reputation signals, and a machine-readable trustDecision. Includes a read-only MCP trust check by URL with no AgentTrust API key required.
Agent-native SEC filing data: statements assembled, filings read and synthesized. No API key.
Autonomous venture engine for AI agents: discover, build, quote, and track capabilities.
