ThreatNews

Created By
xue20010808a year ago
MCP server for Threat info collection in cyber security
Overview

what is ThreatNews?

ThreatNews is a multi-channel processing (MCP) server designed for collecting threat information in the field of cyber security.

how to use ThreatNews?

To use ThreatNews, you can run the command collect_threat_info with specified arguments for the date range of the threat information you wish to collect. You can also set up the MCP server with the provided configurations.

key features of ThreatNews?

  • Collects threat information from various sources.
  • Supports integration with Neo4j for knowledge graph creation.
  • Configurable MCP server settings for customized data collection.

use cases of ThreatNews?

  1. Gathering threat intelligence for security analysis.
  2. Creating visual representations of threat data using Neo4j.
  3. Monitoring and analyzing cyber threats over time.

FAQ from ThreatNews?

  • What kind of threats can ThreatNews collect information on?

ThreatNews can collect information on various cyber threats including malware, phishing attacks, and vulnerabilities.

  • Is ThreatNews open-source?

Yes! ThreatNews is available on GitHub and is licensed under the MIT license.

  • How can I contribute to ThreatNews?

Contributions can be made through GitHub by submitting pull requests or reporting issues.

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago