Mitre Attck
Server Details
MITRE ATT&CK adversary TTPs (STIX bundles)
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-mitre-attck
- GitHub Stars
- 0
- Server Listing
- mcp-mitre-attck
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
21 tool updates
- First observed
ask_pipeworx - First observed
bet_research - First observed
compare_entities - First observed
discover_tools - First observed
domains - First observed
entity_profile - First observed
forget - First observed
group - First observed
mitigation - First observed
pipeworx_feedback - First observed
polymarket_arbitrage - First observed
polymarket_edges - First observed
recall - First observed
recent_changes - First observed
remember - First observed
resolve_entity - First observed
search - First observed
software - First observed
tactic - First observed
technique - First observed
validate_claim
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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!
Related MCP Connectors
Query and retrieve information about various adversarial tactics and techniques used in cyber atta…
ThreatFox MCP — abuse.ch indicator-of-compromise feed (free, key required)
TLPTOracle — 17-tool TIBER-EU TLPT framework: scope, threat intel, scenarios, reports.
AlienVault OTX MCP — Open Threat Exchange (free with key)
Related MCP Servers
- FlicenseBqualityDmaintenanceProvides comprehensive access to the MITRE ATT\&CK knowledge base with 50+ tools for querying threat actors, malware, and techniques, including automatic ATT\&CK Navigator layer generation for threat analysis and visualization.5543-
- AlicenseBqualityCmaintenanceEnables cyber defenders to query ATT\&CK techniques, list tactics, map incidents to techniques, look up threat actor groups and mitigations, all via the MCP protocol.5MIT
- AlicenseAqualityDmaintenanceEnables AI-native access to the MITRE ATT\&CK framework, allowing LLMs and agents to query techniques, threat groups, software, and generate ATT\&CK Navigator layers for threat intelligence and security workflows.65765Apache 2.0
- AlicenseAqualityAmaintenanceComprehensive MITRE ATT\&CK MCP server with SOC integration for technique lookup, alert mapping, and coverage analysis.26354MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
The tools split into two distinct groups: MITRE ATT&CK tools (group, mitigation, technique, etc.) and Pipeworx data tools (ask_pipeworx, bet_research, compare_entities, etc.). While within each group tools are fairly distinct, the overall mix can confuse an agent expecting only MITRE tools. Some tools like 'search' and 'discover_tools' have overlapping purposes for finding information.
Tool names are inconsistent: some use verb_noun patterns (e.g., ask_pipeworx, resolve_entity), while MITRE tools use single nouns (group, technique, tactic). CamelCase is not used, but underscore conventions vary. The mix of single-word and multi-word names with underscores creates no clear pattern.
With 21 tools, the server seems overloaded for its stated MITRE ATT&CK purpose. Only 7 tools are directly MITRE-related, while the remaining 14 are from a completely different domain (Pipeworx data and betting). This mismatch makes the tool count feel excessive and unfocused.
For MITRE ATT&CK, the coverage is minimal: basic lookups exist but no relationship queries, listing, or advanced analysis. For the Pipeworx side, it appears more complete but that domain is not expected from the server name. Overall, the surface has significant gaps for its primary stated purpose.