Izawa MCP Server

Created By
i-am-ethana year ago
Overview

what is Izawa MCP Server?

Izawa MCP Server is a Model Context Protocol (MCP) server built with TypeScript and Express, providing profile information and blog articles.

how to use Izawa MCP Server?

To use the Izawa MCP Server, clone the repository, install dependencies, and run the development server or build for production.

key features of Izawa MCP Server?

  • Provides profile information
  • Lists blog articles
  • Returns specific blog article content

use cases of Izawa MCP Server?

  1. Serving user profile data for applications.
  2. Providing a blog platform with article management.
  3. Integrating with other services using MCP endpoints.

FAQ from Izawa MCP Server?

  • What are the requirements to run Izawa MCP Server?

You need Node.js v20.18.0 or higher and npm or yarn.

  • How do I start the development server?

Run npm run dev to start the server at http://localhost:3000.

  • Can I customize the profile information and blog content?

Yes! You can edit the userProfile object in src/server.ts and implement data sources for blog articles.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
i-am-ethan
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Hellogrowthcrm

2 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
Payai X402 Tools

11 hours ago