tlpt MCP server
io.tooloracle/tlpttooloracle.iostreamable-httpv1.0.0Scanned
TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.
17 tools: 15 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
15 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the tlpt MCP server can do
The tlpt MCP server is published by tooloracle.io, a domain the MCP Registry verified. It has 17 tools. It can create or change data (15 tools: register_exercise, phase_tracker, threat_profile, team_assignment and 11 more), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 21, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Changes things 15Claude Code: ask
attack_chainGenerate kill chain for a TIBER-EU scenario with MITRE mapping.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it Generate kill chain for a TIBER-EU scenario with MITRE mapping.
auto_simulateAutonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Autonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection. Art. 26.
evidence_bundleCompile TLPT evidence for authority attestation.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Compile TLPT evidence for authority attestation.
generate_scenariosList all 8 TIBER-EU scenarios available for autonomous simulation.No findings
Why it is in this group
- The name "generate_scenarios" says "generate": a word for a change.
Description, as the server wrote it List all 8 TIBER-EU scenarios available for autonomous simulation.
health_checkServer status.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Server status.
mitre_mapMap MITRE ATT&CK techniques to DORA TLPT.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Map MITRE ATT&CK techniques to DORA TLPT. Filter by technique ID or tactic.
obligation_mapTLPT obligations DORA-TST-06 to TST-10.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it TLPT obligations DORA-TST-06 to TST-10.
phase_trackerTrack TIBER-EU 8-phase lifecycle.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Track TIBER-EU 8-phase lifecycle.
register_exerciseRegister a TLPT/pentest exercise.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Register a TLPT/pentest exercise.
remediation_planTrack remediation of TLPT findings.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Track remediation of TLPT findings. Set add=true to create.
sync_to_ampelPush TLPT results to AmpelOracle Art.No findings
Why it is in this group
- The name "sync_to_ampel" says "sync": a word for a change.
Description, as the server wrote it Push TLPT results to AmpelOracle Art. 26 checks.
team_assignmentManage Red/Blue/White/Purple team assignments.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Manage Red/Blue/White/Purple team assignments.
test_calendarAnnual testing schedule and compliance check.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Annual testing schedule and compliance check.
threat_profileDefine threat landscape for TLPT scoping.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Define threat landscape for TLPT scoping.
tlpt_readinessAssess organizational readiness for a TLPT exercise.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Assess organizational readiness for a TLPT exercise.
Only reads 2Show 2 read-only tools
finding_registerLog a pentest/TLPT finding.No findings
Why it is in this group
- The description's first verb is "log": a word for reading.
Description, as the server wrote it Log a pentest/TLPT finding.
pingConnectivity test.No findings
Why it is in this group
- The name "ping" says "ping": a word for reading.
Description, as the server wrote it Connectivity test.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://tooloracle.io/.well-known/oauth-protected-resource/tlpt/mcp
- Authorization servers
- https://feedoracle.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (15 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tooloracle.io/tlpt/mcp/: tools/list returned 17 tools to an anonymous client, including register_exercise (write), phase_tracker (write), threat_profile (write), team_assignment (write), remediation_plan (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tlpt https://tooloracle.io/tlpt/mcp/claude mcp add --transport http tlpt https://tooloracle.io/tlpt/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tlpt__finding_register",
"mcp__tlpt__ping"
],
"ask": [
"mcp__tlpt__register_exercise",
"mcp__tlpt__phase_tracker",
"mcp__tlpt__threat_profile",
"mcp__tlpt__team_assignment",
"mcp__tlpt__remediation_plan",
"mcp__tlpt__evidence_bundle",
"mcp__tlpt__test_calendar",
"mcp__tlpt__tlpt_readiness",
"mcp__tlpt__health_check",
"mcp__tlpt__auto_simulate",
"mcp__tlpt__mitre_map",
"mcp__tlpt__attack_chain",
"mcp__tlpt__generate_scenarios",
"mcp__tlpt__sync_to_ampel",
"mcp__tlpt__obligation_map"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tlpt. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.tooloracle/tlpt/verify?hash=fbe96958c2427c425290238463486c25f209c7794af7bb27e2eac7b87cab6db6" | jq -e '.changed == false'Pinned hash fbe96958c242, from Nov 21, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.tooloracle/tlpt/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.tooloracle/tlpt)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:52 UTC.
tlpt MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the tlpt MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the tlpt MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the tlpt MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the tlpt MCP server have?
- 17 tools: 15 write, 2 read. register_exercise, phase_tracker, threat_profile, team_assignment, remediation_plan, evidence_bundle, test_calendar, tlpt_readiness and 9 more.
Does the tlpt MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the tlpt MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the tlpt MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.