长亭百川云网站安全监测

Created By
co0onttya year ago
百川网站安全监测系统 基于大模型,提供通过 MCP Tools 对长亭百川云-网站安全监测的数据进行查询、分析和操作的功能。
Overview

What is 长亭百川云网站安全监测?

长亭百川云网站安全监测 is a monitoring tool designed for users with site detection needs, capable of effectively monitoring site availability, SSL certificate validity, expiration times, and website path scanning functionality for user-configured sites.

How to use 长亭百川云网站安全监测?

To use the tool, configure your site settings and run the command using npx with the appropriate arguments. Ensure you have the necessary tokens set in your environment variables.

Key features of 长亭百川云网站安全监测?

  • Website asset grouping queries
  • Real-time monitoring status checks for website assets
  • Configuration information queries

Use cases of 长亭百川云网站安全监测?

  1. Monitoring the availability of websites to ensure uptime.
  2. Checking the validity and expiration of SSL certificates.
  3. Scanning website paths for security vulnerabilities.

FAQ from 长亭百川云网站安全监测?

  • What types of sites can be monitored?

Any user-configured sites can be monitored using this tool.

  • Is there a cost associated with using this tool?

The tool is open-source and free to use under the MIT license.

  • How do I set up the monitoring?

Follow the quick start guide provided in the documentation to configure your monitoring settings.

Server Config

{
  "mcpServers": {
    "长亭百川云网站安全监测": {
      "isActive": true,
      "name": "长亭百川云网站安全监测",
      "description": "",
      "command": "npx",
      "args": [
        "-y",
        "rivers-radar-mcp"
      ],
      "env": {
        "RIVERS_ORG_TOKENS": ""
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
co0ontty
Star
-
Language
-
License
-
Category
monitoring

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour 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