w3security-mcp

Created By
GoPlusSecuritya year ago
A web3 security mcp server for users
Overview

what is w3security-mcp?

w3security-mcp is a web3 security management control panel (MCP) server designed to enhance security for users in the web3 ecosystem.

how to use w3security-mcp?

To use w3security-mcp, users can set up the server by following the installation instructions provided in the GitHub repository and configure it according to their security needs.

key features of w3security-mcp?

  • Comprehensive security management for web3 applications
  • User-friendly interface for monitoring and controlling security settings
  • Integration with various web3 protocols and services

use cases of w3security-mcp?

  1. Managing security settings for decentralized applications (dApps)
  2. Monitoring security threats in real-time
  3. Providing a secure environment for web3 transactions

FAQ from w3security-mcp?

  • What is the purpose of w3security-mcp?

The purpose of w3security-mcp is to provide a robust security framework for users operating in the web3 space.

  • Is w3security-mcp open-source?

Yes! w3security-mcp is open-source and available on GitHub under the Apache-2.0 license.

  • How can I contribute to w3security-mcp?

Contributions are welcome! You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GoPlusSecurity
Star
0
Language
-
License
Apache-2.0 license
Category
security

Recommend Servers

View All
Payai X402 Tools

8 hours 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.

a day ago