Home / MCP registry index / io.tooloracle/tlpt
io.tooloracle/tlpt
io.tooloracle/tlpt in the official MCP registry.
Endpoint https://tooloracle.io/tlpt/mcp/. Source: github.com/ToolOracle/tlpt.
The registry describes it as: TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.
We read its 17 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
register_exercise phase_tracker threat_profile team_assignment finding_register remediation_plan evidence_bundle test_calendar tlpt_readiness health_check auto_simulate mitre_map attack_chain generate_scenarios sync_to_ampel obligation_map ping
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-tooloracle-tlpt)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.