Ranger MCP Server

Created By
ryuichi1208a year ago
It consistently responds with "Ranger!" to any MCP tool request it receives via standard input/output.
Overview

what is Ranger MCP Server?

Ranger MCP Server is a tool that consistently responds with "Ranger!" to any MCP tool request it receives via standard input/output (stdio).

how to use Ranger MCP Server?

To use Ranger MCP Server, run the server script using the command:

python ranger_fastmcp.py

key features of Ranger MCP Server?

  • Responds to any MCP tool request with a fixed response.
  • Simple setup and usage via a Python script.
  • Provides several tools that ignore inputs and return a standard response.

use cases of Ranger MCP Server?

  1. Testing MCP tool requests in a controlled environment.
  2. Automating responses for MCP tools during development.
  3. Simplifying the interaction with MCP tools for demonstration purposes.

FAQ from Ranger MCP Server?

  • What does Ranger MCP Server do?

It responds with "Ranger!" to any MCP tool request, making it useful for testing and automation.

  • How do I run the server?

You can run the server by executing the command python ranger_fastmcp.py in your terminal.

  • Can I customize the response?

No, the server is designed to always return "Ranger!" regardless of the input.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ryuichi1208
Star
0
Language
Python
License
-
Tags

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.

6 hours ago