Servidor de Consultas MySQL

Created By
fersoftwarea year ago
Servidor de Consultas MySQL baseado em MCP com suporte a SSE e segurança avançada
Overview

What is MySQL MCP Server SSE?

MySQL MCP Server SSE is a MySQL query server based on the MCP (Model-Controller-Provider) framework that provides functionalities for database operations through Server-Sent Events (SSE).

How to use MySQL MCP Server SSE?

To use the server, clone the project from GitHub, install the required dependencies, configure the environment variables, and start the server using the provided command.

Key features of MySQL MCP Server SSE?

  • Built with the FastMCP framework
  • Real-time data transmission via SSE
  • Comprehensive logging system
  • Automatic transaction management (commit/rollback)
  • Advanced SQL security mechanisms including risk level control and SQL injection protection

Use cases of MySQL MCP Server SSE?

  1. Real-time data updates for web applications
  2. Secure database operations with automatic logging
  3. Managing complex SQL queries with enhanced security features

FAQ from MySQL MCP Server SSE?

  • Can I use this server for any MySQL database?

Yes! It is designed to work with any MySQL database.

  • Is there a way to customize the security settings?

Yes! You can configure various security parameters in the environment variables.

  • How do I handle errors during database operations?

The server includes a comprehensive error handling mechanism that logs errors and reverts transactions automatically.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fersoftware
Star
0
Language
Python
License
-
Category
databases
Tags

Recommend Servers

View All
Payai X402 Tools

6 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