Nody

Created By
olympeioa year ago
Nody provides a powerful MCP Composer for creating and managing custom MCP servers. It enables you to personalize each tool's name and description to add context, helping agents use them with fewer tokens. It manages the configurations and secrets of MCP servers in one secure place, making it easier to deploy and scale your AI toolsets efficiently.
Overview

One MCP Server to TOOL them all!

Nody is a developer-first platform for managing and deploying Model Context Protocol (MCP) servers and toolsets. Nody technology maintains the tools collections in a knowledge graph. Nody clients exposing tools to your AI Agents request the knowledge graph to discover what tool should ben installed and exposed.

Nody provides a powerful MCP Composer for creating and managing custom MCP servers. It enables you to personalize each tool's name and description to add context, helping agents use them with fewer tokens. It manages the configurations and secrets of MCP servers in one secure place, making it easier to deploy and scale your AI toolsets efficiently.

Server Config

{
  "mcpServers": {
    "<Nody client name>": {
      "command": "npx",
      "args": [
        "-y",
        "@olympeio/nody-vmcp@latest"
      ],
      "env": {
        "NODY_CLIENT_ID": "<Nody client id>",
        "NODY_USER_KEY": "<your very own secret encryption key>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
olympeio
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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.

8 hours ago