Jokes MCP Server (TypeScript SDK)

Created By
Laskewitza year ago
TypeScript Implementation of the Jokes MCP Server
Overview

what is Jokes MCP Server?

Jokes MCP Server is a TypeScript implementation of a server that fetches jokes from various sources, specifically designed to work with the Model Context Protocol (MCP).

how to use Jokes MCP Server?

To use the Jokes MCP Server, you can make API calls to retrieve jokes from the integrated sources like chucknorris.io and icanhazdadjoke.com.

key features of Jokes MCP Server?

  • Fetch random jokes from multiple sources.
  • Supports jokes from Chuck Norris and Dad jokes.
  • Built using TypeScript for better type safety and development experience.

use cases of Jokes MCP Server?

  1. Integrating joke-fetching capabilities into applications.
  2. Creating fun chatbots that can share jokes.
  3. Enhancing user engagement on websites with random jokes.

FAQ from Jokes MCP Server?

  • What types of jokes can I get?

You can get Chuck Norris jokes and Dad jokes.

  • Is there a limit to how many jokes I can fetch?

There is no strict limit, but be mindful of the API usage policies of the joke sources.

  • How do I integrate this server into my application?

You can use the provided API endpoints to fetch jokes and integrate them into your application.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Laskewitz
Star
1
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Voyei

3 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.

13 hours ago