MCP Server com SSE e Autenticação Bearer

Created By
br-silvanoa year ago
MCP Server com SSE e Autenticação Bearer
Overview

What is MCP Server com SSE e Autenticação Bearer?

MCP Server com SSE e Autenticação Bearer is an implementation of a Model Context Protocol (MCP) server built in TypeScript. It utilizes Server-Sent Events (SSE) for real-time message transport and Bearer Token authentication, enabling secure communication with clients such as LLM hosts.

How to use MCP Server?

To use the MCP Server, clone the repository, install the dependencies, configure the Bearer Token in a .env file, and run the server using ts-node for development or compile it for production.

Key features of MCP Server?

  • Real-time communication using Server-Sent Events (SSE).
  • Secure authentication via Bearer Token.
  • Modular architecture following SOLID principles.
  • Example tool for basic arithmetic operations.
  • Direct execution of TypeScript files without pre-compilation.

Use cases of MCP Server?

  1. Real-time data communication for applications requiring instant updates.
  2. Secure API interactions with Bearer Token authentication.
  3. Integration with LLMs for enhanced functionality.

FAQ from MCP Server?

  • What is the purpose of the Bearer Token?

The Bearer Token is used to authenticate requests to ensure secure access to the server.

  • Can I run this server in production?

Yes, the server can be compiled and run in a production environment after building the TypeScript files.

  • What are the requirements to run this project?

You need Node.js (version 20 or higher), npm, TypeScript, and ts-node for development.

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

5 hours ago