Endpoint Tenure Verdict
Tenure verdict for trusted endpoints: expiry, re-registration and drift graded against approval day.
Should I use this
Quality & Safety
B
Findings (1)
- LOWin disagreement_receipt
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~141Tokens (tool definitions)
~350 BTypical response size
Minimal attention impact (0.11% 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": {
"endpoint-tenure-verdict": {
"url": "https://textforagents.com/products/endpoint-tenure-verdict/mcp"
}
}
}Remote endpoints
https://textforagents.com/products/endpoint-tenure-verdict/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪tenure_verdict(baseline, current, endpoint)
Grade an endpoint domain's tenure against an approval-time baseline snapshot (fixture pair {baseline, current}, or {endpoint} for a live witness audit).
Input Schema
{
"type": "object",
"properties": {
"baseline": {
"type": "object"
},
"current": {
"type": "object"
},
"endpoint": {
"type": "string"
}
}
}⚪disagreement_receipt(probe, tenure)
Join a probe verdict (LIVE/DEAD) with a tenure verdict into one disagreement receipt.
Input Schema
{
"type": "object",
"properties": {
"probe": {
"type": "string"
},
"tenure": {
"type": "string"
}
},
"required": [
"probe",
"tenure"
]
}Community
Evidence
Recent observations
verifiedversion not recorded2 tools