ORKL MCP Server

Created By
heithsa year ago
MCP server for ORKL Threat Intelligence Library
Overview

What is ORKL MCP Server?

ORKL MCP Server is a Model Control Protocol server designed for accessing the ORKL Threat Intelligence Library, providing users with tools to interact with threat intelligence data.

How to use ORKL MCP Server?

To use the ORKL MCP Server, clone the repository from GitHub, install the necessary dependencies, and configure the server with your API settings. You can then run the server and utilize its tools to fetch threat intelligence data.

Key features of ORKL MCP Server?

  • Access to ORKL Threat Intelligence Library data via the ORKL API.
  • Efficient caching to minimize API calls.
  • Rate limiting to respect ORKL API restrictions.
  • Standardized MCP Tools and Resources for LLM interaction.
  • Built-in support for Claude Desktop integration.

Use cases of ORKL MCP Server?

  1. Fetching recent threat intelligence reports.
  2. Investigating specific threats using SHA1 hashes.
  3. Analyzing the threat landscape for specific industries.

FAQ from ORKL MCP Server?

  • What programming language is ORKL MCP Server built with?

ORKL MCP Server is built using Python.

  • Is there a license for using ORKL MCP Server?

Yes, it is licensed under the MIT License.

  • How can I configure the server?

Configuration can be done through environment variables or a JSON configuration file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
heiths
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago