Sieve
Server Details
AI-powered startup due diligence. Screen any startup across 7 IMPACT-X dimensions, get a Sieve Score (0-140) with evidence-typed findings and a clear meeting recommendation. Built for VCs, solo GPs, and angel investors.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 8 of 8 tools scored.
Each tool has a clearly distinct purpose with no ambiguity. For example, sieve_dataroom lists documents, sieve_dataroom_add uploads documents, sieve_screen runs analysis, sieve_results retrieves results, and sieve_status checks progress—all targeting specific, non-overlapping actions in the deal screening workflow.
All tools follow a consistent 'sieve_' prefix with snake_case naming, using clear verb-noun patterns like sieve_dataroom_add, sieve_screen, and sieve_results. This uniformity makes the tool set predictable and easy to navigate.
With 8 tools, the set is well-scoped for the Sieve server's purpose of startup deal screening and analysis. Each tool serves a specific role in the workflow—from data management to screening and reporting—without redundancy or bloat.
The tool set provides complete coverage for the deal screening domain, including data room management (list/add), deal listing, screening, status checking, results retrieval, memo generation, and usage tracking. There are no obvious gaps, supporting end-to-end agent workflows.
Available Tools
8 toolssieve_dataroomRead-onlyInspect
List all documents in a deal's data room.
Shows what files and content have been uploaded for a deal, along with their processing status.
Args: deal_id: The deal ID (from sieve_deals or sieve_dataroom_add).
| Name | Required | Description | Default |
|---|---|---|---|
| deal_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_dataroom_addInspect
Add a document to a deal's data room. Creates the deal if needed.
This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room.
Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal.
Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL).
Args: title: Document title (e.g. "Pitch Deck Q1 2026"). company_name: Company name -- creates deal if new, finds existing if not. deal_id: Add to an existing deal (from sieve_deals or previous sieve_dataroom_add). website_url: Company website URL (used when creating a new deal). document_type: Type: 'pitch_deck', 'financials', 'legal', or 'other'. file_path: Path to a local file (PDF, DOCX, XLSX). The tool reads and uploads it. text: Raw text or markdown content (alternative to file). url: URL to fetch document from (alternative to file).
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| text | No | ||
| title | Yes | ||
| deal_id | No | ||
| file_path | No | ||
| website_url | No | ||
| company_name | No | ||
| document_type | No | other |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_dealsRead-onlyInspect
List deals in your Sieve pipeline.
Search by company name or list all deals. Returns deal metadata including Sieve scores for screened deals.
Args: search: Search by company name (partial match). Empty returns all. limit: Maximum results to return (1-100, default 20).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| search | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_memoInspect
Get or generate an investment memo for a deal.
If generate=false (default), retrieves the existing memo. If generate=true, creates a new memo (~15-30 seconds). Requires a completed screen.
Args: deal_id: The deal ID (from sieve_deals or sieve_screen). generate: Set to true to generate a new memo. memo_type: 'internal' (IC-facing, full risks) or 'external' (founder-facing). Default: internal.
| Name | Required | Description | Default |
|---|---|---|---|
| deal_id | Yes | ||
| generate | No | ||
| memo_type | No | internal |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_resultsRead-onlyInspect
Get the full results of a completed Sieve analysis.
Returns the Sieve Score (0-140), meeting decision (Take Meeting/Pass/ Need More Info), executive summary, key strengths, and key concerns.
Args: deal_id: The deal ID returned by sieve_screen. sections: Comma-separated filter (e.g. 'summary,strengths,concerns'). Options: summary, profiles, findings, questions, strengths, concerns. Empty returns everything. Score and decision are always included.
| Name | Required | Description | Default |
|---|---|---|---|
| deal_id | Yes | ||
| sections | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_screenInspect
Run a Sieve IMPACT-X Quick Screen on a startup.
Analyzes the company across 7 dimensions (Innovators, Market, Product, Advantage, Commerce, Traction, X-Factor) and returns an analysis ID. Takes 2-5 minutes to complete. Upserts -- if the company was previously screened, returns the existing deal (set confirm=true to re-screen).
Two ways to use:
v3 (recommended): First add documents with sieve_dataroom_add, then call sieve_screen(deal_id=...) to analyze everything in the data room.
v2 (legacy): Call sieve_screen(company_name=..., website_url=...) directly. At least one of website_url or pitch_deck_text is required in this mode.
Args: company_name: Name of the startup to screen (v2 flow, or to create new deal). deal_id: Screen an existing deal by ID (v3 flow -- use after sieve_dataroom_add). website_url: Company website URL (v2 flow). pitch_deck_text: Extracted pitch deck text (v2 flow). description: Brief company description (optional). confirm: Set to true to re-screen an existing deal.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | ||
| deal_id | No | ||
| description | No | ||
| website_url | No | ||
| company_name | No | ||
| pitch_deck_text | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_statusRead-onlyInspect
Check the progress of a Sieve analysis.
Returns which IMPACT-X dimensions are complete with their scores, overall progress percentage, and current phase.
Args: deal_id: The deal ID returned by sieve_screen.
| Name | Required | Description | Default |
|---|---|---|---|
| deal_id | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
sieve_usageRead-onlyInspect
Check your Sieve API usage for the current billing period.
Shows screens used, monthly limit, tier, and organization name.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!