Enrichment MCP Server

Created By
MSAdministratora year ago
A Model Context Protocol server for enriching data from multiple security products
Overview

what is enrichment-mcp?

Enrichment-mcp is a Model Context Protocol (MCP) server designed for the enrichment of security data, providing a structured approach to enhance the quality and context of security-related information.

how to use enrichment-mcp?

To use enrichment-mcp, set up the server by following the installation instructions on the GitHub repository, and then send security data to the server for enrichment via the defined API endpoints.

key features of enrichment-mcp?

  • Provides a structured Model Context Protocol for security data.
  • Enhances the context and quality of security information.
  • Supports integration with various security tools and platforms.

use cases of enrichment-mcp?

  1. Enriching threat intelligence data for better decision-making.
  2. Integrating with SIEM systems to improve incident response.
  3. Enhancing logs and alerts with contextual information.

FAQ from enrichment-mcp?

  • What is the purpose of enrichment-mcp?

The purpose of enrichment-mcp is to provide a standardized way to enrich security data, making it more useful for analysis and response.

  • Is enrichment-mcp open source?

Yes! enrichment-mcp is available under the MIT license and can be found on GitHub.

  • How can I contribute to enrichment-mcp?

Contributions are welcome! You can submit issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MSAdministrator
Star
0
Language
Python
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.

33 minutes ago