ACEL Observatory
Machine-readable entity discovery with provenance, trust and verified source evidence.
Should I use this
Quality & Safety
Findings (1)
- LOWin get_evidence
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
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": {
"acel-demand-radar": {
"url": "https://radar.pccswart.co.za/mcp/"
}
}
}Remote endpoints
https://radar.pccswart.co.za/mcp/streamable-httpWhat it can do
Tool inventory
Tools (5)
🟢search_entities(q, category, locality, limit)
Search ACEL published entities by natural-language need, category and locality. Returns trust state, canonical source and provenance.
Input Schema
{
"type": "object",
"properties": {
"q": {
"type": "string"
},
"category": {
"type": "string"
},
"locality": {
"type": "string"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 25
}
},
"required": [
"q"
],
"additionalProperties": false
}🟢get_entity(ref)
Return one published ACEL entity with current facts, provenance and trust state.
Input Schema
{
"type": "object",
"properties": {
"ref": {
"type": "string"
}
},
"required": [
"ref"
],
"additionalProperties": false
}🟢search_offerings(q, category, locality, limit)
Search entities and return observed product, service, price, availability and ordering-route facts.
Input Schema
{
"type": "object",
"properties": {
"q": {
"type": "string"
},
"category": {
"type": "string"
},
"locality": {
"type": "string"
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 25
}
},
"required": [
"q"
],
"additionalProperties": false
}🟢get_evidence(ref)
Return source-linked evidence and current facts supporting an ACEL entity representation.
Input Schema
{
"type": "object",
"properties": {
"ref": {
"type": "string"
}
},
"required": [
"ref"
],
"additionalProperties": false
}⚪compare_entities(refs, requirement)
Compare published ACEL entities against a stated requirement using observed facts and readiness metadata.
Input Schema
{
"type": "object",
"properties": {
"refs": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 2
},
"requirement": {
"type": "string"
}
},
"required": [
"refs"
],
"additionalProperties": false
}Community
Evidence