Nestjs Mcp Server Starter

Created By
adrian-d-hidalgoa year ago
Overview

What is Nestjs Mcp Server Starter?

Nestjs Mcp Server Starter is a TypeScript starter repository for building efficient and scalable server-side applications using the Nest framework.

How to use Nestjs Mcp Server Starter?

To use this starter project, clone the repository and run the following commands to set up and start your application:

$ npm install
$ npm run start

Key features of Nestjs Mcp Server Starter?

  • Built on the progressive Nest framework for Node.js.
  • Supports TypeScript for better development experience.
  • Easy setup and deployment process.
  • Includes commands for running tests and coverage.

Use cases of Nestjs Mcp Server Starter?

  1. Developing RESTful APIs.
  2. Building microservices.
  3. Creating scalable web applications.

FAQ from Nestjs Mcp Server Starter?

  • Is this project suitable for production use?

Yes, it is designed to be a starter for production-ready applications.

  • Can I deploy my application easily?

Yes, you can deploy your application using the Mau platform for AWS with simple commands.

  • Where can I find more resources?

You can visit the NestJS Documentation for more information.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
adrian-d-hidalgo
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

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.

16 hours ago