y

Created By
mingder78a year ago
a jsonrpc server for mcp testing
Overview

what is Project Y?

Project Y is a JSON-RPC server designed for testing MCP (Multi-Channel Protocol) functionalities. It provides a framework for developers to test and validate their MCP implementations.

how to use Project Y?

To use Project Y, first install the necessary dependencies using the command bun install. Then, run the server with the command bun run index.ts to start testing your MCP functionalities.

key features of Project Y?

  • Fast and efficient JSON-RPC server implementation.
  • Easy setup and installation with Bun.
  • Supports testing of various MCP functionalities.

use cases of Project Y?

  1. Testing MCP implementations in development environments.
  2. Validating JSON-RPC requests and responses.
  3. Facilitating communication between different components in a multi-channel system.

FAQ from Project Y?

  • What is JSON-RPC?

JSON-RPC is a remote procedure call (RPC) protocol encoded in JSON.

  • How do I install Project Y?

You can install Project Y by running bun install in your terminal.

  • Is Project Y open source?

Yes! Project Y is available on GitHub and is open for contributions.

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

a day ago