Trusted architecture context for AI agents: an evidence-backed architecture grap
Trusted architecture context for AI agents: an evidence-backed architecture graph from OpenAPI, AsyncAPI and OpenTelemetry, served over MCP.
active Production-safe Score 94/100 http no auth
At a glance
| Endpoint | https://mcp.daip.io/mcp |
|---|---|
| Source | https://github.com/michaelegner/architecture-intelligence-platform |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-10 22:29:47 |
| Last checked | 2026-11-17 21:47:58 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 369 / 576 ms |
| Last successful check | 2026-11-17 21:47:58 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
get_api_consumer_usage— Which consumers have configured access to, and which have independently observed usage of, an API Operation, an application Service or a gatget_architecture_drift— Direct service dependencies whose current evidence qualification shows a declared-versus-observed discrepancy, bound to the same stable snapget_binding_picture— EXPERIMENTAL (v0.8). The binding picture of one Bounded Context: for each consumer Service x Topic x broker, whether the binding crosses theget_destination_consumers— Which Services AIP can evidence-qualify as consumers of one Kafka Topic, for one broker and environment: each Kafka consumer group attachedget_evidence— Resolves 1..20 opaque evidence references to bounded, sanitized provenance for one explicit snapshot.get_service_dependencies— One-hop direct dependencies of a service, qualified against declared and observed evidence and bound to a stable snapshot. Also returns theget_service_dependencies_by_locality— Discovers evidenced caller-Workload localities of a service and returns its positively established HTTP dependencies per locality, with an o
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:47:58 | ✓ | ✓ | 237 ms | 94 | active |
| 2026-11-17 21:32:52 | ✓ | ✓ | 614 ms | 91 | active |
| 2026-11-17 21:17:42 | ✓ | ✓ | 231 ms | 94 | active |
| 2026-11-17 21:02:40 | ✓ | ✓ | 244 ms | 94 | active |
| 2026-11-17 20:47:18 | ✓ | ✓ | 387 ms | 91 | active |
| 2026-11-17 20:32:13 | ✓ | ✓ | 230 ms | 94 | active |
| 2026-11-17 20:17:06 | ✓ | ✓ | 514 ms | 91 | active |
| 2026-11-17 20:01:28 | ✓ | ✓ | 237 ms | 94 | active |
| 2026-11-17 19:46:11 | ✓ | ✓ | 257 ms | 94 | active |
| 2026-11-17 19:31:06 | ✓ | ✓ | 230 ms | 94 | active |
| 2026-11-17 19:16:02 | ✓ | ✓ | 255 ms | 94 | active |
| 2026-11-17 19:00:22 | ✓ | ✓ | 362 ms | 91 | active |
| 2026-11-17 18:45:21 | ✓ | ✓ | 447 ms | 91 | active |
| 2026-11-17 18:30:18 | ✓ | ✓ | 430 ms | 91 | active |
| 2026-11-17 18:15:13 | ✓ | ✓ | 592 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.daip.io/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-daip-io-mcp # JSON