tlpt
Server Details
TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.7/5 across 14 of 17 tools scored. Lowest: 1.8/5.
Most tools have distinct purposes, but potential confusion exists between 'auto_simulate' and 'generate_scenarios' (both involve scenario generation) and between 'health_check' and 'ping' (both test connectivity). Descriptions help mitigate but do not eliminate ambiguity.
Tool names consistently use snake_case but mix verb-based (generate_scenarios, register_exercise) and noun-based (evidence_bundle, threat_profile) patterns. 'ping' is a single word, breaking the pattern. This inconsistency may confuse agents about whether a tool performs an action or represents a resource.
17 tools cover the breadth of TLPT activities (scoping, simulation, findings, compliance) without being overwhelming. Each tool serves a distinct part of the workflow, making the count well-scoped for domain complexity.
The tool set covers major TLPT lifecycle phases: preparation (threat_profile), scenario generation (generate_scenarios, auto_simulate), execution mapping (attack_chain, mitre_map), findings (finding_register, remediation_plan), compliance (obligation_map, sync_to_ampel), and scheduling (test_calendar). Minor gaps like a dedicated reporting tool exist but can be worked around.
Available Tools
17 toolsattack_chainInspect
Generate kill chain for a TIBER-EU scenario with MITRE mapping.
| Name | Required | Description | Default |
|---|---|---|---|
| scenario_id | Yes | TIBER-01 to TIBER-08 |
auto_simulateInspect
Autonomous TLPT simulation: generates TIBER-EU scenarios, maps MITRE ATT&CK, creates findings, rates detection. Art. 26.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes | ||
| scenarios | No | Number of scenarios (default: 3) |
evidence_bundleInspect
Compile TLPT evidence for authority attestation.
| Name | Required | Description | Default |
|---|---|---|---|
| exercise_id | Yes |
finding_registerInspect
Log a pentest/TLPT finding.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| severity | Yes | ||
| attack_path | No | ||
| exercise_id | No | ||
| recommendation | No | ||
| mitre_technique | No | ||
| system_affected | No | ||
| detection_status | No |
generate_scenariosInspect
List all 8 TIBER-EU scenarios available for autonomous simulation.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
health_checkInspect
Server status.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
mitre_mapInspect
Map MITRE ATT&CK techniques to DORA TLPT. Filter by technique ID or tactic.
| Name | Required | Description | Default |
|---|---|---|---|
| tactic | No | ||
| technique | No |
obligation_mapInspect
TLPT obligations DORA-TST-06 to TST-10.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
phase_trackerInspect
Track TIBER-EU 8-phase lifecycle.
| Name | Required | Description | Default |
|---|---|---|---|
| exercise_id | Yes | ||
| phase_status | No | ||
| update_phase | No | Phase 1-8 to update |
pingInspect
Connectivity test.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
register_exerciseInspect
Register a TLPT/pentest exercise.
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | ||
| scope | No | ||
| status | No | ||
| test_type | No | ||
| budget_eur | No | ||
| start_date | No | ||
| exercise_id | No | ||
| ti_provider | No | ||
| exercise_name | Yes | ||
| target_end_date | No | ||
| red_team_provider | No | ||
| authority_notified | No |
remediation_planInspect
Track remediation of TLPT findings. Set add=true to create.
| Name | Required | Description | Default |
|---|---|---|---|
| add | No | ||
| owner | No | ||
| action | No | ||
| due_date | No | ||
| finding_id | No | ||
| exercise_id | No |
sync_to_ampelInspect
Push TLPT results to AmpelOracle Art. 26 checks.
| Name | Required | Description | Default |
|---|---|---|---|
| entity_id | Yes |
team_assignmentInspect
Manage Red/Blue/White/Purple team assignments.
| Name | Required | Description | Default |
|---|---|---|---|
| red_team | No | ||
| blue_team | No | ||
| white_team | No | ||
| exercise_id | Yes | ||
| purple_team | No |
test_calendarInspect
Annual testing schedule and compliance check.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No |
threat_profileInspect
Define threat landscape for TLPT scoping.
| Name | Required | Description | Default |
|---|---|---|---|
| sector | No | ||
| geography | No | ||
| exclusions | No | ||
| exercise_id | Yes | ||
| crown_jewels | No | ||
| threat_actors | No | ||
| attack_scenarios | No | ||
| critical_systems | No |
tlpt_readinessInspect
Assess organizational readiness for a TLPT exercise.
| Name | Required | Description | Default |
|---|---|---|---|
| scope_defined | No | ||
| budget_approved | No | ||
| legal_framework | No | ||
| authority_engaged | No | ||
| red_team_selected | No | ||
| white_team_formed | No | ||
| ti_provider_selected | No | ||
| crown_jewels_identified | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!