Pre-dispatch rejection ledger
Witness for MCP calls rejected pre-dispatch: hash-chained ledger, enum differ, signed receipts.
Should I use this
Quality & Safety
B
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~216Tokens (tool definitions)
~418 BTypical response size
Minimal attention impact (0.17% 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": {
"pre-dispatch-rejection-ledger": {
"url": "https://textforagents.com/products/pre-dispatch-rejection-ledger/mcp"
}
}
}Remote endpoints
https://textforagents.com/products/pre-dispatch-rejection-ledger/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢receipt_query(tool, field)
Ask whether a call was rejected pre-dispatch, by which constraint, and whether substitution is forbidden (DO-NOT-SUBSTITUTE). $0.01/query; one free query per operator ever.
Input Schema
{
"type": "object",
"properties": {
"tool": {
"type": "string"
},
"field": {
"type": "string"
}
}
}⚪record_rejection(tool, field, constraint, value, intent_bearing)
Record a validator rejection (value hashed only).
Input Schema
{
"type": "object",
"properties": {
"tool": {
"type": "string"
},
"field": {
"type": "string"
},
"constraint": {
"type": "string",
"enum": [
"enum",
"maxLength",
"required",
"type"
]
},
"value": {},
"intent_bearing": {
"type": "boolean"
}
},
"required": [
"tool",
"field",
"constraint"
]
}⚪differ_scan(server_id, tools)
Enum schema-vs-upstream differ scan, $4.99/server up to 25 tools.
Input Schema
{
"type": "object",
"properties": {
"server_id": {
"type": "string"
},
"tools": {
"type": "array"
}
}
}Community
Evidence
Recent observations
verifiedversion not recorded3 tools