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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 minutes ago