OpenWatch Nigeria
REMOTE · API.OPENWATCH.NG · 2 COMPONENTS
Security incidents across Nigeria, such as kidnapping and banditry, with sources and confidence.
Available components
Last scanned (13 hours ago)
Scores higher than 18% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Security
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 25 Oct 26 −5
- HTTPS: pass → unverified ▼ security
- 18 Oct 26 −37
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.17 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Tool “get_case” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 71
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 25 Oct 2026 · Probed https://api.openwatch.ng/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openwatch.ng | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b52e0577769385a0e2c999c43074adb |
| SANs: openwatch.ng, api.openwatch.ng, *.api.openwatch.ng | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.openwatch.ng. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ng. | present | 45566 | 13 | Verified |
| openwatch.ng. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="openwatch"
Bearer realm="openwatch"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
| www-authenticate | Bearer realm="openwatch" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.openwatch.ng/mcp | Auth required | 401 | |
| http (plaintext) | http://api.openwatch.ng/mcp | Inconclusive | 405 |
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 →
get_case Get a case timeline ~73
One case. Without a paid key: its status, how it ended, dates and a short summary. With one: the full file, with totals (abducted, rescued, killed), places, who was responsible, and the dated developments with sources.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The case slug from list_cases |
No output schema declared.
No examples provided.
get_daily_brief Daily intelligence brief ~38
The daily Nigeria security brief: headline, threat level, the day's key incidents and hotspots.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Defaults to today |
No output schema declared.
No examples provided.
get_incident Get an incident ~34
One incident in full: location, casualties, confidence and the news sources that reported it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_state_risk State risk profile ~51
A state's security risk tier, national rank, incident and fatality totals, most reported threats and most affected LGAs.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Nigerian state, e.g. Plateau or FCT |
No output schema declared.
No examples provided.
get_trends Incident trends ~201
Incident counts over time with a per-type breakdown, daily, weekly or monthly, optionally for one state or incident type. Included with API plans; held to the plan's archive window.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| period | string | – | – |
| state | string | – | Nigerian state, e.g. Zamfara or FCT |
| type | string | – | Incident type code: TER Terrorism, KDN Kidnapping, BOM Bombing/Explosion, ARB Armed Robbery, CMV Communal Violence, PRT Protest, SCM Scam/Fraud, MSP Missing Person, PIR Piracy/Maritime, ASN Assassina… |
No output schema declared.
No examples provided.
list_cases List case timelines ~49
Published case timelines: ongoing or resolved stories such as mass abductions, followed from first report to outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | – | Nigerian state, e.g. Zamfara or FCT |
No output schema declared.
No examples provided.
search_incidents Search incidents ~318
Search security incidents in Nigeria, newest first. Filter by state, LGA, type code, status, confidence and date range. Bandit attacks are coded by what happened (KDN, MUR, CTR, TER), with the group in perpetrator_group. Results keep to the caller's archive window; archive.clamped says when an older date_from was cut.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | – |
| date_to | string | – | – |
| lga | string | – | Local government area within the state, e.g. Gusau; needs state. Not available on the free view, which shows state only |
| min_confidence | number | – | – |
| order | string | – | – |
| page | integer | – | – |
| per_page | integer | – | – |
| sort | string | – | – |
| state | string | – | Nigerian state, e.g. Zamfara, Akwa Ibom, FCT or Abuja |
| status | string | – | – |
| type | string | – | Incident type code: TER Terrorism, KDN Kidnapping, BOM Bombing/Explosion, ARB Armed Robbery, CMV Communal Violence, PRT Protest, SCM Scam/Fraud, MSP Missing Person, PIR Piracy/Maritime, ASN Assassina… |
No output schema declared.
No examples provided.
How do I install the OpenWatch Nigeria MCP server?
OpenWatch Nigeria is a hosted endpoint at https://api.openwatch.ng/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 · api.openwatch.ng
claude mcp add --transport http ng-openwatch-openwatch 'https://api.openwatch.ng/mcp'
What is the OpenWatch Nigeria MCP server?
OpenWatch Nigeria is an MCP server listed in the public MCP registry as ng.openwatch/openwatch. Security incidents across Nigeria, such as kidnapping and banditry, with sources and confidence. This page covers its hosted endpoint (https://api.openwatch.ng/mcp).
Is the OpenWatch Nigeria MCP server safe to use?
OpenWatch Nigeria scores 31 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 OpenWatch Nigeria MCP server expose?
OpenWatch Nigeria exposes 7 tools: search_incidents, get_incident, get_trends, get_daily_brief, get_state_risk, and 2 more. Their descriptions and schemas cost roughly 764 tokens of context every time the server is loaded.
Does the OpenWatch Nigeria MCP server require authentication?
Yes. OpenWatch Nigeria asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the OpenWatch Nigeria MCP server still maintained?
OpenWatch Nigeria is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.