AI Security Gateway MCP · AI Security Gateway
Not responding as MCPAvailability — last 30 days
Last observed 2 d ago by MCP Tools Edge Scanner · scheduled every 120 min
Advertised capabilities
No capability baseline
No successful discovery has completed yet, so there is no inventory to show. The Observations tab records exactly how far each attempt got.
No contract recorded yet
The first successful discovery becomes rev 1 — a normalized inventory hashed centrally (normalizer v1). Every later observation is compared against the latest revision; when the canonical hash changes, a new snapshot is stored and the change is classified as a diff. Until a baseline exists there is nothing to drift from.
Recent observations latest 7
| Observed | Result | Latency |
|---|---|---|
| Oct 30, 2026 — 2:10 PM (2 d ago) | Not an MCP response | 289 ms |
| Oct 26, 2026 — 2:05 PM (6 d ago) | Not an MCP response | 215 ms |
| Oct 22, 2026 — 2:00 PM (10 d ago) | Not an MCP response | 190 ms |
| Oct 18, 2026 — 2:00 PM (14 d ago) | Not an MCP response | 74 ms |
| Oct 14, 2026 — 1:55 PM (18 d ago) | Not an MCP response | 127 ms |
| Oct 10, 2026 — 1:51 PM (22 d ago) | Not an MCP response | 139 ms |
| Oct 6, 2026 — 1:46 PM (26 d ago) | Not an MCP response | 121 ms |
Publisher supplied
unverified| Name | AI Security Gateway MCP |
| Vendor | AI Security Gateway |
| Category | infrastructure |
| Docs | — |
| Repository | — |
| Auth expected | API key expected |
Registry and publisher metadata from the deployment seed. Displayed as supplied — MCP Tools does not verify it.
Independently observed
verified| Server name | — |
| Server version | — |
| Transport | — |
| Protocol version | — |
| First observed | — |
| Last observed | 2 d ago |
| Last successful | 53 d ago |
| Origin | Registry seed |
Facts recorded by scanners during passive observation — initialize and list calls only, never tool invocation.