ACEL Observatory
REMOTE · RADAR.PCCSWART.CO.ZA
Machine-readable entity discovery with provenance, trust and verified source evidence.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 234 tokens (~46/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Aug 26 0
- Stability: 0.03 → fail ▼ security
- Tool “search_acel” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: ACEL Demand Intelligence Radar → ACEL Observatory Agent Discovery Gateway security
- Tool coverage: 33% → 0% ▼ functional
- Schema quality: 130 → 46 ▲ functional
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- MCP protocol version: 2026-07-28 → 2025-11-25 functional
- Server version: 0.1.0 → 0.3.0 functional
- New tool “compare_entities” functional
- New tool “get_entity” functional
- New tool “get_evidence” functional
- New tool “search_entities” functional
- New tool “search_offerings” functional
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://radar.pccswart.co.za/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=radar.pccswart.co.za | CN=YR1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | RSA 2048 | SHA256-RSA | 57fd1af16c0de79fb165cf9a33f93727d7d |
| SANs: radar.pccswart.co.za | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of radar.pccswart.co.za. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| za. | present | 45749 | 8 | Verified |
| co.za. | present | 41369 | 8 | Verified |
| pccswart.co.za. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://radar.pccswart.co.za/mcp/ | Verified | 200 | |
| http (plaintext) | http://radar.pccswart.co.za/mcp/ | HTTPS enforced | 301 | https://radar.pccswart.co.za/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_entities ~38
Compare published ACEL entities against a stated requirement using observed facts and readiness metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| refs | array | yes | – |
| requirement | string | – | – |
No output schema declared.
No examples provided.
get_entity ~30
Return one published ACEL entity with current facts, provenance and trust state.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | – |
No output schema declared.
No examples provided.
get_evidence ~30
Return source-linked evidence and current facts supporting an ACEL entity representation.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | yes | – |
No output schema declared.
No examples provided.
search_entities ~59
Search ACEL published entities by natural-language need, category and locality. Returns trust state, canonical source and provenance.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| locality | string | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
search_offerings ~54
Search entities and return observed product, service, price, availability and ordering-route facts.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| locality | string | – | – |
| q | string | yes | – |
No output schema declared.
No examples provided.
How do I install the ACEL Observatory MCP server?
ACEL Observatory is a hosted endpoint at https://radar.pccswart.co.za/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · radar.pccswart.co.za
claude mcp add --transport http za-co-pccswart-radar-acel-demand-radar 'https://radar.pccswart.co.za/mcp/'
What is the ACEL Observatory MCP server?
ACEL Observatory is an MCP server listed in the public MCP registry as za.co.pccswart.radar/acel-demand-radar. Machine-readable entity discovery with provenance, trust and verified source evidence. This page covers its hosted endpoint (https://radar.pccswart.co.za/mcp/).
Is the ACEL Observatory MCP server safe to use?
ACEL Observatory scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ACEL Observatory MCP server expose?
ACEL Observatory exposes 5 tools: search_entities, get_entity, search_offerings, get_evidence, compare_entities. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.
Does the ACEL Observatory MCP server require authentication?
No. We connected to ACEL Observatory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ACEL Observatory MCP server still maintained?
ACEL Observatory is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.