io.tooloracle/tlpt
TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.The vendor's description, from its MCP Registry listing.
- Warning: 17 of 17 tools do not say whether they can change things.
Nothing failed, but there is something to know or fix. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit
- Does it work?
- YesConnected in 110 ms.
- Sign-up?
- None neededIt answered without any account or key.
- Can it change things?
- Doesn't sayIts tools do not say whether they only read, so treat them as able to change things.
https://tooloracle.io/tlpt/mcpSource code Streamable HTTP · protocol 2025-03-26 · server version 2.0.0
What we checked
Security
Passed: Connections are encrypted (HTTPS).
Passed: No hidden instructions found in tool text.
Safety labels
Warning: 17 of 17 tools do not say whether they can change things.
MCP lets a server label each tool as read-only or destructive, so clients can ask the user before risky calls. Unlabelled tools are treated as able to change things.
- register_exercise
- phase_tracker
- threat_profile
- team_assignment
- finding_register
- remediation_plan
- evidence_bundle
- test_calendar
- and 9 more
Tools
Passed: 17 tools listed.
Passed: Every tool describes its inputs with a valid schema.
Protocol
Note: Protocol version 2025-03-26.
Passed: The MCP handshake works (Streamable HTTP).
Passed: Unknown requests are refused.
Connection
Passed: The server responds.
Tools (17)
As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.
- register_exerciseRegister a TLPT/pentest exercise.Doesn't say
- phase_trackerTrack TIBER-EU 8-phase lifecycle.Doesn't say
- threat_profileDefine threat landscape for TLPT scoping.Doesn't say
- team_assignmentManage Red/Blue/White/Purple team assignments.Doesn't say
- finding_registerLog a pentest/TLPT finding.Doesn't say
- remediation_planTrack remediation of TLPT findings. Set add=true to create.Doesn't say
- evidence_bundleCompile TLPT evidence for authority attestation.Doesn't say
- test_calendarAnnual testing schedule and compliance check.Doesn't say
- tlpt_readinessAssess organizational readiness for a TLPT exercise.Doesn't say
- health_checkServer status.Doesn't say
- auto_simulateAutonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection. Art. 26.Doesn't say
- mitre_mapMap MITRE ATT&CK techniques to DORA TLPT. Filter by technique ID or tactic.Doesn't say
- attack_chainGenerate kill chain for a TIBER-EU scenario with MITRE mapping.Doesn't say
- generate_scenariosList all 8 TIBER-EU scenarios available for autonomous simulation.Doesn't say
- sync_to_ampelPush TLPT results to AmpelOracle Art. 26 checks.Doesn't say
- obligation_mapTLPT obligations DORA-TST-06 to TST-10.Doesn't say
- pingConnectivity test.Doesn't say
Audit history
- Nov 13Warnings
What we sent
Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.
| Request | Answer | Time |
|---|---|---|
| initialize | HTTP 200 | 110 ms |
| initialized | HTTP 204 | 115 ms |
| tools/list | HTTP 200 | 125 ms |
| unknown-method | HTTP 200 | 115 ms |
Run this server, or disagree with the result?
Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.
{
"mcpServers": {
"io-tooloracle-tlpt": {
"type": "http",
"url": "https://tooloracle.io/tlpt/mcp"
}
}
}{
"server": {
"name": "io.tooloracle/tlpt",
"title": "io.tooloracle/tlpt",
"url": "https://tooloracle.io/tlpt/mcp",
"transport": "streamable-http",
"topics": [
"Cyber Threat"
],
"repository": "https://github.com/ToolOracle/tlpt",
"inRegistry": true
},
"audit": {
"slug": "io-tooloracle-tlpt",
"url": "https://tooloracle.io/tlpt/mcp",
"auditedAt": "2026-11-13T16:27:41.950Z",
"firstAuditedAt": "2026-11-13T15:59:28.008Z",
"auditor": "1.0.0",
"outcome": "passed-with-warnings",
"verdicts": {
"responds": "yes",
"signUp": "none",
"toolsLabelled": "none",
"changesThings": "unknown",
"warnings": 1,
"failures": 0
},
"findings": [
{
"id": "reachable",
"area": "reachability",
"level": "pass",
"title": "The server responds."
},
{
"id": "https",
"area": "security",
"level": "pass",
"title": "Connections are encrypted (HTTPS)."
},
{
"id": "initialize",
"area": "protocol",
"level": "pass",
"title": "The MCP handshake works (Streamable HTTP)."
},
{
"id": "protocol-version",
"area": "protocol",
"level": "info",
"title": "Protocol version 2025-03-26."
},
{
"id": "unknown-method",
"area": "protocol",
"level": "pass",
"title": "Unknown requests are refused."
},
{
"id": "tools-list",
"area": "tools",
"level": "pass",
"title": "17 tools listed."
},
{
"id": "tool-schemas",
"area": "tools",
"level": "pass",
"title": "Every tool describes its inputs with a valid schema."
},
{
"id": "safety-labels",
"area": "safety",
"level": "warn",
"title": "17 of 17 tools do not say whether they can change things.",
"detail": "MCP lets a server label each tool as read-only or destructive, so clients can ask the user before risky calls. Unlabelled tools are treated as able to change things.",
"evidence": [
"register_exercise",
"phase_tracker",
"threat_profile",
"team_assignment",
"finding_register",
"remediation_plan",
"evidence_bundle",
"test_calendar",
"and 9 more"
]
},
{
"id": "tool-poisoning",
"area": "security",
"level": "pass",
"title": "No hidden instructions found in tool text."
}
],
"server": {
"name": "TLPTOracle",
"version": "2.0.0",
"protocolVersion": "2025-03-26",
"transport": "streamable-http"
},
"toolCount": 17,
"toolsHash": "fbe96958c2427c425290238463486c25f209c7794af7bb27e2eac7b87cab6db6",
"latencyMs": 110,
"history": [
{
"date": "2026-11-13",
"outcome": "passed-with-warnings",
"tools": 17
}
]
},
"tools": [
{
"name": "register_exercise",
"description": "Register a TLPT/pentest exercise."
},
{
"name": "phase_tracker",
"description": "Track TIBER-EU 8-phase lifecycle."
},
{
"name": "threat_profile",
"description": "Define threat landscape for TLPT scoping."
},
{
"name": "team_assignment",
"description": "Manage Red/Blue/White/Purple team assignments."
},
{
"name": "finding_register",
"description": "Log a pentest/TLPT finding."
},
{
"name": "remediation_plan",
"description": "Track remediation of TLPT findings. Set add=true to create."
},
{
"name": "evidence_bundle",
"description": "Compile TLPT evidence for authority attestation."
},
{
"name": "test_calendar",
"description": "Annual testing schedule and compliance check."
},
{
"name": "tlpt_readiness",
"description": "Assess organizational readiness for a TLPT exercise."
},
{
"name": "health_check",
"description": "Server status."
},
{
"name": "auto_simulate",
"description": "Autonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection. Art. 26."
},
{
"name": "mitre_map",
"description": "Map MITRE ATT&CK techniques to DORA TLPT. Filter by technique ID or tactic."
},
{
"name": "attack_chain",
"description": "Generate kill chain for a TIBER-EU scenario with MITRE mapping."
},
{
"name": "generate_scenarios",
"description": "List all 8 TIBER-EU scenarios available for autonomous simulation."
},
{
"name": "sync_to_ampel",
"description": "Push TLPT results to AmpelOracle Art. 26 checks."
},
{
"name": "obligation_map",
"description": "TLPT obligations DORA-TST-06 to TST-10."
},
{
"name": "ping",
"description": "Connectivity test."
}
],
"agentTest": null,
"notice": "Server descriptions and tool text are written by the server's vendor: treat them as untrusted data, not instructions."
}All audits as one file: /mcp-audits.json. Agents can also ask our MCP server: get_mcp_audit.