Creator Engine
Promise extraction and alignment from contracts, NDAs, and legal documents.
Should I use this
Quality & Safety
B
Findings (1)
- LOWin extract_promises
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~127Tokens (tool definitions)
~927 BTypical response size
Minimal attention impact (0.10% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"creator-engine-mcp": {
"url": "https://creator-engine.mcpize.run/mcp"
}
}
}Remote endpoints
https://creator-engine.mcpize.run/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢extract_promises(sales_text, contract_text)
Extract promises from a sales conversation and align them against contract terms. Returns promises, contract_terms, and alignments (EXACT, IMPLIED, PARTIAL, MISSING, CONFLICT, AMBIGUOUS).
Input Schema
{
"type": "object",
"properties": {
"sales_text": {
"type": "string",
"description": "Sales conversation text (vendor promises, commitments)"
},
"contract_text": {
"type": "string",
"description": "Contract text (terms, clauses)"
}
},
"required": [
"sales_text",
"contract_text"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools