# 404-Team-Not-Found MCP server

Agent View of the PolicyLayer registry record for 404-Team-Not-Found: identity, probed posture, risk grade, and all 12 tools classified. HTML page: https://policylayer.com/tools/404-team-not-found

## Facts

- Server id: `Aryan-B-Parikh/404-Team-Not-Found`
- Homepage: https://github.com/Aryan-B-Parikh/404-Team-Not-Found
- Registry record: grade D, identity unverified
- Lifecycle: active
- Rate-limited: no
- Tools: 12
- Tool categories present: Execute, Read, Write
- Tags: 404 team not found, automation
- Record last modified: 2026-09-27T11:43:13.594Z

## Tools (12)

| Tool | Category | Risk | Record |
| --- | --- | --- | --- |
| `optimise_berth_cranes` | Execute | High | https://policylayer.com/tools/404-team-not-found/optimise-berth-cranes.md |
| `simulate_scenario` | Execute | High | https://policylayer.com/tools/404-team-not-found/simulate-scenario.md |
| `ask_operations_question` | Read | Low | https://policylayer.com/tools/404-team-not-found/ask-operations-question.md |
| `detect_anomalies` | Read | Low | https://policylayer.com/tools/404-team-not-found/detect-anomalies.md |
| `forecast_congestion` | Read | Low | https://policylayer.com/tools/404-team-not-found/forecast-congestion.md |
| `get_data_provenance` | Read | Low | https://policylayer.com/tools/404-team-not-found/get-data-provenance.md |
| `get_port_overview` | Read | Low | https://policylayer.com/tools/404-team-not-found/get-port-overview.md |
| `get_terminals` | Read | Low | https://policylayer.com/tools/404-team-not-found/get-terminals.md |
| `query_vessels` | Read | Low | https://policylayer.com/tools/404-team-not-found/query-vessels.md |
| `rank_hotspots` | Read | Low | https://policylayer.com/tools/404-team-not-found/rank-hotspots.md |
| `recommend_routing` | Read | Low | https://policylayer.com/tools/404-team-not-found/recommend-routing.md |
| `generate_operations_plan` | Write | Medium | https://policylayer.com/tools/404-team-not-found/generate-operations-plan.md |

## Tool descriptions

- `optimise_berth_cranes` — Run the real OR-Tools CP-SAT berth allocation and quay-crane assignment under physical constraints and compare it with FIFO. Use crane_factor and move_rate_per_crane_hour for capacity/productivity what-if analysis.
- `simulate_scenario` — Run a what-if scenario through the real CP-SAT engine. Compare baseline vs impaired crane availability/productivity and return the impact on serviced vessels, moves, wait and makespan.
- `ask_operations_question` — Ask Bob an operational question. This is a helper for nested MCP workflows; it remains engine-grounded and returns the detected intent, actions and provider mode.
- `detect_anomalies` — Detect operational anomalies with Isolation Forest and classify them as bunching, outage, yard saturation, weather or data error.
- `forecast_congestion` — 72-hour LightGBM congestion forecast for a zone. Returns hourly index, queue, wait, yard utilisation, uncertainty bands, validation, drivers and confidence. Valid zones: Z-PORT, Z-LBCT, Z-ITS, Z-PCT, Z-TTI.
- `get_data_provenance` — Return explicit data provenance and model state: AIS vs DEMO_AIS, context fingerprint, weather usage, forecast model version and confidence. Use this when a user asks whether data is real.
- `get_port_overview` — Live port overview: current KPIs, 72h congestion, hotspot risk, anomalies, arrivals and utilisation. Call this for broad situational awareness.
- `get_terminals` — Return Port of Long Beach reference terminal capacity plus live crane availability, yard utilisation and gate queue. Capacity figures are real reference data; live operational state follows dataset provenance.
- `query_vessels` — Query the current vessel queue, optionally filtered by status, and include the current CP-SAT assignment.
- `rank_hotspots` — Rank congestion hotspots using the composite risk engine and report the binding resource: BERTH, CRANE, YARD or GATE, with confidence and explanation.
- `recommend_routing` — Recommend vessel actions: DIVERT, SLOW_STEAM, PRIORITY_WINDOW or HOLD. Returns predicted wait, sustained-congestion evidence, estimated savings, confidence and rationale.
- `generate_operations_plan` — Generate the 72-hour operations plan as 12 six-hour shifts with arrivals, berthings, crane deployment, alerts, routing deadlines and supervisor checklist. Set include_text=true for printable text.

## Related servers

- UnClick (1662 tools) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md
- Apibase (1384 tools) — https://policylayer.com/tools/io-github-whiteknightonhorse-apibase.md
- Delx Mcp A2a (1068 tools) — https://policylayer.com/tools/io-github-davidmosiah-delx-mcp-a2a.md
- MCP Framework Personal (912 tools) — https://policylayer.com/tools/inggerman-mcps.md
- Hermoso (896 tools) — https://policylayer.com/tools/hermoso.md
- Nodebench (824 tools) — https://policylayer.com/tools/io-github-homenshum-nodebench.md
- Altium-MCP-Suite (817 tools) — https://policylayer.com/tools/altium-mcp-suite.md
- Eda Agent (777 tools) — https://policylayer.com/tools/eda-agent.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=404-team-not-found · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/404-team-not-found