LSPD Interrogation MCP Server

Created By
ziyacivana year ago
🚨 A MCP Server repository for LSPD Officer Agents (PoC).
Overview

what is MCP Officer?

MCP Officer is a police interrogation simulation server built using Model Context Protocol (MCP) and powered by OpenAI's GPT-3.5-turbo model. It allows users to simulate police interrogations with dynamic strategies and realistic dialogue flows.

how to use MCP Officer?

To use MCP Officer, clone the repository, install the required packages, set up the environment variables, and start the server. You can then interact with the API to manage officer profiles and conduct interrogations.

key features of MCP Officer?

  • Integration with Model Context Protocol for dynamic resource management.
  • Utilizes OpenAI's GPT-3.5-turbo for generating interrogation strategies and simulating suspect responses.
  • Core components include officer profile management, smart interrogation mechanics, and crime type integration.

use cases of MCP Officer?

  1. Training police officers in interrogation techniques.
  2. Simulating real-life interrogation scenarios for educational purposes.
  3. Developing AI-driven interrogation tools for law enforcement agencies.

FAQ from MCP Officer?

  • Can MCP Officer simulate any type of crime?

Yes! MCP Officer can simulate various crimes and integrate evidence into the interrogation process.

  • Is there a limit to the number of suspects I can interrogate?

No, you can interrogate as many suspects as needed, depending on your server capacity.

  • How secure is the data handled by MCP Officer?

MCP Officer employs strong type checking, validation, and secure input handling to protect sensitive data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ziyacivan
Star
1
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago